11 ms·
Tip: I very often use AI for inspiration. In this case, I ended up keeping a lot (not all) of the UI code it made, but I will very often prompt an agent, throw
by tptacek 1y ago
Tip: I very often use AI for inspiration. In this case, I ended up keeping a lot (not all) of the UI code it made, but I will very often prompt an agent, throw away everything it did, and redo it myself (manually!). I find the "zero to one" stage of creation very difficult and time consuming and AI is excellent at being my muse.
This right here is the single biggest win for coding agents. I see and directionally agree with all the concerns people have about maintainability and sprawl in AI-mediated projects. I don't care, though, because the moment I can get a project up on its legs, to where I can interact with some substantial part of its functionality and refine it, I'm off to the races. It's getting to that golden moment that constitutes 80% of what's costly about programming for me.
This is the part where I simply don't understand the objections people have to coding agents. It seems so self-evidently valuable --- even if you do nothing else with an agent, even if you literally throw all the code away.
PS
Put a weight on that bacon!
- ramon156 1y agoIt's invaluable if you don't know how to work with it
- sjdjsin 1y ago> This is the part where I simply don't understand the objections people have to coding agents Because I have a coworker who is pushing slop at unsustainable levels, and proclaiming to management how much more productive he is. It’s now even more of a risk to my career to speak up about how awful his PRs are to review (and I’m not the only one on the team who wishes to speak up). The internet is rife with people who claim to be living in the future where they are now a 10x dev. Making these claims costs almost nothing, but it is negatively effecting mine and many others day to day. I’m not necessarily blaming these internet voices (I don’t blame a bear for killing a hiker), but the damage they’re doing is still real.
- tptacek 1y agoI don't think you read the sentence you're responding to carefully enough. The antecedent of "this" isn't "coding agents" generally: it's "the value of an agent getting you past the blank page stage to a point where the substantive core of your feature functions well enough to start iterating on". If you want to respond to the argument I made there, you have to respond to the actual argument, not a broader one that's easier (and much less interesting) to take swipes at.
- sjdjsin 1y agoMy understanding of your argument is: Because agents are good on this one specific axis (which I agree with and use fwiw), there’s no reason to object to them as a whole My argument is: The juice isn’t worth the squeeze. The small win (among others) is not worth the amounts of slop devs now have to deal with.
- tptacek 1y agoSounds like a very poorly managed team.
- JasonSage 1y agoI have to agree. My experience working on a team with mixed levels of seniority and coding experience is that everybody got some increase in productivity and some increase in quality. The ones who spend more time developing their agentic coding as a skillset have gotten much better results. In our team people are also more willing to respond to feedback because nitpicks and requests to restructure/rearchitect are evaluated on merit instead of how time-consuming or boring they would have been to take on.
- bsder 1y ago> My experience working on a team with mixed levels of seniority and coding experience is that everybody got some increase in productivity and some increase in quality. Is that true? There have been a couple of papers that show that people have the perception that they are more productive because the AI feels like motion (you're "stuck" less often) when in reality it has been a net negative.
- roughly 1y agoIn tech? Say it ain't so.
- dingnuts 1y agoin any organization???
- wilg 1y agoNot sure what to tell you, if there's a problem you have to speak up.
- fn-mote 1y agoAnd the longer you wait, the worse it will be. Also, update your resume and get some applications out so you’re not just a victim.
- j45 1y agoMaybe it's possible to use AI to help review the PRs and claim it's the AI making the PR's hyperproductive?
- XenophileJKO 1y agoYes, this. If you can describe why it is slop, an AI can probably identify the underlying issues automatically. Done right you should get mostly reasonable code out of the "execution focused peer".
- austinjp 1y agoIn climate terms, or even simply in terms of $cost, this very much feels like throwing failing on a bonfire. Should we really advocate for using AI to both create and then destroy huge amounts of data that will never be used?
- wahnfrieden 1y agoThe environmental cost of AI is mostly in training afaik. The inference energy cost is similar to the google searches and reddit etc loads you might do during handwritten dev last I checked. This might be completely wrong though
- pastel8739 1y agoI hear this argument a lot, but it doesn’t hold water for me. Obviously the use of the AI is the thing that makes it worthwhile to do the training, so you obviously need to amortize the training cost over the inference. I don’t know whether or not doing so makes the environmental cost substantially higher, though.
- XenophileJKO 1y agoI don't think it is a long term solution. More like training wheels. Ideally the engineers learn to use AI to produce better code the first time. You just have a quality gate. Edit: Do I advocate for this? 1000%. This isn't crypto burning electricity to make a ledger. This objectively will make the life of the craftsmanship focused engineer easier. Sloppy execution oriented engineers are not a new phenomenon, just magnified with the fire hose that an agentic AI can be.
- matwood 1y agoWhat if your coworker was pushing tons of crap code and AI didn't exist? How would you deal with the situation then? Do that.
- chotmat 1y agoIt's not the same because, with AI, they will likely be called anti-ai or anti-progress if they push back against it.
- matwood 1y agoDon't mention AI, just point out why the code is bad. I've had co-workers who were vim wizards and others who literally hunt and pecked to type. At no point did their tools ever come up when reviewing their code. AI is a tool like anything else, treat it that way. This also means that the OPs default can't be AI == bad; focus on the result.
- ttiurani 1y ago> the moment I can get a project up on its legs, to where I can interact with some substantial part of its functionality and refine it, I'm off to the races. [...] This is the part where I simply don't understand the objections people have to coding agents. That's what's valuable to you. For me the zero to one part is the most rewarding and fun part, because that's when the possibilities are near endless, and you get to create something truly original and new. I feel I'd lose a lot of that if I let an AI model prime me into one direction.
- wahnfrieden 1y agoOP is considering output productivity, but your comment is about personal satisfaction of process
- srcreigh 1y agoSurely there are some things which you can’t be arsed to take from zero to one? This isn’t selling your soul; it is possible to let AI scaffold some tedious garbage while also dreaming up cool stuff the old fashioned way.
- ttiurani 1y ago> Surely there are some things which you can’t be arsed to take from zero to one? No, not really: https://news.ycombinator.com/item?id=45232159 https://news.ycombinator.com/item?id=45232159 > This isn’t selling your soul; There is a plethora of ethical reasons to reject AI even if it was useful.
- ipaddr 1y agoThis is an artefact of a language ecosystem that does not prioritize getting started. If you picked php/laravel with a few commands you are ahead of the days of work piping golang or node requires to get to a starting point.
- trenchpilgrim 1y agoI guess it depends on your business. I rarely start new professional projects, but I maintain them for 5+ years - a few pieces of production software I started are now in the double digits. Ghostty definitely aims to be in that camp of software.
- Xss3 1y agoMy trouble is that the remaining 20% of work takes 80% of my time. Ai assistance or not. The edge
- shinycode 1y ago100% agree and LLM does have many blind spots and high confidence which makes it hard to really trust without checking
- jebarker 1y agoJust this week I watched an interview with Mitchell about his dev setup and when asked about using neovim instead of an IDE he said something along the lines of "I don't want something that writes code for me". I'm not pointing this out as a criticism, but rather that it's worth taking note that an accomplished developer like him sees value in LLMs that he didn't see in previous intellisense-like tooling.
- scns 1y agoCognitive Dissonance. Still there, even in the best of us.
- mitchellh 1y agoNot sure exactly what you're referring to, but I'm guessing it may be this interview I did 2 years ago: https://youtu.be/rysgxl35EGc?t=214 https://youtu.be/rysgxl35EGc?t=214 (timestamp linked to LLM-relevant section) I'm genuinely curious because I don't quite remember saying the quote you're saying I did. I'm not denying it, but I'd love to know more of the context. :) But, if it is the interview from 2 years ago, it revolved more around autocomplete and language servers. Agentic tooling was still nascent so a lot of what we were seeing back then was basically tab models and chat models. As the popular quote goes, "When the Facts Change, I Change My Mind. What Do You Do, Sir?" The facts and circumstances have changed considerably in recent years, and I have too!
- jebarker 1y agoIt was this one: https://sourcegraph.com/blog/dev-tool-time-mitchell-hashimoto https://sourcegraph.com/blog/dev-tool-time-mitchell-hashimot... They even used the quote as the title of the accompanying blog post. As I say, I didn’t mean this as a gotcha or anything- I totally agree with the change and I have done similarly. I’ve always disabled autocomplete, tool tips, suggestions etc but now I am actively using Cursor daily.
- mitchellh 1y agoYeah understood, I'm not taking it negatively, I just genuinely wanted to understand where it came from. Yeah this is from 2021 (!!!) and is directly related to LSPs. ChatGPT didn't even get launched until Nov 2022. So I think the quote doesn't really work in the context of today, it's literally from an era where I was looking at faster horses when cars were right around the corner and I had not a damn clue. Hah. Off topic: I still dislike [most] LSPs and don't use them.
- chrisweekly 1y ago100% agreed. > "Put a weight on that bacon!" ?
- simonw 1y agoMitchell included a photograph of his breakfast preparation, and the bacon was curling up on the frying pan.
- tptacek 1y agoThese are great and everybody should own a bunch of them. https://www.thechefspress.com/ https://www.thechefspress.com/
- chrisweekly 1y agoThanks for the tip! (I just ordered a single 13oz one)
- mitchellh 1y agoI ordered one. Thank you!
- chrisweekly 1y agoAh, I see it now. Thanks!
- vunderba 1y ago> the moment I can get a project up on its legs, to where I can interact with some substantial part of its functionality and refine it, I'm off to the races AI is an absolute boon for "getting off the ground" by offloading a lot of the boilerplate and scaffolding that one tends to lose enthusiasm for after having to do it for the 99th time. > AI is excellent at being my muse. I'm guessing we have a different definition for muse. Though I admit I'm speaking more about writing (than coding) here but for myself, a muse is the veritable fount of creation - the source of ideas. Feel free to crank the "temperature" on your LLM until the literal and figurative oceans boil off into space, at the end of the day you're still getting the ultimate statistical distillation. https://imgur.com/a/absqqXI https://imgur.com/a/absqqXI
- harrall 1y agoPeople get into this field for very different reasons. - People who like the act and craftsmanship of coding itself. AI can encourage slop from other engineers and it trivializes the work. AI is a negative. - People who like general engineering. AI is positive for reducing the amount of (mundane) code to write, but still requires significant high-level architectural guidance. It’s a tool. - People who like product. AI can be useful for prototyping but won’t won’t be able to make a good product on its own. It’s a tool. - People who just want to build a MVP. AI is honestly amazing at making something that at least works. It might be bad code but you are testing product fit. Koolaid mode. That’s why everyone has a totally different viewpoint.
- tptacek 1y agoReal subtle. Why not just write "there are good programmers and bad programmers and AI is good for bad programmers and only bad programmers"? Think about what you just said about Mitchell Hashimoto here.
- roughly 1y agoI'm not sure that's a fair take. I don't think it's an unfair statement that LLM-generated code typically is not very good - you can work with it and set up enough guard rails and guidance and whatnot that it can start to produce decent code, but out of the box, speed is definitely the selling point. They're basically junior interns. If you consider an engineer's job to be writing code, sure, you could read OP's post as a shot, but I tend to switch between the personas they're listing pretty regularly in my job, and I think the read's about right. To the OP's point, if the thing you like doing is actually crafting and writing the code, the LLMs have substantially less value - they're doing the thing you like doing and they're not putting the care into it you normally would. It's like giving a painter an inkjet printer - sure, it's faster, but that's not really the point here. Typically, when building the part of the system that's doing the heavy lifting, I'm writing that myself. That's where the dragons live, that's what's gotta be right, and it's usually not worth the effort to incorporate the LLMs. If you're trying to build something that will provide long-term value to other people, the LLMs can reduce some of the boilerplate stuff (convert this spec into a struct, create matching endpoints for these other four objects, etc) - the "I build one, it builds the rest" model tends to actually work pretty well and can be a real force multiplier (alternatively, you can wind up in a state where the LLM has absolutely no idea what you're doing and its proposals are totally unhinged, or worse, where it's introducing bugs because it doesn't quite understand which objects are which). If you've got your product manager hat on, being able to quickly prototype designs and interactions can make a huge, huge difference in what kind of feedback you get from your users - "hey try this out and let me know what you think" as opposed to "would you use this imaginary thing if I built it?" The point is to poke at the toy, not build something durable. Same with the MVP/technical prototyping - usually the question you're trying to answer is "would this work at all", and letting the LLM crap out the shittiest version of the thing that could possibly work is often sufficient to find out. The thing is, I think these are all things good engineers _do_. We're not always painting the Sistine Chapel, we also have to build the rest of the building, run the plumbing, design the thing, and try to get buy-in from the relevant parties. LLMs are a tool like any other - they're not the one you pull out when you're painting Adam, but an awful lot of our work doesn't need to be done to that standard.
- SatvikBeri 1y agoAgree – my personal rule is that I throw away any branches where I use LLM-generated code, and I still find it very helpful because of the speed of prototyping various ideas.
- roughly 1y agoI was talking about this the other day with someone - broadly I agree with this, they're absolutely fantastic for getting a prototype so you can play with the interactions and just have something to poke at while testing an idea. There's two problems I've found with that, though - the first is that it's already a nightmare to convince management that something that looks and acts like the thing they want isn't actually ready for production, and the vibe coded code is even less ready for production than my previous prototyping efforts. The second is that a hand-done prototype still teaches you something about the tech stack and the implementation - yes, the primary purpose is to get it running quickly so you can feel how it works, but there's usually some learning you get on the technical side, and often I've found my prototypes inform the underlying technical direction. With vibe coded prototypes, you don't get this - not only is the code basically unusable, but you really are back to starting from scratch if you decide to move forward - you've tested the idea, but you haven't really tested the tech or design. I still think they're useful - I'm a big proponent of "prototype early," and we've been able to throw together some surprisingly large systems almost instantly with the LLMs - but I think you've gotta shift your understanding of the process. Non-LLM prototypes tend to be around step 4 or 5 of a hypothetical 10-step production process, LLM prototypes are closer to step 2. That's fine, but you need to set expectations around how much is left to do past the prototype, because it's more than it was before.
- benhurmarcel 1y ago> it's already a nightmare to convince management Then just don’t show it to management, no?
- wilsonnb3 1y ago> This is the part where I simply don't understand the objections people have to coding agents. It seems so self-evidently valuable --- even if you do nothing else with an agent, even if you literally throw all the code away. It sounds like the blank page problem is a big issue for you, so tools that remove it are a big productivity boost. Not everyone has the same problems, though. Software development is a very personal endeavor. Just to be clear, I am not saying that people in category A or category B are better/worse programmers. Just that everyone’s workflow is different so everyone’s experience with tools is also different. The key is to be empathetic and trust people when they say a tool does or doesn’t work for them. Both sides of the LLM argument tend to assume everyone is like them.
- ttul 1y agoI concur here and would like to add that I worry less about sprawl when I know I can ask the agent to rework things in future. Yes, it will at times implement the same thing twice in two different files. Later, I’ll ask it to abstract that away to a library. This is frankly how a lot of human coding effort goes too.
- stavros 1y agoI'm the opposite, I find getting started easy and rewarding, I don't generally get blocked there. Where I get blocked, after almost thirty years of development, is writing the code. I really like building things, but they're all basically putting the same code together in slightly different ways, so the part I find rewarding isn't the coding, it's the seeing everything come together in the end. That's why I really like LLMs, they let me do all the fun parts without any of the boring parts I've done a thousand times before.
- tptacek 1y agoIt's funny because the part you find challenging is exactly the thing LLM skeptics tend to say accounts for almost none of the work (writing the code). I personally find that once my project is up on its legs and I'm in flow state, writing code is easy and pleasant, but one thing clear from this thread is everyone experiences programming a little differently.
- stavros 1y agoYeah, definitely. I do agree with the skeptics to a point, as I don't let the LLM write code without reviewing (it makes many mistakes that compound), but I'd still rather have it write a function, review and steer, have it write another, and so on, than write database models myself for the millionth time. It's not that I find it hard, I've just done it so many times that it's boring. Maybe I should be solving different/harder problems, but I don't mind having the LLM write the code, and I'm doing what I like and I'm more productive than ever, so eh!
- tptacek 1y agoI was just talking about this in a chat today, because 'simonw had at some point talked about getting to the point where he was letting go of reviewing every line of LLM code, and I am nowhere close to that point --- I'll take Claude's word on Tailwind classes as long as the HTML looks right, but actual code, I review line-by-line, token-by-token, and usually rewrite things, even if just for cosmetic reasons.
- Jenk 1y agoI explain it to my peers as "exploiting Cunningham's Law[0] with thyself" I'll stare blankly at a blank screen/file for hours seeking inspiration, but the moment I have something to criticise I am immediately productive and can focus. [0]: https://en.wikipedia.org/wiki/Ward_Cunningham#Law https://en.wikipedia.org/wiki/Ward_Cunningham#Law > The best way to get the right answer on the Internet is not to ask a question; it's to post the wrong answer.
- r_lee 1y agoAbout that quote, iirc it's also a technique in Intelligence for getting information from people. You say something stupid and wrong and they will instantly just correct you on the spot and explain why etc. So it works in real life too