Live data from Hacker News

Ask HN: Where is the programming profession going?

news.ycombinator.com

181–190 of 206 posts

Re: Ask HN: Where is the programming profession going?

#181

My personal experience: writing code has always been the easy part. AI does most of that now. Understanding the problem and the existing system well enough to design the right solution, even with AI assistance, is a higher cognitive load. I’m doing a lot more of that lately. I’m more productive, but also more tired. This may be due in part to the breadth of what my team owns, which makes my day a bit more context-swi…

> My personal experience: writing code has always been the easy part. AI does most of that now. That's exactly why I don't have AI writing my code. It is doing the easiest part of the job (making symbols appear in the text), which isn't actually valuable to me. A good tool should help me to do hard things, not easy things.

I seem to only have discussions about architecture with it.

Re: Ask HN: Where is the programming profession going?

#182
Yes, this is the direction I am observing. Ironically, I don't think anybody is happy about it and we keep saying that it is a tool and you need to verify everything, etc, but this is not what is happening.

There are tons of people who produce questionable code at a rate which is not really compatible with a thoughtful review, we have people with little engineering background pushing their changes (although there is a large pushback against that as the results are really bad even short term), as you said, there is an explosion of LLM-generated tests.

As soon as someone writes a next-level harness which tightly iterates based on the spec/plan and/pr pioneers some sort of acceptance criteria format that works, I think at that point SWE job will completely change. We are not there yet but probably not that far off.

Re: Ask HN: Where is the programming profession going?

#183
imho programmers should jump into completely unrelated jobs (even unskilled labor) and discover how gawd awful all of the software is. Nothing gives you the user perspective like being the user. Then dogfood your way into a highly specialized product.

There is an amazing amount of complexity in even the dumbest looking job. It takes decades to see all the strange edge cases.

The people planning the work never have the full picture, if they did the job themselves the layer of management above fails to imagine it. The people doing the manual work match the offer by inability to explain how to ride a bicycle and not understanding how to plan or budget.

Re: Ask HN: Where is the programming profession going?

#184
post #104
post #54

Earlier quoted context omitted.

> little to no automated tests I'm still amazed people don't achieve extremely high test quality, since you get tests "for free" now. One of the limitations of testing were always that people "design" things so they're hard to test. And then they argue "This can't be tested", or "Refactoring this for testing is not worth it." It is now. Yet, I work on codebases with no tests and lots of yolo co-authoring.

You get quantity of tests, but the tests are not good quality by default, at all.

I’m not sure how you can say something general about the quality of tests unless you mean by simply prompting “make tests” or similar.

Yes, I’ve experienced that those tests succeed, and the app still breaks trivially on first run.

What I mean is: you design the tests. You analyse patterns. You insist on making testable code (average code by humans isn’t, so neither is average code by LLMs unless you specify testability as a design constraint.

One way to get testable code is to mock all interfaces. This is usually expensive, but not difficult for an AI, because you can set the success criterion to be interface exactness of your mock for a series of plausible and somewhat extensive interactions.

The tests you can make with AI are as good as you can make them otherwise, you just save time doing them, which should justify making more extensive testing.

Re: Ask HN: Where is the programming profession going?

#185

Earlier quoted context omitted.

> Who hires “pure solution modelers”? I don’t think I’ve ever encountered someone like that. They're called Business Analysts, sometimes simply Analysts, and that's effectively their job - come up with a spec and give it to the software engineers.

I've never seen BAs execute that way. I don't think that is an accurate description of their role and its link to SWEs.

Agreed; typically (especially if a client is involved) I’ve seen creative and dev define and articulate spec and expected behavior, and BA documents it. Then, when it inevitably evolves, BA’s job is to capture the changed spec. The artifact is simply documentation as a client deliverable that’s then often never referenced or used for anything outside of maybe complaining that a feature doesn’t do what the spec claimed, or maybe as context when the client takes their whole project to another vendor to be rebuilt from scratch lol

Re: Ask HN: Where is the programming profession going?

#186

Every software developer will be a manager of one or more AI agents. Managing AI agents will turn out to be surprisingly similar to managing people, except for the drama, illness, and tragedy.

I'm downvoting you because: 1) You're anthropomorphizing AI. 2) You're devaluing your fellow human/professional. >except for the drama, illness, and tragedy. "By using AI we get all the benefits of workers but with none of the drawbacks of humans." I hear this spiel most often about junior engineers on HN, and it really pisses me off. It just comes off as incredibly anti-social.

I was trying to make a different statement. Everyone will need to become a manager, even ICs. But in the past, many engineers shied away from management, for various reasons. Now, it will need to change.

Managing people is hard because of all the things that make us human. Managing AI will be simpler as we won't need to deal with some of those things.

Separately,

> "By using AI we get all the benefits of workers but with none of the drawbacks of humans."

To be fair, I did not write that. You are projecting your thoughts on my post.

Re: Ask HN: Where is the programming profession going?

#187
compare this to Electronic engineering, we are not making chips by hand, It is impossible to squeeze too many transistors in such a small space, we just create the circuit designs. I believe writing the code is heading in the same direction as well, you don't write too much code now, but you have to design the architecture and connect things. But it does not mean that you don't need to understand the code, now of all the times people who understand code are more important. Many below par devs will loose jobs for sure.

Re: Ask HN: Where is the programming profession going?

#188
Programming models will continue to improve; in the foreseeable future, enterprises will rely less and less on human programmers to write code.

If you are still interested in programming, do not waste time delving deep into the code itself; instead, spend time understanding requirements and the market. The combination of an individual and Codex will be the optimal approach to programming.

Re: Ask HN: Where is the programming profession going?

#190
I think of AI as an intelligent partner that took away the boring stuff and give me the real design decisions. The expectations of clients have changed but most of the code I have seen written by AI does the work but AI do ignore somethings that matter in scaling. In my company actually boss thinks he is a programmer now with claude but writes too much error prone code which I think mainly not because of claude because non technical person giving generic commands. For me in near future the need for proper engineers is still very high.
Post reply on HN