If we generate so much code using AI that no one is really looking or reading the code anymore, just verifying end functionality, we can really just skip all that and go straight to assembler, no?

Sure, we could reuse some basic building blocks like implementations of the tcp/ip protocol, http, sockets etc but server frameworks like fastapi are just human friendly abstractions over all that.

Comments URL: https://news.ycombinator.com/item?id=47813874

Points: 14

# Comments: 16

Now, can someone please help me get some data of this Iomega ZIPdrive disc?

I'm also old enough to have started my career learning the rational unified process and then progressed through XP, agile, scrum etc

My process is I spend 2-3 hours writing a "spec" focusing on acceptance criteria and then by the end of the day I have a working, tested next version of a feature that I push to production.

I don't see how using a spec has made me less agile. My iteration takes 8 hours.

However, I see tons of useless specs. A spec is not a prompt. It's an actual definition of how to tell if something is behaving as intended or not.

People are notoriously bad at thinking about correctness in each scenario which is why vibe coding is so big.

People defer thinking about what correct and incorrect actually looks like for a whole wide scope of scenarios and instead choose to discover through trial and error.

I get 20x ROI on well defined, comprehensive, end to end acceptance tests that the AI can run. They fix everything from big picture functionality to minor logic errors.

Sure, I've added no new functionality, but my patterns are clean, signatures become more symmetrical, I take time to think about some odd choices and really figure out what needs to happen.

Leaves me feeling refreshed and with a huge feeling of accomplishment at the end of the day.

Really quite irrational.

Comments URL: https://news.ycombinator.com/item?id=45653828

Points: 2

# Comments: 0

I've been on Ubuntu and PopOS for the last 15 years.

So what about this solution is actually agentic?

Overall, it sounds like you sat down and did a proper business process analysis and automated it.

Your subagents for sure have no autonomy and are just execution steps in a classic workflow except you happen to be calling an LLM.

Does the orchestrating agent adapt the process between invocations depending on the data and does it do so in any way more complex than a simple if then branch?

As someone technical, I start, I build something simple quickly but then start thinking edge cases, exception handling, alternate flows etc and suddenly all that is easier to handle in code directly.

Much of the power of these solutions is the pre made integrations into other systems, and not the flow control to someone technical. Once you realize that, you start looking for integration platforms and not workflow.

How are things on the enterprise side?

Large existing codebases, detailed requirements, lots of interconnected features and dependencies.

Any success stories?

Comments URL: https://news.ycombinator.com/item?id=44583494

Points: 1

# Comments: 0

[bring on the downvotes]

If the governing part at the time of the Nazi trials actually held each and every person involved accountable, would they win the next election?

If a company holds their employees to the actual standards laid out by their policies or guidelines, what would attrition look like? Would they immediately be short staffed critial roles? Would they loose a key employee at a very inconventient time?

These are the real reasons preventing us from holding people accountable.

Imagine having your customers write feature requests for your saas, that immediately triggers code generation and a PR. A virtual environment with that PR is spun up and served to that customer for feedback and refinement. Loop until customer has implemented the feature they would like to see in your product.

Enterprise plan only, obviously.

It's a cop out way to differentiate because you are clearly not comparing apples to apples.

You have a fraction of the features and a fraction of the bug fixes. You are trying to make it sound like you are a 1:1 replacement, when you are not.

Please post again 10 years from now after you have added all the bloat your users request and handled all the edge cases you don't yet understand.

If you are still lighter than a react button...that will be news worthy.