Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I don't think AI will make your processes go faster

frederickvanbrabant.com

Post reply on HN
Print view View original

441–450 of 490 posts

Re: I don't think AI will make your processes go faster

#441

Post by rimliu »

bunderbunder wrote: post #378
tombert wrote: post #253

Earlier quoted context omitted.

I've noticed even more than the "hallucinations", just the code is generally quite bad. At least with concurrent and distributed systems stuff (which is really all I know nowadays), it is great at getting a prototype, but the code is generally mediocre-at-best and pretty sub-optimal. I don't know if it's because it is trained on a lot of mediocre and/or buggy code but for concurrency-heavy stuff I've been having to r…

I'm getting the impression that LLMs are just not very good at "reasoning" about time. I have definitely had success getting a coding agent to produce decent concurrent code, but I had to basically lead it by the nose, and I strongly suspect that in most cases it would have taken less time to just do it the old fashioned way.

LLMs are very bad at reasoning. They don't reason, they just backport their "reasoning" to fit what they did.

Re: I don't think AI will make your processes go faster

#442

Post by lomase »

ddosmax556 wrote: post #146

This article assumes that AI only has an impact on the development phase which is certainly not true. It can speed up every part of the step. Including ideation, legal, documentation, development, and deployment. Ideation: Throw ideas back & forth, cross reference with knowledge bases, generate design documents. Documentation: Generate large parts of docs. Development: Clear. Deployment: Generate deployment manifests…

[dead]

Re: I don't think AI will make your processes go faster

#445

Post by gpderetta »

Philip-J-Fry wrote: post #278
angarg12 wrote: post #189

> This exact thing is what software developers have been begging for since the beginning of the profession: Receiving a detailed outline of the problem and what the end result should look like. > This is often the part that slows down software development. Trying to figure out what a vague, title only, feature request actually means. But that is exactly what Software Engineering is!. It's 2026 and the notion that you…

I don't agree. I regularly get pieces of work someone product guy has thought up in an afternoon. They only care about the happy path, and sometimes only part of the happy path. I work for a global company that has to abide by rules and regulations in each country we operate in. The product guy thinks up some feature, we implement the feature, then we're told "actually, we legally aren't allowed to do this in 90% of…

I have only been doing this for the last 20 years, so maybe I don't know, but it seems to me that requirement gathering is trivially software engineering. How can you implement something if you do not know what you need to implement. Figuring out what it need to be built and how to build it are closely linked. A good project manager will help collecting any missing domain knowledge, but ultimately it is on the architect to make sure that all the right questions have been asked.

And it is given that not all requirements will have been discovered before a development start or that they may change during development.

Re: I don't think AI will make your processes go faster

#446

Post by necovek »

graemep wrote: post #422
necovek wrote: post #421

Earlier quoted context omitted.

> ...good PMs which by definition review and write good tickets with a clear explanation of the problem and what they want the solution to be This is where the problem is — such PMs are not "good PMs...by definition". They are usually terrible PMs who start with a solution they envision and work backwards to a customer problem or two. PMs should be able to clearly form a customers' world model, fit that into their bu…

> PMs should be able to clearly form a customers' world model, fit that into their business, and clearly articulate needs to the "builders": UX designers and software engineers What your describing fits a job I did many years ago and my role was distinct from that of the PM and my job title was Business Designer. That was in the context of software that required complex and precise specifications so may not be typica…

Depends on your "business moment" (how mature you are, how complex your product is, etc) if you want to have more specialization or less.

Most software teams benefit from getting daily access to someone who deeply empathises with customers and understands how can their challenges translate into business wins, especially when the problem space is still being explored.

Note that I am referring to product managers, and not project managers (since you bring up projects).

Re: I don't think AI will make your processes go faster

#450

Post by graemep »

necovek wrote: post #446
graemep wrote: post #422

Earlier quoted context omitted.

> PMs should be able to clearly form a customers' world model, fit that into their business, and clearly articulate needs to the "builders": UX designers and software engineers What your describing fits a job I did many years ago and my role was distinct from that of the PM and my job title was Business Designer. That was in the context of software that required complex and precise specifications so may not be typica…

Depends on your "business moment" (how mature you are, how complex your product is, etc) if you want to have more specialization or less. Most software teams benefit from getting daily access to someone who deeply empathises with customers and understands how can their challenges translate into business wins, especially when the problem space is still being explored. Note that I am referring to product managers, and…

That explains it. I interpreted PM as project manager.
Post reply on HN