Your job is to deliver code you have proven to work
simonwillison.net
Your job is to deliver code you have proven to work
1–10 of 699 posts
Re: Your job is to deliver code you have proven to work
#2Maybe in an ideal world
Re: Your job is to deliver code you have proven to work
#3> Your job is to deliver code you have proven to work.
Your job is to solve customer problems. Their problems may only be solvable with code that is proven to work, but it is equally likely (I dare say even more likely) that their problem isn't best solved with code at all, or even solved with code that doesn't work properly but works well enough.
Re: Your job is to deliver code you have proven to work
#4Manual testing as the first step… not very productive imo.
Outside in testing is great but I typically do automated outside in testing and only manual at the end. The loop process of testing needs to be repeatable and fast, manual is too slow
Re: Your job is to deliver code you have proven to work
#5I think the problem is in what “proven” means. People that don’t know any better will just do that all with LLMs and still deliver the giant untested PRs but with some LLM written tests attached.
I vibe code a lot of stuff for myself, mostly for viewing data, when I don’t really need to care how it works. I’m coming around to the idea that outside of some specific circumstances where everyone has agreed they don’t need to care about or understand the code, team vibe coding is a bad practice.
If I’m paying an engineer, it’s for their work, unless explicitly agreed otherwise.
I think vibe coding is soon going to be seen the same way as “research” where you engage an offshore team (common e.g. in consulting) to give you a rundown on some topic and get back the first five google search results. Everyone knows how to do that, if it’s what they wanted they wouldn’t be hiring someone to do it.
Re: Your job is to deliver code you have proven to work
#6there’s one depressing anecdote that I keep on seeing: the junior engineer, empowered by some class of LLM tool, who deposits giant, untested PRs on their coworkers—or open source maintainers—and expects the “code review” process to handle the rest.
Is anyone else seeing this in their orgs? I'm not...
Re: Your job is to deliver code you have proven to work
#7Whole article seems very much all llm generated
Edit: I'm an idiot ignore me.
Re: Your job is to deliver code you have proven to work
#8there’s one depressing anecdote that I keep on seeing: the junior engineer, empowered by some class of LLM tool, who deposits giant, untested PRs on their coworkers—or open source maintainers—and expects the “code review” process to handle the rest. Is anyone else seeing this in their orgs? I'm not...
It's not a new phenomenon. Time was, people would copy-paste from blog posts with the same effect.
Re: Your job is to deliver code you have proven to work
#9As if! :)
Re: Your job is to deliver code you have proven to work
#10Whole article seems very much all llm generated Edit: I'm an idiot ignore me.
Do elaborate, I don't see anything standing out