Live data from Hacker News

The copilot delusion

deplet.ing

31–40 of 214 posts

Re: The copilot delusion

#31

Adapt or die. Keep up on industry trends and learn how to (responsibly) use the tools to be a better programmer, or be unnaturally selected out.

What does 'better' mean in this context? Commercial viability is important if one wants to eat, but doesn't seem to justify the smugness projected...

Re: The copilot delusion

#32

As a preface, I think lots of people will not like this take. A lot of people are going to have to come to the realization that has already been mentioned before but many find it hard to grasp. Your boss, stakeholders, and especially non-technical people literally give 0 fucks about "quality code" as long as it does what they want it to do. They do not care about tests insofar as if it works it works. Many have no cl…

I lost all my snobism about that years ago and I do just follow the paradigm, "does it work". But for some reasons, even with AI I ain't on another level.

And those reasons are, it all collapses very quickly once the complexity reaches an medium amount.

And if I want to rely on things and debug them - I cannot just have a pile of generated garbage, that works as long as the sun is shining. For isolated tasks it works for me. For anything complex, I am faster on my own.

Re: The copilot delusion

#33
post #27

As a preface, I think lots of people will not like this take. A lot of people are going to have to come to the realization that has already been mentioned before but many find it hard to grasp. Your boss, stakeholders, and especially non-technical people literally give 0 fucks about "quality code" as long as it does what they want it to do. They do not care about tests insofar as if it works it works. Many have no cl…

Clean code is nice. Working code is a requirement. You missed the point. AI slop doesn't just fail on point 1. It fails on point 2.

I work in an enterprise company where we just recently got access to use cursor, before that copilot.

We have literally stood up entire services built practically entirely with AI that are deployed right now and consumers are using.

AI does work with competent people behind the wheel. People can't keep hiding behind saying that it always churns out code that doesn't work. We are way past those days. If you don't you will end up losing your job. Theres no way around it. The problem is we may end up losing our jobs either way.

Re: The copilot delusion

#34

I wonder if we'll look back on this period in a couple of years and feel a nostalgic fondness as we think of the fateful moment when people working in software were forced to pull the wool from their eyes and look at the fact that businesses really, really, really dislike losing huge amounts of money paying people to make the software their businesses completely depend on. I mean, I'm guessing that's true. It'd make…

Non-technical business owners have always had deep anxiety about software development. They don’t understand it, it’s very expensive, timelines can explode, and a hack or leak can materially damage their business. A reasonably smart CEO can pretty much understand, in depth, every aspect of their business. But when it comes to tech, which is often the most essential part, they are left grasping, and must rely on the e…

CTO can be a funny position at companies. It sometimes does mean head of engineering and responsible for technical direction at a pretty granular level. But it often also can mean being sort of the public face for the company's technology vision. I've definitely seen companies where the two are largely one and the same. I've also seen companies where the CTO was more the outward-facing vision person.

Re: The copilot delusion

#35

As a preface, I think lots of people will not like this take. A lot of people are going to have to come to the realization that has already been mentioned before but many find it hard to grasp. Your boss, stakeholders, and especially non-technical people literally give 0 fucks about "quality code" as long as it does what they want it to do. They do not care about tests insofar as if it works it works. Many have no cl…

They will demand use of AI tools for "productivity" and then complain when there are bugs in prod without realizing the root cause.

Re: The copilot delusion

#36
> if you want to sculpt the kind of software that gets embedded in pacemakers and missile guidance systems and M1 tanks—you better throw that bot out the airlock and learn.

But the bulk of us aren't doing that... We're making CRUD apps for endless incoming streams of near identical user needs, just with slightly different integrations, schemas, and lipstick.

Let's be honest. For most software there is nothing new under the sun. It's been seen before thousands of times, and so why not recall and use those old nuggets? For me coding agents are just code-reuse on steroids.

Ps. Ironically, the article feels AI generated.

Re: The copilot delusion

#37

I wonder if we'll look back on this period in a couple of years and feel a nostalgic fondness as we think of the fateful moment when people working in software were forced to pull the wool from their eyes and look at the fact that businesses really, really, really dislike losing huge amounts of money paying people to make the software their businesses completely depend on. I mean, I'm guessing that's true. It'd make…

Non-technical business owners have always had deep anxiety about software development. They don’t understand it, it’s very expensive, timelines can explode, and a hack or leak can materially damage their business. A reasonably smart CEO can pretty much understand, in depth, every aspect of their business. But when it comes to tech, which is often the most essential part, they are left grasping, and must rely on the e…

If senior management feels their destiny is not in their control, they're doing it wrong. The best management don't always have the most expertise - but the good ones have an uncanny ability to know when they should defer, when/who to consult with, who to trust, and what to delegate.

Re: The copilot delusion

#38
these tools have no understanding of clean architecture, they are like geeksforgeeks or w3cschools, decades old shitty "tutorials" written by amateurs for amateurs condensed into a chatbot. If you work on cleanly architectured code they can still be useful, they can see the patterns and usually perform better in my experience. But not in a million years will you get to that clean architecture by starting them off from scratch. Keep it turned off until you have a solid foundation would be my advice.

Re: The copilot delusion

#39

As a preface, I think lots of people will not like this take. A lot of people are going to have to come to the realization that has already been mentioned before but many find it hard to grasp. Your boss, stakeholders, and especially non-technical people literally give 0 fucks about "quality code" as long as it does what they want it to do. They do not care about tests insofar as if it works it works. Many have no cl…

They will demand use of AI tools for "productivity" and then complain when there are bugs in prod without realizing the root cause.

They won't blame the AI as the root cause. They will blame you.

This is why I mention you need to be competent enough to understand what is being generated or they will find someone else who does. There's no 2 ways around it. AI is here to stay.

Post reply on HN