Degorath

7 ms·

1.
by Degorath 15d ago
Well, stacking is one thing, doing it well is another (see github) ;) But that's good to hear.
2.
by Degorath 15d ago
As someone trying to compete in this space: will ERSC make the change/commit their unit of code review? It's one of the pet peeves I have with GitHub et al.
3.
by Degorath 15d ago
Thought I saw that announcement on LinkedIn a few weeks back already!
4.
by Degorath 29d ago
Unfortunately I wouldn't know how to do that. But just saying that I would probably argue against any new forge at my workplace if it didn't adopt the jujutsu model for changes. While agents can wrangle git better than 90% of deve
5.
by Degorath 1mo ago
Does it support jujutsu natively?
6.
by Degorath 1mo ago
There's simply a ton of teams that also never updated. My previous team was not using RTK and our redux setup was extremely confusing to me (a backend engineer).
7.
by Degorath 1mo ago
Ah, that's a shame to hear. I would only like to add that at least for Android apps that I've been "hanging around" (my team never really worked on them), the teaching materials that are provided have generally made them
8.
by Degorath 1mo ago
While all of the points you brought up are valid, I've hated every react native app I've ever had to work on. Not because of react native itself, but because they usually take random react developers to work on these apps and the
9.
by Degorath 1mo ago
Bit late to the thread, but I'm building a EU native jujutsu forge that optimises for productivity and ability to deliver your features faster. I saw that tons of companies are still on GitHub, using their unproductive tools that have
10.
by Degorath 2mo ago
That's really cool! I tried getting on board with ERSC, but the timezone difference proved too much :(. At least it gave me the kick to try and build my own company, though!
11.
by Degorath 2mo ago
Already working on that!
12.
by Degorath 2mo ago
My experience is that in companies that rely on this flow, these assumptions are generally hashed out during design doc review/discussions. I have never had it happen to me that I need to discard the rest of the stack for an assumption
13.
by Degorath 2mo ago
Not sure if it makes you feel better, but it seems there's at least a few startups trying to get a jujutsu-native forge going, by people who have seen and used the way Google's (and other big tech's) systems work.
14.
by Degorath 2mo ago
Jujutsu makes the author-side of it all fairly nice, indeed. But the reviewer-side has been so horribly abandoned by github that it has been frustrating me for a long while now.
15.
by Degorath 2mo ago
I would like to add that CachyOS also supports Niri, a scrolling tiling WM. As someone who long had "papercuts" from floating WMs I've had great success with it and even prefer it to something fully tiling like hyprland.
16.
by Degorath 2mo ago
Depending on the country, it's not even that difficult to fire in the EU... (e.g. Estonia and Poland)
17.
by Degorath 2mo ago
Well, they are wishing to lock you into their ecosystem, so that switching would be a high-friction decision. And then they can simply raise prices without you leaving.
18.
by Degorath 3mo ago
Do you folks also hire outside the US?
19.
by Degorath 4mo ago
Not anymore they don't (usual caveats apply: no longer work there; big company so YMMV). It was an option for a while, but getting it to work with the remote filesystems for the monorepo was a bit annoying (e.g. you'd create a new
20.
by Degorath 4mo ago
I just want to mention that in my personal anecdotal experience, every codebase I have ever worked on, except 1, was underengineered and not overengineered. The last one was just "engineered".
21.
by Degorath 5mo ago
Fairly certain they do something like Anthropic does, they count the acceptance rate or something else that is fairly "optimistic" (my org has a code acceptance rate of 98,5% per the platform dashboard). So, to clarify, me accepti
22.
by Degorath 5mo ago
I'm building a new version control forge around Jujutsu :). I think GitHub is pretty bad in its UX and I want to build something that is a) more opinionated than raw git; b) optimised more around team usage than GitHub is; c) uses nic
23.
by Degorath 7mo ago
My experience has so far been similar to the root commenter - at the stage where you need to have a long cycle with planning it's just slower than doing the writing + theory building on my own. It's an okay mental energy saver for
24.
by Degorath 8mo ago
I was really taken in by this premise a while back so I tried building some side projects with server side swift on my windows machine inside WSL. I really wanted to like it, but the experience was terrible, from the editing side (with vsco
25.
by Degorath 8mo ago
No, but it is a European leader that has ~recently enjoyed that situation, but is no longer in it. Sorry, but I don't want to spell it out too obviously, for my own privacy.
26.
by Degorath 8mo ago
I understand what you mean, but at this point I don't find it ironic at all. It's been quite similar in my corner of the world, where a leader enjoys great support and visibility externally, but is fairly unpopular internally.
27.
by Degorath 9mo ago
But if you just want a nicely typed interface for your APIs, in my experience gRPC is much more useful, because of all of the other downsides the blog author mentioned.
28.
by Degorath 10mo ago
Could you please elaborate on "patterns for your interfaces"?
29.
by Degorath 10mo ago
Not the person you asked, but I hate how it screws up keyboard shortcuts. It overrode the delete line shortcut with its own inline chat one, for example. Decided to ditch it for claude code right after that, since I cannot be bothered to go
30.
by Degorath 11mo ago
The IDE experience on Linux doesn't make it any better either. Oh how I wish I could have a working Swift :(.

More ›