The finished product alone does not have to be the reward. The reward can still be building a great tool, a great application, etc. With AI we can build it 100x faster, freeing us up to think deeper about our test coverage, our design, our scaling, our observability.
There is no excuse for lazy execution using AI, that is, IMO, equivalent to shoddy software engineering. it's just faster and more accessible now. "AI slop" is just poor execution delivered more quickly.
The onus is still on the human in the drivers seat to deliver quality outcomes.
I enjoy building things. I do not enjoy the act typing out code by hand.
> Do you not enjoy coding? I'm not trying to be snarky, just a genuine question
To follow this debate through, to maximize coding enjoyment, shouldn't we be avoiding compilers? They take away a lot of the code we need to write. Frameworks as well?
I also hate the idea of streaming, but I have been super lazy in the past
I have listened to 44,000 songs on Spotify over the last 13 years. It has brought me a ton of value, but I would love to move back to owning my music as files. I've been getting fancier with managing self-hosted infra at home, especially using AI to help me out.
Maybe I'll get back there, but I also can't imagine only listening to 500 songs!!!!
I had to take computer architecture. We made a 4 bit CPU... or maybe it was 8 bit. I can't remember. But it was all in a software breadboard simulator thing. LogicWorks.
GraphQL and SQL are not comparable or competing technologies. GraphQL is more analogous to a REST API. GraphQL can use SQL under the hood, or you can even hand serve the bytes (tongue in cheek here). It's just an over-the-network protocol to serve data.
a Node.JS server might use SQL directly or call out to a GraphQL API, but I literally don't think it's possible to let client-side JavaScript (safely) call a SQL database server directly.