I'm a software engineer, completing 10 years of professional experience this year. I started my career as a web frontend engineer (it was easier for me to de...
Not sure I agree with the “three pillar” framing in this one. I think it’s more like he was able to use the LLMs effectively because he had already built those years of experience. Someone new trying to vibe code their way into designing robust distributed systems is going to need a similar amount of time to build the correct intuitions, because the LLM doesn’t give a shit one way or the other, it’ll just do what’s in the prompt.
On the other hand, commodotizing domains that fit a repeatable pattern isn’t so bad, is it? At work I sometimes have to remind people that we’re generally just building CRUD apps to interact with data, which isn’t exactly at the bleeding edge of software. I like the idea of software engineers getting to be more portable, but unfortunately the industry still thinks LLMs are going to replace most jobs, which is obviously not possible.
Not sure I agree with the “three pillar” framing in this one. I think it’s more like he was able to use the LLMs effectively because he had already built those years of experience. Someone new trying to vibe code their way into designing robust distributed systems is going to need a similar amount of time to build the correct intuitions, because the LLM doesn’t give a shit one way or the other, it’ll just do what’s in the prompt.
On the other hand, commodotizing domains that fit a repeatable pattern isn’t so bad, is it? At work I sometimes have to remind people that we’re generally just building CRUD apps to interact with data, which isn’t exactly at the bleeding edge of software. I like the idea of software engineers getting to be more portable, but unfortunately the industry still thinks LLMs are going to replace most jobs, which is obviously not possible.