← Back to context

Comment by SchemaLoad

7 hours ago

Everything is unless your app is a React todolist or leatcode questions.

HN's cynicism towards AI coding (and everything else ever) is exhausting. Karpathy would probably cringe reading this.

  • okay but he literally does have a bridge that non-deterministically might take you to the wrong place to sell you

    • The original context of this sub-thread was Karpathy saying how AI coding tools were pretty useless for him when working on this particular project.

people say this like it's a criticism, but damn is it ever nice to start writing a simple crud form and just have copilot autocomplete the whole thing for me.

  • Back in the 90s you could drag and drop a vb6 applet in Microsoft word. Somehow we’ve regressed..

    Edit: for the young, wysiwyg (what you see is what you get) was common for all sorts of languages from c++ to Delphi to html. You could draw up anything you wanted. Many had native bindings to data sources of all kinds. My favourite was actually HyperCard because I learned it in grade school.

  • I agree. I am "writing" simple crud apps for my own convenience and entertainment. I can use unfamiliar frameworks and languaged for extra fun and education.

    Good times!

or a typical CRUD app architecture, or a common design pattern, or unit/integration test scaffolding, or standard CI/CD pipeline definitions, or one-off utility scripts, etc...

Like 80% of writing coding is just being a glorified autocomplete and AI is exceptional at automating those aspects. Yes, there is a lot more to being a developer than writing code, but, in those instances, AI really does make a difference in the amount of time one is able to spend focusing on domain-specific deliverables.

  • And even for "out of distribution" code you can still ask question about how to do the same thing but more optimized, could a library help for this, why is that piece of code giving this unexpected output etc

  • It has gotten to the point that I don't modify or write SQL. Instead I throw some schema and related queries in and use natural language to rubber duck the change, by which point the LLM can already get it right.