Live data from Hacker News

Reflections on software engineering in the age of AI

adiamond.me

101–110 of 110 posts

Re: Reflections on software engineering in the age of AI

#101

Writing and coding are not the same thing; coding is a means to an end, since you don’t use the code , you use the software. This means the mechanism by which the code was created is orthogonal to the software as you’d experience it as a user. There are many reasons to curate what goes into the software - for example, if it must be maintainable, if it must conform to standards that cannot be fully codified into the s…

[dead]

Re: Reflections on software engineering in the age of AI

#102

Earlier quoted context omitted.

Regarding 2 Isn't it possible that people who think LLMs are awesome at coding are in fact bad at it themselves, leading to them over estimating the LLMs "skill"? To me it feels like people telling on themselves that they aren't very good

I don’t consider myself an expert, but I’ve been programming for the last 6 years, and of those 6 years I’ve spent almost all my spare time programming during this period except for a 1 year hiatus. This includes personal projects with a decent amount of users, and 1 sold project. I’m not the best programmer, but I wouldn’t say I’m bad at all. Question to you, have you actually used a leading model like Fable when it…

I mean sure. It can get stuff done faster

So can just copying from Stack Overflow, or taking from Open Source repos

There have always been reasons why we didn't prefer to do that in the past, but I guess laundering it through LLMs is fine. And that's just the tip of the ethical ice berg

High volumes of unvetted code is a bad practice. If the code winds up working out fine then congrats you won the slot machine. It's still a bad practice and very, very stupid to become reliant on

And by the way, I had been programming for longer than you have before I even graduated high school, if that matters

Re: Reflections on software engineering in the age of AI

#103
post #52

Machine hater and manual labour worshiper..he thinks he got stupid because he stopped doing if/else and for-loops. Life is full of complexity and it might be helpful to get one level-up in abstraction to try to solve real problems and other people actually care about.

When I started posting on HN, many times I get downvoted. And this an another example, you don't get discussion you just get downvoted.

And it's a good thing, it means I think differently.

The fact is, one could pump literally 10k LOC/Day using LLMs, and in the right hands, those will be quality code, and this is objective observation from someone who has been coding for 20+ years. It almost feels like we have tractors for mechanical thinking, but there are those in the industry who built their entire career and identity on the bottleneck of coding, and those struggle.

But those people will be left out, forgotten. Progress doesn't care about feelings and identities, entire civilizations with their minds collapsed, and buried because they didn't adapt to progress. Do you really think your ego can help you to shelter from that when many before you parished?

Re: Reflections on software engineering in the age of AI

#104

Earlier quoted context omitted.

I don’t have those problems You have to build your architecture modularly so you’re never having to reason about more than the schema and api-contracts for IPC

Well... again, I'm giving the LLM total freedom to destroy what's there and start from scratch. That could nudge it to structure the code base more like that. It would be totally different if I told that to a junior developer. But imo LLMs don't really structure code well or as well as humans could.

> Well... again, I'm giving the LLM total freedom to destroy what's there and start from scratch

Why would you use it like that as a default?

Like the first thing you should do when talking to an LLM about a project is to have it discuss exit criteria, scoping, rules, and managing the smallest thing to ship to get iteration started

Re: Reflections on software engineering in the age of AI

#105

Earlier quoted context omitted.

I don’t consider myself an expert, but I’ve been programming for the last 6 years, and of those 6 years I’ve spent almost all my spare time programming during this period except for a 1 year hiatus. This includes personal projects with a decent amount of users, and 1 sold project. I’m not the best programmer, but I wouldn’t say I’m bad at all. Question to you, have you actually used a leading model like Fable when it…

I mean sure. It can get stuff done faster So can just copying from Stack Overflow, or taking from Open Source repos There have always been reasons why we didn't prefer to do that in the past, but I guess laundering it through LLMs is fine. And that's just the tip of the ethical ice berg High volumes of unvetted code is a bad practice. If the code winds up working out fine then congrats you won the slot machine. It's…

But we aren’t discussing ethics here, we are discussing technical capabilities.

Who said it’s unvetted?

Sure it matters

Re: Reflections on software engineering in the age of AI

#106
post #20

"you haven’t done any of the hard thinking you would normally do in writing the code yourself" It's true, I spend less time solving problems that arise naturally from the process of implementation. But implementation errors have a poor signal-to-noise ratio. For every error that exposes a real design problem there are 10 others that involve routine fixes: type errors, scope issues, import resolution, dependencies. Th…

| type errors, scope issues, import resolution, dependencies. I write code myself and use the LLM to find mistakes then fix them manually. I recommend inverting the conventional wisdom on LLMs: 1. Don't use it to write code. It's a terrible programmer. But it's an intelligent rubber duck and a solid analysis tool. 2. Write the code yourself. It'll go faster than figuring it out as you go along. It's just typing if yo…

Definitely agree. And once you factor in the review time + time spent fixing LLM bugs, I'm pretty sure this inverted process is actually faster than using the LLM to write code

Re: Reflections on software engineering in the age of AI

#107

Earlier quoted context omitted.

Regarding 2 Isn't it possible that people who think LLMs are awesome at coding are in fact bad at it themselves, leading to them over estimating the LLMs "skill"? To me it feels like people telling on themselves that they aren't very good

I don’t consider myself an expert, but I’ve been programming for the last 6 years, and of those 6 years I’ve spent almost all my spare time programming during this period except for a 1 year hiatus. This includes personal projects with a decent amount of users, and 1 sold project. I’m not the best programmer, but I wouldn’t say I’m bad at all. Question to you, have you actually used a leading model like Fable when it…

People are generally bad at judging themselves, and for some reason even worse about judging their agents' output.

I've heard a million people say their LLM workflow produces amazing code. But I have never actually seen the amazing code allegedly being produced. Where are the people saying "I love when my coworkers send me AI-generate PRs"?

Re: Reflections on software engineering in the age of AI

#108

Earlier quoted context omitted.

I don’t consider myself an expert, but I’ve been programming for the last 6 years, and of those 6 years I’ve spent almost all my spare time programming during this period except for a 1 year hiatus. This includes personal projects with a decent amount of users, and 1 sold project. I’m not the best programmer, but I wouldn’t say I’m bad at all. Question to you, have you actually used a leading model like Fable when it…

People are generally bad at judging themselves, and for some reason even worse about judging their agents' output. I've heard a million people say their LLM workflow produces amazing code. But I have never actually seen the amazing code allegedly being produced. Where are the people saying "I love when my coworkers send me AI-generate PRs"?

“Amazing code”… who cares?

that’s like saying a book is only worth reading if each sentence is beautiful

To me I couldn’t care less as long as the overall story is coherent, and I care more about the idea density in the book.

Lord of the rings is a great book because of the ideas, not because Tolkien is the best writer ever.

Same with AI. I couldn’t care less if some of its code is crap, if it is dense with ideas and generally good execution. If it writes crap code sections I can “beautify” myself.

Plus LLMs are only going to improve… they have improved so much since ChatGPT 3. It’s insane.

And the arguments saying they haven’t can’t be taken in good faith

Re: Reflections on software engineering in the age of AI

#109
post #20

"you haven’t done any of the hard thinking you would normally do in writing the code yourself" It's true, I spend less time solving problems that arise naturally from the process of implementation. But implementation errors have a poor signal-to-noise ratio. For every error that exposes a real design problem there are 10 others that involve routine fixes: type errors, scope issues, import resolution, dependencies. Th…

This is half question, half thought experiment: What exactly is it that makes us think „great, I can delegate coding to the agent, and focus on architecture myself“, instead of „great, I can delegate coding to the agent, and I can delegate architecture to the agent, and I can focus on myself“? And how many levels up can you construct this sentence before things go south? What I‘m implying with this question is, of co…

I'd say this is relative to the novelty of the problem domain. At work I'm often solving problems that have fairly standard solutions, e.g. Python scripts to automate build and execution workflows. For this stuff I'm often happy to delegate architecture, and in general, since I spend a lot of time working with legacy code, the solutions the models develop are both clearer and more maintainable than what was already there. The personal project I'm working on (small research compiler for stateless computation) has sparse precedent, and because of this I spend a lot more time hashing out architectural questions with the models. I think of it as a collaborative enterprise.

Re: Reflections on software engineering in the age of AI

#110

Earlier quoted context omitted.

> I see this sentiment often, and I’m honestly not sure where this comes from, as it’s really not been my experience If you see people saying it often, but you are convinced they are just feeling threatened, what AI generated software would point to to say, "Look at this! Definitive evidence that they are just coping!"

>If you see people saying it often, but you are convinced they are just feeling threatened, what AI generated software would point to to say, "Look at this! Definitive evidence that they are just coping!" This is a trap. Anyone who answers this will see the goalposts being moved yet again. 95% of our code at a top in market global fintech is now written by agents. We make it write good code, and it does.

This is very vague. Maybe you could actually name the fintech (or, if that is too sensitive), you can list a few of its competitors?
Post reply on HN