A bit hyperbolic, if you use a modern linter like biome or eslint it can warn you of the few that may cause issues.
Our react/react-native monorepo has been a pleasure to work with and has massively reduced the overhead for development with a limited number of staff.
Essentially letting go of controlling our lives in ways that cause suffering. Accepting that bad things can and do happen. Realising that life is temporary and we should focus ourselves on things in our power that make us a person of better character. Everything else is out of our control and should be accepted without judgement.
It's brought a lot of comfort to me over the years.
Zed doesn’t have file delete undo and I found the AI autocomplete to be so bad I had to turn it off. I still use vscode for work. Zed is kind of in a purgatory state where its lacking in way to be a main for many folks but its close. Just the AI focus is sadly the best way for it to keep investments going, but are really not the top things I think Zed needs.
On the occasion that I find myself having to write web code for whatever reason, I'm very happy to have Claude. I don't enjoy coding for the web, like at all.
Doing backend and large distributed systems it (seems to me), much deeper. Types of consistency and their tradeoffs in practice, details like implementing and correctly using lamport clocks, good API design, endless details about reworking, on and on.
And then for both, a learned sense of what approaches to system organization will work in the long run (how to avoid needing to stage a re-write every 5 years).
Gatekeeping?
Why couldn't a backend team have all tasks be junior compatible, if uncoupled from deadlines and time constraints?