15 ms·
The 70% problem: Hard truths about AI-assisted coding
- cess11 2y ago"Get a working prototype in hours or days instead of weeks" This is nothing new. Algorithmic code generation has been around since forever, and it's robust in a way that "AI" is not. This is what many Java developers do, they have tools that integrate deeply with XML and libraries that consume XML output and create systems from that. Sure, such tooling is dry and boring rather than absurdly polite and submissive, but if that's your kink, are you sure you want to bring it to work? What does it say about you as a professional? As for IDE-integrated "assistants" and free floating LLM:s, when I don't get wrong code they consistently give suggestions that are much, much more complicated than the code I intend to write. If I were to let those I've tried write my code I'd be a huge liability for my team. I expect the main result of the "AI" boom in software development to be a lot of work for people that are actually fluent, competent developers maintaining, replacing and decommissioning the stuff synthesised by people who aren't.
- skydhash 2y agoIt seems most developers that are hyping AI capabilities have never used a proper IDE like IntelliJ IDEA. The productivity boost compared to using a text editor is real. Most experienced programmers that use a text editor subscribe to Unix as an IDE philosophy or have built their own integration using Emacs or what's not. Code generation is not an issue as I have an idea of what to write (If I don't, I should go learning about it instead of writing code). The issue is boilerplate (solved by code snippets and generators), syntax mistakes (highlighter and linting), and bugs (debugger and console log).
- cess11 2y agoProbably true for at least some of them. Having crunched out prototypes by both more formal and ad hoc code generation in a bunch of languages, and also having inherited some mature applications that started that way, I'm not really impressed with the notion of putting down some foundations fast. If you're building something possibly serious, you expect to be hacking away for years anyway. Whether it takes you one or five weekends to make something for recruiting or financing or whatever doesn't actually matter much, it's not a very good sales pitch. I think a lot of the hype is from managerial people, the kind that have been swayed by promises from people selling RAD and "low code" and so on over the decades. And yeah, you can put your non-technical employees to work building things if you want, but when it breaks your profits are at risk anyway and the consultants you need to hire won't be cheap.
- deadbabe 2y agoIf engineers have this problem then people with no engineering skill at all that just want to build some app will be hopeless. The days of no longer needing to hire engineers will never come.
- osigurdson 2y agoI can't imagine anything more awful than using AI as a non-coder to build an application.
- a3w 2y agoSaves the trip to stackoverflow, or provides many valid links to stackoverflow (SO) as a comment or chat answer. So it is not that bad, when comparing it to reading SO directly. But yes, you often get stuck, with the genAI looping in its proposals.
- 2snakes 2y agoOne thing that LLM can do besides generate code is explain complex code too. So that is inherently an upskilling feature.
- a3w 2y agoOur company never adds comments, because the code speaks for itself. And with genAI I can have these comments added in very low time, helping me to get an overview of what happens. But as for the "why are are doing this in the first place" business documentation is usually outside the source code and therefore out of reach of any genAI, for now. As for what senior devs should do when coding: > They're constantly: > Refactoring the generated code into smaller, focused modules > Adding edge case handling the AI missed > Strengthening type definitions and interfaces > Questioning architectural decisions > Adding comprehensive error handling Ain't nobody got time for that! The one girl and other guy that could do this, because they know the codebase, have no time to do it. Everyone else works by doing just enough, which is nearly what TDD dictates. And we have PR code review to scrape up quality to barely get maintainable code. And never overcomplicate things, since writing code that works is good enough. And by the time you want to refactor a module three years later, you would want to use another data flow style or library to do the work altogether.
- shireboy 2y agoI think this is a pretty clear-eyed view. I've been a developer for 25 years. I use Copilot every day now exactly the way he describes. I get it to do XYZ, then use it to refactor what it just did or clean it up myself. Every now and then it goes sideways, but on the whole it saves me time and helps me focus on business problems more than ceremony.
- causal 2y agoIf you can read code fast, it's very useful. I think this may be the biggest reason it's more helpful to seniors than juniors. It's easy for a senior engineer to forget how exhausting it is for juniors to read code. I can glance at a page of code from Claude and tell pretty quickly if it's what I want. So it's useful to me if it's right more than half the time. For a junior this is definitely worse than just trying to write it themselves, they would learn more that way and come out less exhausted.
- joshdavham 2y ago> While engineers report being dramatically more productive with AI, the actual software we use daily doesn’t seem like it’s getting noticeably better. I would disagree with this. There are many web apps and desktop apps that I’ve been using for years (some open source) and they’ve mostly all gotten noticeably better. I believe this is because the developers can iterate faster with AI.
- agentultra 2y agoI think the real problem is that people are misunderstanding what programming is: understanding problems. The hard truth is that you will learn nothing if you avoid doing the work yourself. I'm often re-reading ewd-273 [0] from Dijkstra, The programming task considered as an intellectual challenge. How little distance have we made since that paper was published! His burning question: > Can we get a better understanding of the nature of the programming task, so that by virtue of this better understanding, programming becomes an order of magnitude easier, so that our ability to compose reliable programs is increased by a similar order of magnitude? I think the answer AI-assistants provide is... no. Instead we're using the "same old methods," Dijkstra disliked so much. We're expected to rely on the Lindy effect and debug the code until we feel more confident that it does what we want it to. And we still struggle to convince ourselves that these programs are correct. We have to content ourselves with testing and hoping that we don't cause too much damage in the AI-assisted programming world. Not my preferred way to work and practice programming. As for, "democratizing access to programming..." I can't think of a field that is more open to sharing it's knowledge and wisdom. I can't think of a field that is more eager to teach its skills to as many people as possible. I can't think of any industry that is more open to accepting people, without accreditation, to take up the work and become critical contributors. There's no royal road. You have to do the work if you want to build the skill. I'm not an educator but I suspect that AI isn't helping people learn the practice of programming. Certainly not in the sense that Dijkstra meant it. It may be helping people who aren't interested in learning the skills to develop software on their own... up to a point, 70% perhaps. But that's always been the case with low-code/no-code systems. [0] https://www.cs.utexas.edu/~EWD/ewd02xx/EWD273.PDF https://www.cs.utexas.edu/~EWD/ewd02xx/EWD273.PDF Update: Added missing link, fixed consistent mis-spelling of one of my favourite researchers' name!
- falcor84 2y ago>The hard truth is that you will learn nothing if you avoid doing the work yourself. I understand where you're coming from, but this would imply that managers, product people and even tech leads don't learn anything from working on a project, which would strongly go against my experience. It is absolutely possible to delegate implementation details but stay close to the problem.
- tippytippytango 2y agoYou break through the 70% barrier by writing detailed spec and architecture documents. Also tests that define behavior. Those go in every request as you build. Don’t ask an LLM to read your mind.
- jccalhoun 2y agoI've done a little bit of javascript but I was doing a hobby project with a raspberry pi. That meant learning python and linux. Chatgpt was invaluable in completing the project because although I know the very basics I don't know the libraries. The script Chatgpt provided based on my description included several libraries that are super common and useful but I had never heard of. So instead of trying to reinvent the wheel or endlessly googling until I found something that sort of did what I wanted and then looked at that code, I was able to get something that worked. Then I could adjust it and add features.
- sebastianz 2y agoThat is indeed very helpful and feels magical. But the fact remains that if you did all those things yourself, although much slower and more frustrating at times, you would have learned and remembered more, and would have understood the task, the libraries, and your own program on a deeper level. Which many times is the actual point of the exercise.
- codedokode 2y agoOut of curiosity, I tried to use freely available LLM to generate simple Python tests. I provided the code and specified exactly what requirements I want to be tested. What I found out is that initially it generates repetitive, non-DRY code so I have to write propmts for improvement like "use parametrization for these two tests" or "move this copy-paste code into a function". And it turns out that it is faster to take initial version of code and fix it yourself rather than type those prompts and explain what you want to be done. And worse, the model I was using doesn't even learn anything and will make the same mistakes the next time. But, this was a generic LLM, not a coding assistant. I wonder if they are different and if they remember what you were unhappy with the last time. Also LLMs seem to be good with languages like Python, and really bad with C and Rust, especially when asked to do something with pointers, ownership, optimization etc.
- m3kw9 2y agoThere is a problem with AI coding where you want to let it write as much as possible, but when it hits a wall where is just looping back to the same error, you would have to roll up the sleeve and get dirty. As AI is able to write more complex code, the skill of the engineer must increase to go in when necessary to diagnose the code it wrote, if you can’t, your app is stuck to the level of the AI
- mediumsmart 2y agoI agree with the article. I am in the camp "learning with the AI" and the main task is getting young foolish Einsteiborg to use simple things and go step by step without jabbering about the next steps or their alternative etc. I also have to go in blocks to get a usable whole and git branch saves the day every time. But its also really nice and you learn so much.
- commandlinefan 2y agoAn axiom that was true even before pervasive AI: If you're using the computer to do something you don't have time to do yourself, that's good. If you're using the computer to do something you don't understand, that's bad.
- enum 2y agoAcademic studies are finding the same thing. Although there are a handful of beginners who are great at prompting, when you study beginning programmers at scale, you find that the mostly struggle to write prompts and understand why things go wrong. Here is one of several example studies: https://dl.acm.org/doi/full/10.1145/3613904.3642706 https://dl.acm.org/doi/full/10.1145/3613904.3642706
- hazrmard 2y agoI agree with the author. My work involves designing simulations for control. Yesterday, I asked GPT-4o to write a python-only simulation for a HVAC system (cooling tower, chiller on the water side, and multiple zones with air handling units on the air side). It wrote functions to separately generate differential equations for water/air side, and finally combined them into a single state vector derivative for integration. Easy peasy, right? No. On closer inspection, the heat transfer equations had flipped signs, or were using the wrong temperatures. I'd also have preferred to have used structured arrays for vectors, instead of plain lists/arrays. However, the framework was there. I had to tweak some equations, prompt the LLM to re-write state vector representations, and there it was! AI-assisted coding is great for getting a skeleton for a project up. You have to add the meat to the bones yourself.
- crakhamster01 2y agoThis tracks with my experience as a more "senior" dev using Copilot/Cursor. I can definitely see these tools being less useful, or more misleading, for someone just starting out in the field. One worry I have is what will happen to my own skills over time with these tools integrated into my workflow. I do think there's a lot of value in going through the loop of struggling with -> developing a better understanding of technologies. While it's possible to maintain this loop with coding assistants, they're undoubtedly optimized towards providing quick answers/results. I'm able to accomplish a lot more with these coding assistants now, but it makes me wonder what growth I'm missing out on by not always having to do it the "hard" way.
- leebriskcyrano 2y agoThe 70% framing suggests that these systems are asymptotically approaching some human "100%," but the theoretical ceiling for AI capabilities is much higher. > the future isn't about AI replacing developers - it's about AI becoming an increasingly capable collaborator that can take initiative while still respecting human guidance and expertise. I believe we will see humans transition to a purely ceremonial role for regulatory/liability reasons. Airplanes fly themselves with autopilot, but we still insist on putting humans at the yoke because everyone feels more comfortable with the arrangement.
- mnky9800n 2y agoI find that irritating and iterative problem of watching the ai fail over and over helps me understand the problem I’m trying to solve. But that led me to believe none of the promises of Altman et al are connected to reality.
- DesiLurker 2y agoI mostly use it to get past the drudge-work. often I have mental blocks in doing super mundane things that 'just need to be done'. AI is good at those super defined and self contained problems ATM & thats okey for me. anything that requires deep expertise or knowledge base it falls flat IMO. It can change if the AI can get its own sandbox to try and learn with experimentation. IDk that has its own implications but its one way to improve its understanding of a system.
- AIorNot 2y agoI absolutely think this is a spot on analysis btw and ties well into my own experience with LLM based coding. However one difference between these tools and previous human developed technologies is these tools are offering direct intelligence sent via the cloud to your environment. That is unprecedented. Its rather like the the first time we started piping energy through wires. Sure it was clunky then, bit give it time. LLMs are just the first phase of this new era.
- artificialLimbs 2y agoI built a full featured Laravel crud app recently with probably 10 tables, auth, users, ‘beautiful’ tailwind styling, dark/light mode button, 5 different tabs, history function, email functions. 99% ai generated code. I almost didn’t even look at the code, just run some tests and make sure I’ve got functionality and no unexpected ‘normal’ bugs like min/max/0. Took me 15-20 hours with Windsurf. Windsail. Waveshark. Whatever that nice VSCode ai editor skin is called (completely forgettable name btw). It’s completely blowing my mind that this is even possible. There were of course some frustrating moments and back/forth (why did you change the layout of the list? I just wanted a filter…), but overall phenomenal. Deploying it shortly because if it dies, so what, this was a free job for a farm stand anyway. =)
- johann8384 2y agoToday an AI tool let me build a new tool from scratch. I published it to a git repo with unit tests, great coverage, security scanning, and pretty decent documentation of how the tool works. I estimate just coding the main tool would have been 2 or 3 days and all the other overhead would have been at least another day or two. So I did a week of work in a few hours today. Maybe it did 70%, maybe it did 42.5%, either way it was a massive improvement to the way I used to work.
- rini17 2y agoCan you please capture the process next time? Make a screencast? Apparently not everyone is in tune with AI. It keeps doing something else than they want, resulting in frustration. Happens to me often.
- johann8384 2y agoYeah, there was one point where I told it there was an error and it said "Oh, my mistake, I'll publish the update to the repository" and I said "Did you publish the update, I don't see it" and it said "yes" and I said "How did you do that? I don't think you can use those tools" and it said "Oh yeah, my mistake, I am not able to access external tools like github and make changes for you but I can share the changes with you" I am paraphrasing of course. It was a little comical that all the sudden it switched from typing the artifacts to trying to tell me it committed the changes directly.
- MrMan 2y ago[dead]
- AlienRobot 2y agoI realized today that the average person types half my typing speed. I wonder if this factors in people's tendency to use AI? Typing takes too long so just let the AI do it? In some ways, I'm not impressed by AI because much of what AI has achieved I feel could have been done without AI, it's just that putting all of it in a simple textbox is more "sleek" than putting all that functionality in a complex GUI.
- Frederation 2y ago100% agreed.Much of my time involved with AI during the course of work is used delegating for better output and reevaluating everything it does. 70% sounds right. And I have even told AI, dont act like an over-eager 14 year with ADHD. Which I was/am still, myself. XD
- mediumsmart 2y agoIn my experience the AI provides 170% of the solution and the hard part is getting rid of the shitty 70% it has been trained on.
- ilrwbwrkhv 2y ago> In other words, they're applying years of hard-won engineering wisdom to shape and constrain the AI's output. This. Junior devs are f*cked. I don't know how else to say it.
- zamfi 2y agoI've been wondering about this. They'll still get that hard-won engineering wisdom that comes from watching AI agents code badly, deploy it, and have it fail---as much as we'd like it to be otherwise, engineering wisdom often comes from experience, not just from hearing stories from senior devs. I guess the question is whether this role is still employable.
- HellDunkel 2y agoBut isnt this a very ineffective way of learning from second-hand mistakes?
- tstrimple 2y agoIt's not really second hand. The LLM didn't merge and deploy the code. The developer did. The LLM won't fix the bad push, the developer will have to. This is no different than a more junior dev copying and pasting a snippet from Stack Overflow that they partially understand without accounting for the edge cases or sometimes even their specific use case. Experience comes from failure and LLMs will help you fail and potentially help you recover from it just like any other resource developers have been using for years.
- HellDunkel 2y agoThe novelty is that AI made the „pasting code“ work somehow whereas copy and paste from stack overflow did not. Before merge and deploy you need to run the code. If it fails what do you do? search a new snippet on stack overflow? or paste the error into the ai? This seems like a completely inefficient way of learning to me.
- 2y ago
- miftassirri 2y agoThis feels like skipping the tutorial in a game
- pcwelder 2y ago> 3. The "Trust but verify" pattern To add on to this point, there's a huge role of validation tools in the workflow. If AI written rust code compiles and the test cases pass, it's a huge positive signal for me, because of how strict rust compiler is. One example I can share is https://github.com/rusiaaman/color-parser-py https://github.com/rusiaaman/color-parser-py which is a python binding of rust's csscolorparser created by Claude without me touching editor or terminal. I haven't reviewed the code yet, I just ensured that test cases really passed (on github actions), installed the package and started using it directly.
- aiono 2y agoI checked the code. The code validates that values are within the range https://github.com/rusiaaman/color-parser-py/blob/ec739c80ba73edbf8d01a322ac3d38814f95de39/src/lib.rs#L14 https://github.com/rusiaaman/color-parser-py/blob/ec739c80ba... but the library it wraps already does validation and a lot more checks (see range check here: https://docs.rs/csscolorparser/latest/src/csscolorparser/parser/mod.rs.html#449 https://docs.rs/csscolorparser/latest/src/csscolorparser/par...). So the code generated by AI has unnecessary checks that will never be visited.
- fmbb 2y agoDid you write the test cases?
- User23 2y agoTDD is, in my opinion and based on some tentative forays, one of the areas where LLM assisted coding really shines.
- pcwelder 2y agoNo everything in the repo is AI generated.
- dkdbejwi383 2y agoHow can you trust the tests? Sure, they may pass, but they could be testing for the incorrect outcome.
- leeoniya 2y agoi usually say this about all assistive ai, not just coding. you still need a close-to-expert human at the keyboard who can detect hallucinations. a great answer can only be deemed so by someone already very knowledgeable in the technical / deep subject matter.
- fifilura 2y agoIsn't this similar to how for example the food industry has developed. You don't need a baker to make bread, but you need a "food technician" to monitor the bread making machines.
- chii 2y agoand yet the food industry hasn't mastered the sourdough. So you end up with factory white bread - amazingly fluffy, stores for unusually long without going stale and very shelf stable without refrigeration, has little to no nutrition, but tastes amazing. it's because the type of product that is suited for industrialized, low skill but high automation production is a very different product from artisanal production (which is what sourdough is - you can't easily use automation for sourdough). I reckon ai coded products will have similarities.
- Ringz 2y ago> but tastes amazing What’s amazing to one person might not be to another. Is it rich and nuanced like a well-made, hand-crafted German sourdough bread (hard to get these days, nearly impossible in South Africa), or just overly sweet and processed?
- nitwit005 2y agoMaking a lot of sandwich bread didn't somehow made them incapable of making other breads. They'd happily mass produce whatever type of bread people wanted, with whatever method people wanted, if they'd pay for it. Instead people by the cheap sandwich bread.
- fifilura 2y ago
- zerop 2y agoI fear that in the goal of going to "manual coding" to "fully automated coding", we might end up in the middle, where we are "semi manual coding" assisted by AI which needs different software engineer skill.
- jansan 2y agoWe have always been there since compilers were invented. AI is just another (rather big) iteration. Previous steps included API documentation tools, syntax highlighting, checking and formatting tools, refactoring tools, linters, and of course Stackoverflow :)
- paradite 2y agoYeah that's what I had in mind from the very beginning. In fact I built a tool [1] that applies this principle for semi automated coding. It uses LLMs for generating code, but leave the context selection and code editing for human to complete. I find this a sweet spot between productivity and quality of output. [1] https://prompt.16x.engineer/ https://prompt.16x.engineer/
- kgilpin 2y agoI like how you put the context and prompts into the foreground. In so many tools, it’s invisible. We all know that context and prompts are there - the operation of LLMs is well known. Yet tools try and hide this and pretend that they are magic, instead of exposing control points and handles for the developer to use.
- bravetraveler 2y agoProbably right. Feedback loops are interesting. An anecdote: I spent my career learning how to do things well... so that I could eventually be promoted to try to do it by proxy. Infinitely more difficult, garners no interest. Now we're all disappointed. I'm not learning, just forgetting. Entirely different skills - exercise is important.
- Yoric 2y agoYeah, a bit like the many frameworks that were supposed to make development trivial in X, many of which ended up being quite useful, but remained _additional_ skills to master in an ever-growing list of things we need to know to be able to do our jobs.
- globalise83 2y ago"the actual software we use daily doesn’t seem like it’s getting noticeably better" Honestly, this seems like a straw man. The kind of distributed productivity tools like Miro, Figma, Stackblitz, etc. that we all use day-to-day are both impressive in terms of what they do, but even more impressive in terms of how they work. Having been a remote worker 15 years ago, the difference in what is available today is light-years ahead of what was available back then.
- cma 2y agoStill less impressive in a lot of ways than Englebart's mother of all demos.
- Nevermark 2y agoI expect Englebert would have been astounded by real time text generation, faster than he could read, of a first pass draft of a Supreme Court brief involving a James Bond incident uncovering a pharmaceutical plot to undermine the biosphere via a constitutional loophole written in Dr. Seuss prose, with the humor of Monty Python. Or that he could get successive improvements in the form of real time collaboration with the model. It is true that a tool that isn’t as reliable as an expert won’t impress an expert. Even if it’s better/faster on 99% of varied tasks for any given human, for fast response output. “It still isn’t great”, by an experts standards. But as humans, each of our task/field span of expertise or informed amateur fluency is terrifyingly limited compared to the broad awareness of fields and subjects that these models incorporate. And they are crazy impressive in terms of how much better they have become, qualitatively and quantitatively, inexpensive (to deploy/use) and available, in a few years.
- cma 2y agoI was talking about the collaborative productivity tools, not language models.
- jansan 2y agoIIRC all those mentioned products have been around before the AI craze started. Can you explain how bringing up these products is not a straw man by itself?
- deleted 2y ago[deleted]
- roenxi 2y agoThis article looks like a case of skating to where the puck is. Over the next 2-4 years this will change - the rate of improvement in AI is staggering and these tools are in their infancy. I would not be confident betting a career on any those patterns holding. It is like people hand-optimising their assembly back in the day. At some point the compilers get good enough that the skill is a curio rather than an economic edge.
- chewz 2y agoAgree. We will be probably designing projects differently and use different tools in order to make them more manageable by AI code assistants.
- shinycode 2y agoWe said the same thing 3 years ago and we still have errors on basic questions. I don’t know where people get their estimation from ? Their intuition ?
- downWidOutaFite 2y agoI think the tech chauvinism (aka accelerationism) comes from the crypto-hype era and unfortunately has been merged into the culture wars making reasonable discussion impossible in many cases.
- BlueTemplar 2y ago"Culture wars" aside, how is it different from the turn of the millennium dot-com bubble hype accelerationism ? EDIT : http://www.antipope.org/charlie/blog-static/fiction/accelerando/accelerando-intro.html http://www.antipope.org/charlie/blog-static/fiction/accelera... Especially the first 3 chapters, set in the near future (which is ~today now).
- Nevermark 2y agoSo if something takes more than 3 years it doesn’t happen? Models have been getting better, at a fast clip. With occasional leaps. For decades. The fact that we are even talking about model coding limitations greatly surpasses expectations for 2024 from just a few years ago. Progress in steps & bounds isn’t going to stop short of a global nuclear winter.
- fxtentacle 2y ago"AI is like having a very eager junior developer on your team" That's a perfect summary, in my opinion. Both junior devs and AI tools tend to write buggy and overly verbose code. In both cases, you have to carefully review their code before merging, which takes time away from all the senior members of the team. But for a dedicated and loyal coworker, I'm willing to sacrifice some of my productivity to help them grow, because I know they'll help me back in the future. But current AI tools cannot learn from feedback. That means with AI, I'll be reviewing the exact same beginner's mistakes every time. And that means time spent on proofreading AI output is mostly wasted.
- tempodox 2y ago> very eager junior developer Not only that, but one who is infected with terminal Dunning-Kruger syndrome. Of all the things that LLMs are great at, demonstrating a hopeless case of Dunning-Kruger has to be at the very top.
- steveBK123 2y agoIt's interesting because it actually endangers the junior dev job market in the present. And in the near future the mid/senior level will have no replacements as we've under-hired juniors and therefore don't have a pipeline of 5YOE/10YOE/etc devs who have learned to stop being juniors.
- mtrovo 2y agoI see it the other way, assuming these tools keep on improving you will only need junior developers as there's no point on knowing more than the basics about programming to get a job done.
- jeremyjh 2y agoYou say this like it is incremental improvement needed, or that we can see signs of a major shift in capabilities coming. Yes, people are predicting this. People were predicting personal travel by jet pack at one point as well.
- demirbey05 2y ago> the actual software we use daily doesn’t seem like it’s getting noticeably better. %100 agree, I am testing o1 for some math problems. I asked that to prove convolution of two gaussian is gaussian. It gave me 3 page algebraic solution it is correct but not elegant nor good. I have seen more ingenious solution. These tools are really good at doing something but not good at doing like expert human as they claimed.
- OhNoNotAgain_99 2y ago[dead]
- senko 2y ago> I asked that to prove convolution of two gaussian is gaussian. [The solution] is correct but not elegant. The goalposts are moving at the speed of light. A few years ago if someone told us that you could ask a computer to compose a poem, critique a painting, write a professional 360 performance review based on notes, design a website based on a napkin sketch, prove convolution theorems, ... they would say that's a stretch even for sci-fi. Now we have a single LLM that can do all of that, at some level of quality. Yet, the solutions are not elegant enough, the code not completely correct, the design is not inspired and the poem is "slop".
- demirbey05 2y agotbh I am ai skeptic, I think agi cannot be achieved by only with deep learning, but really impressed with o1. I didn't like 4o, but I am against only overhype.
- blharr 2y agoEh, I mean that proof is all around in its training set. It's a fundamental, basic theorem in probability. You can put the same thing into a search engine and get a better solution, for [example](https://jeremy9959.net/Math-5800-Spring-2020/notebooks/convolution_of_gaussians.html https://jeremy9959.net/Math-5800-Spring-2020/notebooks/convo...) Nobody's saying that these aren't fascinating, just that it's not looking like their models are getting significantly better and better as all the hype wants you to believe. Transformers + huge data set is incredible. But literally we've scraped all the data on the web and made huge sacrifices to our entire society already
- neilwilson 2y agoAgain one of the few advantages of having been round the sun a few more times than most is this isn’t the first time this has happened. Packages were supposed to replace programming. They got you 70% of the way there as well. Same with 4GLs, Visual Coding, CASE tools, even Rails and the rest of the opinionated web tools. Every generation has to learn “There is no silver bullet”. Even though Fred Brooks explained why in 1986. There are essential tasks and there are accidental tasks. The tools really only help with the accidental tasks. AI is a fabulous tool that is way more flexible than previous attempts because I can just talk to it in English and it covers every accidental issue you can imagine. But it can’t do the essential work of complexity management for the same reason it can’t prove an unproven maths problem. As it stands we still need human brains to do those things.
- bambax 2y agoWhere AI really really shine is to help an engineer get proficient in a language they don't know well. Simon Willison says this somewhere and in my experience it's very true. If you can code, and you understand the problem (or are well on your way to understanding it), but you're not familiar with the exact syntax of Go or whatever, then working with AI will save you hundreds of hours. If you can't code, or do not (yet) understand the problem, AI won't save you. It will probably hurt.
- fatnoah 2y ago> Where AI really really shine is to help an engineer get proficient in a language they don't know well. I used GitHub Copilot in a project I started mostly to learn Go. It was amazing. I spent not so much time fiddling around with syntax, and much more time thinking about design.
- heelix 2y agoSo very much this. As I was learning Rust, I'd ask what the equivalent was for a snippet I could create in Java. It is funny. I look at the Java code provided by prompts and go meh. The Rust code looks great. I realize this is probably due to 1) me being that junior level in Rust or 2) less legacy crap in the training model. I'm sure it is both, with more of the former as I work from working to beautiful code.
- ChicagoDave 2y agoThis mirrors my own experiences with Claude with one caveat. GenAI can get deeper into a solution that consists of well known requirements. Like basic web application construction, api development, data storage, and oauth integration. GenAI can get close to 100%. If you’re trying to build something that’s never been done before or is very complex, GenAI will only get to 50% and any attempt to continue will put you in a frustrating cycle of failure. I’m having some further success by asking Claude to build a detailed Linear task list and tackling each task separately. To get this to work, I’ve built a file combining script and attaching these files to a Claude project. So one file might be project-client-src-components.txt and it contains all the files in my react nextjs app under that folder in a single file with full file path headers for each file. We’ll see how deep I get before it can’t handle the codebase.
- causal 2y agoIn general it can get further the better the design/interfaces are. I find that if you can define your problem with a really clean set of interfaces, it can generally implement them perfectly. Most of the real thinking work is at the interfaces anyway, so this makes sense. But for a really tricky logic problem, accurately explaining it in English to an LLM might be less natural than just writing the code.
- xxs 2y ago>GenAI will only get to 50% and any attempt to continue 50% seems exceeding high for 'never done before'.
- HDThoreaun 2y agoEven things that have never been done before are mostly made up of tasks that have been done many times.
- nopurpose 2y agoWhich tool can actually help coding and refactoring, not just autocomplete? Copilot plugin for Jetbrains IDE can only suggest source to copy paste or at most replace single snippet I selected. What I'd like to do is to ask "write me libuv based event loop processing messages described by protobuf files in ./protos directory. Use 4 bytes length prefix as a frame header" and then it goes and updates files in IDE itself, adding them to CMakeLists.txt if needed. That would be an AI assisted coding and we can then discuss its quality, but does it exist? I'd be happy to give it a go.
- paradite 2y agoYes. I built a tool exactly for this use case: a coding task that requires context from multiple files and edit across multiple files. Do let me know what you think. https://prompt.16x.engineer/ https://prompt.16x.engineer/
- nopurpose 2y agosimilar to how we have language servers for code analysis and syntax highlighting, we need to have AI assist server, so that any IDE can pull instruction what to do with what file
- paradite 2y agoI think the problem is it's hard to monetize such a piece of software. It would need to come from either open-source or sponsored by big tech company. Maybe MCP is a step in that direction? https://www.anthropic.com/news/model-context-protocol https://www.anthropic.com/news/model-context-protocol
- iamflimflam1 2y agoTake a look at the latest version of cursor - its composer tool does exactly this.
- fragmede 2y agoaider does this, plus there's an architect mode to help think through, well, architectural aspects
- gronky_ 2y agoI think the same can be said about AI-assisted writing… I like the ideas presented in the post but it’s too long and highly repetitive. AI will happily expand a few information dense bullet points into a lengthy essay. But the real work of a strong writer is distilling complex ideas into few words.
- WOnderFullGOnzo 2y ago[dead]
- javaunsafe2019 2y agoI already wrote on another thread already but do it again: copilot failed me for any serious task. Let it be refactoring of a bit more complex Java method or iac code. Everytime there are hidden quirks and failures that make it easier to just do it myself instead of searching for the needle for minutes…. This combined the fact that ai already hitting a wall in terms of scaling gives a good outlook what’s its predictive future seems to be: successful in the far future when we have quantum computing or the like…
- HDThoreaun 2y agoIve found copilot quite good at writing tests. Describe the test, let copilot generate, review + fix up takes me around 5 minutes versus 20 or so to write them myself most of the time. Also very good at scaffolding out new features, basically an extremely quick junior as the article said.
- mrweasel 2y agoPersonally I've been mostly avoiding using AI tools, but I have friends and colleagues who do use or have used LLMs, at least they've tried to. Those who seems to get the best results asks for a prototype or framework for how to do something. They don't expect to use the AI generated code, it's purely there as inspiration and something they can poke at to learn about a problem. Most seems to have a bad experience. Either the LLMs doesn't actually know much, if anything about the subject, and makes up weird stuff. A few colleagues have attempted to use LLMs for generating Terraform, or CloudFormation code, but have given up on making it work. The LLMs they've tried apparently cannot stop making up non-existing resources. SRE related code/problems anecdotally seems to do worse than actual development work, but it feel to like you still need to be a fair good developer to have much benefit from an LLM. The wall we're hitting may be the LLMs not actually having sufficient data for a large set of problems.
- skydhash 2y ago> Those who seems to get the best results asks for a prototype or framework for how to do something. That's what GitHub and sample projects are here for. And the examples would be working ones. No need to train a model for that.
- foo42 2y agoI worry about 2 main pitfalls for junior devs, one more tractable than the other. Firstly there is the double edged sword of AI when learning. The easy path is to use it as a way to shortcut learning, to get the juice without the pressing, skipping the discomfort of not knowing how to do something. But that's obviously skipping the learning too. The discomfort is necessary. On the flip side, if one uses an llm as a mentor who has all the time in the world for you, you can converse with it to get a deeper understanding, to get feedback, to unearth unknown unknowns etc. So there is an opportunity for the wise and motivated to get accelerated learning if they can avoid the temptation of a crutch. The less tractable problem is hiring. Why does a company hire junior devs? Because there is a certain proportion of work which doesn't take as much experience and would waste more senior developers time. If AI takes away the lower skill tasks previously assigned to juniors, companies will be less inclined to pay for them. Of course if nobody invests in juniors, where will the mid and senior developers of tomorrow come from? But that's a tragedy of the commons situation, few companies will wish to invest in developers who are likely to move on before they reap the rewards.
- Vegenoid 2y agoAnother reason companies hire juniors is because they cannot find/afford seniors. The demand that stems from this reason will increase over time when companies are not hiring "enough" juniors (because if we aren't hiring juniors we aren't making more seniors, so they become increasingly scarce and expensive).
- deleted 2y ago[deleted]
- jajko 2y agoYes but then as all else this can easily be cyclic. Too few seniors to hire and they ask for ridiculous packages? Well lets train some of them in house, its not like the situation will explode overnight. Weird times ahead, probably, but we will be fine, mostly.
- 0xDEAFBEAD 2y agoI think the tragedy of the commons problem for juniors has already existed for some time. Previously, companies were reluctant to hire juniors because they had a tendency to leave after a year or two, once you finished training them up. AI will just make the situation a lot worse.
- iamflimflam1 2y agoI have friends who are building products from scratch using tools like Cursor. It’s impressive what someone who is already an expert developer can do. What I don’t see (yet) are these tools delivering for non developers. But this as just a matter of time. I see a lot of devs who appear to be in a complete state of denial about what is happening. Understandable, but worrying.
- shadowmanif 2y agoI am not a professional software engineer but LLMs have showed me how hard software engineering is at the overall level of a system. For me, it feels like being a magic skilled carpenter with the ability to build a giant building, but with no idea what architects do to make blue prints. Just end up building a useless mess of wood and nails that eventually gets burned down. I am actually not impressed by the new o1 at all. I think we might be in denial of how progress is slowing down.
- WesleyJohnson 2y agoI've been a dev for 20 years. I recently watched a YT video of a non-developer putting together an iOS app, from scratch, using Cursor Composer. I can't vouch for the legitimacy of his claim at not being a dev, but some of the language used to describe things definitely suggested they were not. Anyway, it was pretty impressive. I decided, having never used Swift and having never built a 2D iOS game, to give it a go myself. In just a couple of evenings, I have a playable prototype that I confidently say would've taken me weeks to get to on my own. And I'm learning Swift. Reading open-source projects or Swift tutorials is one thing , but seeing code written to satisfy a prompt request - that provides an entirely different level of early comprehension.
- tatersolid 2y ago> But this as just a matter of time. Confidently stated without any evidence. All AI proponents use this phrase repeatedly. Yet I still can’t get these tools to stop making up APIs that don’t exist, and they hey constantly produce face-palm security issues like hard-coded credentials and SQL injection.
- 9rx 2y ago
- senko 2y agoGreat article, Addy gets to the core of it and explains in a non-biased (pro or con), non-hype way. The examples, patterns and recommendations match what I've seen pretty well. I've been working on an agentic full-app codegen AI startup for about a year, and used Copilot and other coding assistance tools since it was generally available. Last year, nobody even thought full app coding tools to be possible. Today they're all the rage: I track ~15 full codegen AI startups (what now seems to be called "agentic coding") and ~10 coding assistants. Of these, around half focus on a specific niche (eg. resolving github issues, full-stack coding a few app types, or building the frontend prototype), and half attempt to do full projects. The paradox that Addy hints at is that senior, knowledgeable developers are much more likely to get value out of both of these categories. For assistants, you need to inspect the output and fix/adapt it. For agentic coders, you need to be able to micromanage or bypass them on issues that block them. However, more experienced developers are (rightly) wary of new hyped up tools promising the moon. It's the junior devs, and even non-developers who drink the kool aid and embrace this, and then get stuck on 70%, or 90%... and they don't have the knowledge or experience to go past. It's worse than useless, they've spent their time, money, and possibly reputation (within their teams/orgs) on it, and got nothing out of it. At the startup I mentioned, virtually all our dev time was spent on trying to move that breaking point from 50%, to 70%, to 90%, to larger projects, ... but in most cases it was still there. Literally an exponential amount of effort to move the needle. Based on this, I don't think we'll be able to see fully autonomous coding agents capable of doing non-toy projects any time soon. At the same time, the capabilities are rising and costs dropping down. IMHO the biggest current limit for agentic coding is the speed (or lack of) of state-of-the-art models. If you can get 10x speed, you can throw in 10x more reasoning (inference-time computing, to use the modern buzzwords) and get 1.5x-2x better, in terms of quality or capability to reason about more complex projects.
- thenoblesunfish 2y agoThinking that AI assistants are going to make programmers better, as opposed to just faster, is liking thinking hiring a paralegal is going to make you a better lawyer, or hiring a nanny is going to make you a better parent, etc. It's helpful, but in terms of offloading some things you could do yourself.
- eru 2y agoYes, by offloading the lower skilled tasks, you can spend more time on the higher skilled tasks, and be a better parent or chef or lawyer or programmer. Just like I'm a better programmer in Rust than in C, because I offloaded lots of mundane checking to the compiler.
- player1234 2y agoReally sad stuff dude, crowbaring Rust into everything.
- 4dregress 2y agoAs a Jetbrains AI user I think it’s great. I don’t ever use the code completion functionality in fact it can be a bit annoying. However asking it questions is the new Google search. Over the last couple of years I’ve noticed that the quality of answers you get from googling has steeply declined, with most results now being terrible ad filled blog spam. Asking the AI assistant the same query yields so much better answers and gives you the opportunity to delve deeper into said answer if you want to. No more asking on stack overflow and having to wait for the inevitable snarky response. It’s the best money I’ve spent on software in years. I feel like Picard asking the computer questions
- skydhash 2y ago> I’ve noticed that the quality of answers you get from googling has steeply declined Are you asking for solutions to a specific problem or searching for information on the problem? I still don't have issue with search engines, because I mostly use it for the latter, treating it as an index of the internet (which is what they really are). And for that AI is a huge step down, because I can't rely on the truthfulness of their replies.
- sota_pop 2y agoI’m actually surprised this isn’t talked about more… it has been great interrogating the docs of unfamiliar frameworks (and giving me good references on where to go in the actual docs for more info). A better mouse trap to “Google-like search” has been my exact experience as well. I once scoffed at a blog article by an “ai communicator” (right around a year ago) entitled something like “chatgpt vs google search, what’s the difference?” I have also found myself using chatgpt as a Google search because the results of actually searching Google have been so unsatisfactory (even after I found myself appending “reddit” as the suffix to every google search for the better part of 2 years). I can’t tell whether this says more about the AI or Google.
- mg 2y agoCurrently, this is my favorite test prompt for AI coding tools: Make a simple HTML page which uses the VideoEncoder API to create a video that the user can download. So far, not a single AI has managed to create a working solution. I don't know why. The AIs seem to have an understanding of the VideoEncoder API, so it seems it's not a problem of not having the infos they need. But none comes up with something that works.
- raincole 2y agoI'd like to share a particular case showing the necessity of verifying AI's work. Yesterday I asked o1-preview (the "best" reasoning AI on the market) how could I safely execute untrusted JavaScript code submitted by the user. AI suggested a library called vm2, and gave me fully working code example. It's so good at programming that the code runs without any modifications from me. However, then I looked up vm2's repository. It turns out to be an outdated project, abandoned due to security issues. The successor is isolated-vm. The code AI gave me is 100% runnable. Had I not googled it, no amount of unit tests can tell me that vm2 is not the correct solution.
- 01100011 2y agoMost of my time isn't spent coding. It's spent designing, discussing, documenting, and debugging. If AI wrote 90% of my code for me I'd still be busy all day.
- eru 2y ago> It's spent designing, discussing, documenting, and debugging. Why not let AI handle these tasks as well?
- bigstrat2003 2y agoIt can't even write code well enough to be useful. Let's not get ahead of ourselves.
- xxs 2y agoAI debugging - a good one!
- eru 2y agoChatGPT can be surprisingly helpful making suggestions for what to do about error messages. (Which is one small area of debugging.)
- zkry 2y agoAs an experiment, at my work I've stopped using all AI tools and went back to my pre-ai workflows. It was kind of weird at difficult at first, like maybe having to drive without GPS navigation, but I feel like I'm essentially at pre-AI usage speed. This experiment made me think, maybe most of the benefit from AI comes from this mental workload shift that our minds subconsciously crave. It's not that we achieve astronomical levels of productivity but rather our minds are free from large programming tasks (which may have downstream effects of course).
- lexandstuff 2y agoGood article. A very relevant paper worth reading is Programming as Theory Building: https://pages.cs.wisc.edu/~remzi/Naur.pdf https://pages.cs.wisc.edu/~remzi/Naur.pdf. Programming is not just about producing a program, it's about developing a mental model of the problem domain and how all the components interact. You don't get that when Claude is writing all your code, so unless the LLM is flawless (which it likely never be on novel problems), you won't understand the problem enough to know how to fix things when they go wrong.
- danielbln 2y agoFeels like a bit of a broad statement. I tend to request chunks of work/code that I place into my codebase. I still know what it's for and where it goes, I just care a lot less about the specific implementation details of the chunk, as long as it's typed and passed the smell test. To me it's just one higher rung on the abstraction latter. But it goes to show how difficult it is to discuss this stuff, because depending on model, IDE, workflow, experience/seniority, intuition etc. LLM assisted developmental might look very different in each instance.
- black_13 2y ago[dead]
- jillesvangurp 2y agoI'm replacing things that I used to delegate to juniors with generated code. Because it's quicker and better. And there's a category of stuff I used to not bother with at all that I'm also taking on. Because I can get it done in a reasonable time frame. It's more fun for me for sure and I definitely am more productive because of it. My feeling is that this stuff is not bottle-necked on model quality but on UX. Chat is not that great of an interface. Copy pasting blobs of text back to an editor seems like it is a bit monkey work. And monkey work should be automated. With AI interactions now being able to call functions, what we need is deeper integration with the tools we use. Refactor this, rename that. Move that function here. Etc. There's no need for it to imagine these things perfectly it just needs to use the tools that make that happen. IDEs have a large API surface but a machine readable description of that easily fits in a context window. Recently chat gpt added the ability to connect applications. So, I can jump into a chat, connect Intellij to the chat and ask it a question about code in my open editor. Works great and is better than me just copy pasting that to a chat window. But why can't it make a modification for me? It still requires me to copy text back to the editor and then hope it will work. Addressing that would be the next logical step. Do it such that I can review what it did and undo any damage. But it could be a huge time saver. And it would also save some tokens. Because a lot of code it generates is just echoing what I already had with only a few lines modification. I want it to modify those lines and not risk hallucinating introducing mistakes into the rest, which is a thing you have to worry about. The other issue is that iterating on code gets progressively harder as there's more of it and it needs to regenerate more of it at every step. That's a UX problem as well. It stems from the context being an imperfect abstraction of my actual code. Applying a lot of small/simple changes to code would be much easier than re-imagining the entire thing from scratch every time. Most of my conversations the code under discussion diverges from what I have in my editor. At some point continuing the conversation becomes pointless and I just start a new one with the actual code. Which is tedious because now I'm dealing with ground hog day of having to explain the same context again. More monkey work. And if you do it wrong, you have to do it over and over again. It's amazing that it works but also quite tedious.
- Quothling 2y ago> The other issue is that iterating on code gets progressively harder as there's more of it and it needs to regenerate more of it at every step. You might know this already, but if you're using the chatbot interfaces it helps quite a bit to prompt it with something along the lines of "only give me the bits that changed". There is nothing worse than fine-tuning a tiny bit of some code you didn't bother writing yourself only to have the bot give you an entire prompt's worth of code.
- est 2y agoI always treat various AI tools like an intern. You have to oversee it.
- xxs 2y agoBut unlike interns they don't learn from their (or anyone else's) mistakes.
- riazrizvi 2y agoIn coding but also generally with deep expertise in other fields too, I find LLMs help only if you deal with them adversarially. You can quickly get its stabs on the current state of topics or opinions about your ideas, but you’ve got to fight it to get to better quality. It tends to give you first the generic crap, then you battle it to get to really interesting insights. Knowing what to fight it on is the key to getting to the good stuff.
- habinero 2y agoIt sounds like you're asking it to rephrase until it spits out something you like. That's not "the good stuff", you've just turned it into robo-Clever Hans.
- riazrizvi 2y agoSo for example if it responded with something like this to me, I would point out Clever Hans the trick horse that answered math questions was giving the specific answer the trainer provided, but an LLM is yielding well-structured content it was trained on that me the prompter is trying to get out that I haven’t seen before. I know what it does not look like and I know pieces of what it does. So no not the same. Then the LLM would take this and redo its answer. Unlike internet strangers, who usually respond unhelpfully to adversarial exchanges because they tend to be too fixated, for my purposes, on finding ways to make their original answer right.
- habinero 2y agoThe owners of Clever Hans thought he could really do math, too.
- danielbln 2y agoThis is it. Always be distrustful and challenge the LLM. That along with providing ample context and guiding it towards a solution you have in mind at a high level is the trick to make LLM assisted coding work really well. And once you're in that groove, and have built the intuition on what works and what doesn't and where you should challenge or follow up, productivity really goes up quite a bit. To quote Memento: "Don't believe his lies." (though thankfully, as the LLMs advance, this is becoming less of an issue. Claude 3.5 Sonnet V2 is already a huge step ahead compared to where it once was).
- remoquete 2y agoPretty much everything the author describes applies to technical writing, too. Thinking AI can replace senior writers is delusional.
- prmph 2y agoJust tried ScreenshotToCode, Bolt.New, and v0. ScreenshotToCode wants me to pay for a subscription, even before I have any idea of its capabilities. V0 keeps throwing an error in the generated code, which the AI tries to remedy, without success after 3 tries. Bolt.New redirects to StackBlitz, and after more than an hour, there are still spinners stuck on trying to import and deploy the generated code. Sounds like snake oil all around. The days of AI-enabled low-/no-code are still quite a while away, I think, if at all feasible.
- stuaxo 2y agoThat's not a 70% problem, that's an "after the first 90% is done you only gave the other 90 to do" These people were never at 70% in the first place. The article also misses experts using this to accelerat themselves at things they are not expert in.
- mdavid626 2y agoWell, it turns out there is no free lunch. One will not get far without understanding the code and creating a mental model of it.
- csbartus 2y agoThis fully resonates with me. When the AI boom started in 2022 I've been already focused on how to create provably, or likely correct software on budget. Since then, I've figured out how to create correct software fast, on rapid iteration. (https://www.osequi.com/ https://www.osequi.com/) Now I can combine productivity and quality into one single framework / method / toolchain ... at least for a niche (React apps) Do I use AI? Only for pair programming: suggestions for algorithms, suggestions for very small technical details like Typescript polymorphism. Do I need more AI? Not really ... My framework automates most part of the software development process: design (specification and documentation), development, verification. What's left is understanding aka designing the software architecture, and for that I'm using math, not AI, which provides me provably-correct translatable-to-code-models in a deterministic way. None of these will be offered by AI in the foreseeable future
- factsaresacred 2y agoThe clue is the name of the tools: "co-pilot". Assistants that work best in the hands of someone who already knows what they're doing, removing tedium and providing an additional layer of quality assurance. Pilot's still needed to get the plane in the air. But even if the output from these tools is perfect, coding isn't only (or even mainly) about writing code, it's about building complex systems and finding workable solutions through problems that sometimes look like cul de sacs. Once your codebase reaches a few thousand lines, LLMs struggle seeing the big picture and begin introducing one new problem for every one that they solve.
- blixt 2y agoI see the same things as Addy, though I'm not 100% sure it's something new happening because of AI assistants. I started learning programming in the late nineties as a 9-year-old sitting at a library paying 10 NOK for an hour of internet access (the librarians were sweet and "forgot" how long I was sitting at the computer because they saw how much I was enjoying it). And I did the exact same thing described in this article: I grabbed whatever code I could that did something, didn't know how to debug it, and at best I could slightly tweak it to do something slightly different. After a few years I got better at it anyway. I started pattern matching, and through curiosity I found out what more senior developers were doing. Maybe the fact that I was just a kid made this different, but I guess my point is that just because AI can now write you a code file in 10 seconds, doesn't mean your learning process also got faster. It may still take years to become the developer that writes well-structured code and thinks of edge cases and understands everything that is going on. When I imagine the young people that will sit down to build their own first thing with the help of AI, I'm really excited knowing that they might actually get a lot further a lot faster than I ever could.
- skydhash 2y agoI started learning how to program around 2010. I was learning Blender and wanted to use its game engine. It was python based, so after running a few examples found on some forum, I downloaded the Python interpreter and some tutorials/book. Maybe my learning process is different, but I don't enjoy spending a day tweaking things in the hope I will get something. I much prefer getting a book on the subject and start learning how to do it instead.
- blixt 2y agoYeah that's fair, I think everyone has their own learning style. I mostly felt a need to respond with a slightly more optimistic view on what this new technology means for juniors, in particular responding to the part that "[AI coding tools] can actually impede learning." Though to be fair to Addy, I like his advice on how to approach this, those are good tips.
- thiht 2y ago> While engineers report being dramatically more productive with AI Where are these people in real life? A few influencers or wannabes say that on Twitter or LinkedIn, but do you know actual people in real life who say they’re "dramatically more productive with AI"? Everyone I know or talked to about AI has been very critical and rational, and has roughly the same opinion: AIs for coding (Copilot, Cursor, etc.) are useful, but not that much. They’re mostly convenient for some parts of what constitutes coding.
- 946789987649 2y agoI've always been a backend developer, but started my own company about a year ago. From that, I had to become full stack and AI has helped dramatically with the learning and implementation. There's a lot of things which would have simply just taken far longer to understand or fix with just stackoverflow/google. And that's just on the coding side, even more on the actual start up side!
- marcosdumay 2y agoOh, I know of a handful of people that report this. The quality of their work has gone down dramatically since they started being "faster", and it needs rewriting way more often than before LLMs existed. But they do claim they are now much faster.
- 946789987649 2y agoNot sure how you gleaned that it was lower quality from my post? You can move fast and still do things well if you set it up correctly at the start. Specifically with things like automated testing and so on.
- marcosdumay 2y ago> Not sure how you gleaned that it was lower quality from my post? I dunno. I responded to a post that had a clear question. Either my reply is on the wrong post, or the text changed.
- empiricus 2y agoI think we underestimate how indefatigable the AI is. It is very hard for a person to keep producing code on demand, again and again and again.
- h1fra 2y agoThe scary part is that in a few years, senior programmers who started their career with AI won't have the capacity to keep the AI in check.
- 0xDEAFBEAD 2y ago>I've seen this firsthand: >Error messages that make no sense to normal users >Edge cases that crash the application >Confusing UI states that never got cleaned up >Accessibility completely overlooked >Performance issues on slower devices >These aren't just P2 bugs - they're the difference between software people tolerate and software people love. I wonder if we'll see something like the video game crash of 1983. Market saturation with shoddy games/software, followed by stigmatization: no one is willing to try out new apps anymore, because so many suck.
- noisy_boy 2y agoUsing AI-assisted coding is like using an exoskeleton to lift things. Makes your life easy, you gradually lose strength because your muscles work less and when it breaks down, you break down too, because you no longer have the strength you used to have.
- kraftman 2y agoAs someone who often forgets the syntax for a for loop in a language I've been using every day for 10 years, for some people the muscles were never there in the first place.
- figassis 2y agoMy problem with ai assisted coding is if I use it to scaffold hundreds of lines of code, I the. Need to review every single line because bugs can be so subtle. Imagine for example Go’s for loop reference footgun. I really don’t know if AI can handle these cases or similar cases that I don’t know about. So this is potentially more work than just writing for scratch. Using it as a smarter autocomplete is where I see a lot of productivity boosts. It replaces snippets, it completes full lines or blocks, and because verifying block likely takes less time than writing it, you can easily get a 100%+ speed up.
- HenriTEL 2y agoThat's far from my experience. Last time I used chatgpt it added many comments to explain the generated code and also attached rough explanatory text. You can also just ask more details about something, or to list other approaches, explain tradeoffs, etc. You can also ask for general questions to help you get started and find a good design. To me it's about asking the right questions no matter the level of experience. If you're junior it will help you ramp up at a speed I could no imagine before.
- dkdbejwi383 2y ago> Last time I used chatgpt it added many comments to explain the generated code and also attached rough explanatory text. Good way to know if a PR opened by someone on your team was LLM generated is to look for inane explanatory comments like // Import the necessary dependencies import { Foo } from './Foo'; // Instantiate a new Foo const myFoo = new Foo(); // return the expected value return true; I don't know if this is because a lot of the training materials are blog posts and documentation, which are focused more on explaining how trivial cases work than "real world" examples, and thus the LLM has "learned" that this is what real code looks like.
- cess11 2y agoI would not leave it to junior developers to ask the right questions. In my experience, from a few juniors I've cooperated with, they get absolutely awful code from ChatGPT. Things like manual opening and closing of files with unnecessary exception handling that crudely reimplements stuff that's already in the standard library and should have been a one-liner, and sure, ChatGPT will happily suggest explanatory comments and whatnot, but it's like copying in material from a reference manual, i.e. provocatively useless. To me it also seems like they don't learn much from it either. They've made much more progress from a bit of mentoring and heavy use of REPL:s and similar shells.
- mrtksn 2y agoIt's great doing things that has a tutorial or something out there, it falls flat when you try to do something slightly novel that doesn't have tons of articles on how to do it. In my case, ChatGPT was quite useful to bootstrap a code for working with Apple's CoreAudio and sucked when I tried to make it write some code to do something special to my app. I got the same experience when I tried to hammer out an app dealing with cryptography(certificates, keys etc) and was only able to solve the issue through Apple's developer forms thanks to to the infamous eskimo1. Then some Russian dev who had the same issues appeared and gave me the full context. ChatGPT, Claude etc. can't put together a Swift code that does things usually not done in Swift but done in C and can't leverage its knowledge on Cryptography to help itself out. I had similar problems in nodeJS etc. too, the instance you do anything non-standart AI falls apart and you can see how stupid actually is.
- estebarb 2y agoSomething that concerns me the most is how are we going to train new generations. I teached a course at the university and many students just chatgpted everything, without any critical thinking. It doesn't matter how many times you showed that it invented assembly instructions or wxwidgets functions, they insist on cheating. I even told them the analogy of going to the gym: you lift with your own strength, you don't use a crane. And of course, it is evident when you receive students that don't know what is a function or that cannot complete simple exercises during a written test. We learned by reading, lots of trial and failing, curiosity, asking around, building a minimal reproducible bug for stackoverflow... they (the ones that rely only on chatgpt and not their brain) cannot even formulate a question by themselves.
- hbn 2y agoIf they can't pass the tests it seems like the problem solves itself. Even if they do manage to cheat their way to a degree, they won't be able to pass interviews or fulfill their role at a job.
- badsectoracula 2y ago> It doesn't matter how many times you showed that it invented assembly instructions or wxwidgets functions, they insist on cheating. Wouldn't the compiler complain in those cases anyway? Why not let them burn through their mistakes, that's how people tend to learn best :-P
- crnkofe 2y agoSurely not 70% but like 5-10% might be a better ballpark figure. Coding or generating with LLMs is just part of the problem and always the fastest part of software building. All the other things eat disproportionately larger amount of time. QA, testing, integration testing, making specs, dealing with outages, dealing with customers, docs, production monitoring etc. etc. It would be cool if we get AI involved there especially for integration testing though. I really dislike the entire narrative that's been built around the LLMs. Feels like startups are just creating hype to milk as much money out of VCs for as long as they can. They also like to use the classic and proven blockchain hype vocabulary (we're still early etc.). Also the constant antropomorphizing of AI is getting ridiculous. We're not even close to replacing juniors with shitty generated code that might work. Reminds me of how we got "sold" automated shopping terminals. More convenient and faster that standing in line with a person but now you've got to do all the work yourself. Also the promises of doing stuff faster is nothing new. Productivity is skyrocketing but burnout is the hot topic at your average software conference.
- ongytenes 2y agoI'm afraid this is going to be like the calculator event. Before electronic calculators happened, kids at least learned to mentally do basic math. Now we have whole generations incapable of making change without a calculator. I met a graduate who claimed 32 ÷ 2 was too difficult because 32 is too big to work with mentally. I believe code development AI is going to lead to a whole generation of mediocre coders.
- tuetuopay 2y agoAh the calculator, the strawman of every maths teacher. And yet, are we worse at math than the previous generations? I'm not so sure. Pretty quickly math becomes toying with letters and not numbers, and unless the calculator has an algebraic engine, it won't help you. We can focus in more important aspects of math, like actually understanding the concepts. However, to me this will be worse than the calculator: LLM pretend to understand the problem, and can offer solutions. On the other hand, you don't get a calculator with a CAS until late university (if you ever get one). Calculators don't pretend to be more than what they are. But IMHO we'll still get the benefits of calculators: let the humans focus on the difficult tasks. I don't want to write the full API scaffolding for the tenth time. I don't want to write the boilerplate for that test framework for the 15th time. LLMs are good at those tasks, let them do it!
- BlueTemplar 2y agoI don't know what happened to that student (I'm guessing not in a field commonly using math ??), but my experience as a student with access to calculators during exams (sometimes even to programmable calculators) is that they were just slowing you down for simple calculations, resulting in a worse grade if abused, especially since you have to lay out all the intermediate steps anyway. (And you just figure out with experience what the cutoff for 'simple' is, and it raises as you keep getting better at it, just as the bar to what is considered a minimum 'intermediate step' raises with the class level.) But then also the importance of using a calculator as one of the tools to double-check your work (because they make much less mistakes) should not be underestimated... whereas the situation seems to be opposite with LLMs !
- 2y ago
- mrjin 2y ago70%, REALLY? My personal experience was that at least 50% of the time, Copilot backfires, sometimes the proposed code was beyond ridiculous. Thus I had to disable it.
- nbittich 2y agoThe article itself sounds like written by chat gpt :D
- goap98 2y agonot sure