News for hackers. Stuff that matters.

shridharxp

As a junior dev there is this pressure to produce code, add features, and investigate bugs within unprecedented time period. I know whole code base is fking up but i will still add that feature or do a sloppy bug fix without digging deeper.
There are concerns that AI might/will make mistakes. Instead of optimizing for producing perfect code, they think that AI can fix bugs as fast as it produces code and are optimizing for MTTR. Sounds like decision made by people who don't write code regularly, as there is this Architectural drift that happens where you are no longer aware of what's happening in your codebase. As a junior guy I so want this to happen.
Re:OpenAI declares 'code red' as Google catches up in AI race on Thursday December 04, 2025 @09:44PM (#46156299)
ClaudeCode:

- Making functions async without need; it doesn't know the difference between the two or in which scenarios to use them.

- Consistently fails to make changes to the frontend if a project grows above 5000 LOC or a file goes near 1000 LOC.

- The worst part is it lies after making changes.

ChatGPT:

- Fails to implement mid-complex functionality such as scrolling to the bottom when new logs are coming in and not scrolling when the user is checking historical logs.

These models are good at mainstream tasks, the snippets of which you find a lot in repositories. Try to do something off-beat such as algorithmic trading; they fail spectacularly.

Re:OpenAI declares 'code red' as Google catches up in AI race on Wednesday December 03, 2025 @01:25AM (#46130868)
Few months ago, the founder was talking about "AGI" and ridiculous universal basic compute. At this point, I don't even know whom to believe. My first hand experience tells ChatGPT and even ClaudeCode are no where near the expertise they are touted to be. Yet, the marketing by these companies is so immense that you get washed away, you don't know who are agents and who are putting their true opinions.
Re:OpenAI declares 'code red' as Google catches up in AI race on Wednesday December 03, 2025 @01:15AM (#46130820)
There is no moat in selling/renting AI models. They are a commoditized product now. I can't imagine with what thought process did investors poured in such money on OpenAI.
Re:Migrating the main Zig repository from GitHub to Codeberg on Thursday November 27, 2025 @12:07AM (#46065884)
It's okay to bring some "natural" language in technical communication. It feels more humane. All the whitewashed corporate language, riddled marketing bullshit feels so soul dead.
That means you would need to expose your proprietary code and you will be left with no moat.
Re:Cloudflare Global Network experiencing issues on Tuesday November 18, 2025 @09:45AM (#45966832)
It's interesting to see hacker news response time reaching almost 2 seconds for this post.
>The longer someone lives, the more potential value they can contribute to a society.

This is questionable. Highly populous countries have worse living conditions than moderately populous ones, currently.

Isn't it Output Power / Input Power which results Q > 1?
Re:Launch HN: Browser Use (YC W25) – open-source web agents on Tuesday February 25, 2025 @11:22PM (#43180570)
Injecting JS into the page or controlling it using extension APIs is not a secure way to control the browser.
Re:Why Blog If Nobody Reads It? on Monday February 10, 2025 @05:35AM (#42998886)
I think, in the end, it comes down to hope—how hopeful you are that your blogs will turn out to be beneficial one day.
Re:Three Observations on Sunday February 09, 2025 @10:14PM (#42996551)
It would be interesting to consider where humans would find fulfillment when what they have done every day for years is rendered worthless.
Re:Ask HN: Who wants to be hired? (February 2025) on Tuesday February 04, 2025 @06:59AM (#42931262)
Location: Bangalore, India

Remote: Flexible

Willing to relocate: Yes

Technologies: Full Stack (Python, Node.js, Vue, React, Docker, AWS)

Résumé/CV: https://tinyurl.com/resume-sparrow

Email: [email protected]

About me: I have mostly worked at startups building tech from ground up

Re:Discovery Coding on Thursday January 30, 2025 @11:43AM (#42879489)
I use a mixture of both discovery and planning. The problem with pure discovery approach is I sometimes start to code when I am not completely attentive because of deadlines, and if I am working with a larger codebase it is difficult to instantly start writing code because you need some time to understand the context. I always have a text file open all the time where I note down stuff such as: context, plans, ideas, edge cases, conflicts, todos etc.; it serves as a swap memory.