With backend I find they're good at the really high level (give me the options for architecture and their pros and cons) and doing something small and precise (gimme a function `List (Maybe a) -> List a`). The stuff in-between I have to handle myself.
This is my #1 complaint about how people talk about LLM productivity
If you aren't good at something you are not qualified to say that LLMs are good at it
> If you aren't good at something you are not qualified to say that LLMs are good at it
Hard disagree: Even if you aren't good at writing a function like `List (Maybe a) -> List a`, you can easily say whether the LLM suggestion was good or not.
If you aren't good at playing the game of go and a program beats you giving you nine handicap stones, probably the program is good at it. Many similar examples.
This doesn't follow at all, maybe you just really suck.
It is entirely possible that a game AI that you find impossible to beat is trivial to beat for almost anyone with more experience than you have
Yes, there are chess engines that can beat the best chess players
However, most people couldn't possibly tell the difference between playing against the best chess engine in the world or a novice difficulty chess AI, because most people suck at chess
"It is better than I am" is a terrible metric to use to judge when you suck at that thing
BE requires a lot more context around microservices, database, reverse-proxy, api-design, etc.
A signal that makes me correct is the number of BE vs FE at a big company.
I think it's a bit like Squarespace. The lowest possible tiers of developers will be replaced. Anything complex enough to be beyond the scope of a hobbyist isn't able to be replaced with an LLM.