Hacker Newsnew | past | comments | ask | show | jobs | submit | duendefm's commentslogin

Having a powerful language going fully anti AI is awesome because you will have something to compare against in the future. If we conclude that it was a bad decision, it shall die. If it wasn't, we will learn a lot.

Haven't considered this take and makes me wonder how we might be slowly losing baselines to compare against (other than targeting years old releases as a sledgehammer guarantee).

I tried the game and in some seconds noticed I can kick the enemies forever if I put them close to the left corner. I'm feeling now that I'm the AI exploiting bugs.

That's kind of audacious, for a php programmer

Yeah, when I saw PHP it made me question everything.

It's the language I hate to write the most.


A preference in language doesn't discount the idea.

I can say the same about any opinion of an LLM 'programmer'

It's just data processing. If it wasn't trained to speak like a human you would have no problems in seeing it's a machine. Try to ask it to create a joke about some topics and you can easily see it's just a robot. The lesson to take is not that we are not prepared to assume other type of intelligence is "real". The lesson here is that we humans fool ourselves when we are exposed to some kinds of data. Remember, you can simulate an AI with pen an paper, and the speed at which you simulate it doens't make a difference, it's provably deterministic (a part from randomness that doesn't change a thing for the point). Good look in proving that humans are deterministic.


nowadays people will have it like either full AI or no AI, guess which one this project went like


I think that what we really need is a global label that makes it easy to see if a project blocks AI contributions and modified software licenses that make it explicit that AI agents cannot use the code of software under that license. I'm up for that. It sucks to try to find a stable, meticulously handcrafted tool and getting spammed with vibecoded stuff.


F* Rust. If AI finds every bug then Rust choice is pointless for those who still care about programming. Real programmers that like to code have no reason to lose time with Rust. Let's leave Rust for vibe coders.


Real programmers write raw machine code, using a magnetized needle and a steady hand.


Leftism, progressism or wtv tries to remove all social value from individuals for their beliefs. Leftists tried to make the world lose respect for people like J. K. Rowling, Elon Musk and recently DHH. If some people say something that is not illegal but is deemed to be offending by leftists, they go tribal gang on that person and try to devalue all they work. I myself prefer to live in a world where people is free to express their thoughts even if they are being retarded at it.


Then they start to use their "well-earned" money to bend the world to their worldview, but "it's their right!". Of the people you bring up, i've been affected just by Musk (his endeavours are a net contributor for global warming), I'm still suspecting you should get fucked with your freely expressed opinion.


I think it's a mistake to put Musk in that category. It harms your entire point. The other two express real human opinions (that one is free to strongly disagree with). Musk purposefully makes himself first and foremost a troll. He negatively affects our society, socially speaking, and it's only human to hate him. He invites it willingly.


I'm a software engineer, I do software development but also system maintenance, and I do handle networking and telephony systems, and work with some juniors. Working with AI is problematic. It can speed up you but at the same time delay you. For the system maintenance part sometimes you need to do a lot of stuff fast and in various machines and you can't just count on a cloud based AI oracle (that takes time) to do your job for you. And the same time, the more you use it as a oracle, the less competent you get. If you are an expert, I would say in any area, you do benefit from using AI as a tool but it easily can become a double edged sword and make you less proficient. For juniors, it can make them rapidly produce stuff that is impressive and works ok for sites and some visual stuff, but it's impossible for a junior to become an expert if they get stuck in the AI using loop. For AI to cause a clean impact, I would say that we would have to live in a world where software engineering didn't matter. That is, the choice of databases, high availability systems, the programming languages themselves.


I think it's more about inertia than anything else. I know the dishwasher will take less than 5 minutes to unload, but I put it off anyway. Problem is the AI can take action immediately, and that's very alluring. I'm sure there's research on exactly where that breakpoint lies. My current goal is to try and spend 15-30 minutes attempting to solve a task when I feel myself reaching for the AI.

One of three things tends to happen. Often it's something that is resolved in a matter of minutes, in which case it was laziness. Or, it's something that will take more time, say up to an hour, but the act of starting has conferred a sense of ownership that I don't want to give up to an LLM. Else, it looks like a much more complex problem and worth re-assessing, and potentially brainstorming with a model.


> we would have to live in a world where software engineering didn't matter.

As an engineer who works very hard to do the right thing, I'm beginning to worry that software engineering doesn't matter. I write code that i think about a lot, understanding every line. It's not perfect, but I try to make sure my code is maintainable and well structured. I work much slower then my colleagues who produce unmaintainable slop at an alarming rate. In my career, no customer has ever complained about code structure or quality. It feels like I'm sinking in quicksand in an industry that's dying.


Of course customers do not care about code quality in and of itself. Just like they don't inherently care about the type of seam used for a garment. But they do care if their clothes fall apart after two washes. People care if software is buggy or slow or becomes harder to use or more expensive over time. And the way we know how to mitigate that is by ensuring code quality (it's definitely not the only factor, but an important one).


It's not about what the customer complains or notices at short term, is about having a quality system that can be augmented without accumulating same kind of debt. I can give a simple example. I have a coder here that filled the crontab of a server with periodic tasks. One of them was doing +200 failed requests per second and shutdown one of our routers. The router wrote so much logs that it changed the health of its internal disk from 15% to 85%. He doesn't even know what the crontab is. This kind of stuff is bound to happen more and more because the more you use AI to vibe, the more disconnected you get from the technology. And that's why I say, the only way that yolo vibecoding could work is if the base stuff didn't matter.


> It's not about what the customer complains or notices at short term, is about having a quality system that can be augmented without accumulating same kind of debt.

I agree with this wholeheartedly, but convincing nontechnical management of this fact has been extremely difficult. It was hard in the days of the stackoverflow copy-paste monkeys, and it's even harder in the age of LLMs.


Some people cannot be convinced of this, but some can, as long as you don't use technical language to describe the issue. Essentially, instead of saying "we need to prevent technical debt and have a maintainable software architecture" one needs to say stuff like "software quality enables a faster time-to-market for new features and less customer churn". i.e. put it in business-y terms.


Yes, but then it's really important to demonstrate that this is true. If they invest in what you propose, time to market for new features needs to actually become faster, or customer churn needs to actually decrease. It's not enough to put the proposal in business-y terms, it has to actually effect the claimed improvements to the business.


You have to pick metrics to show management that they understand the importance of, and then be able to demonstrate degradation in those metrics when you don't do what you propose, and improvements when you do. Accomplish this and you'll build trust.

Too often, what happens is that the proposed benefit is vague and not empirical, and then the benefit is not actually realized by a large investment into it, destroying trust.


Sometimes it matters and sometimes it doesn't. The hard part is figuring out which is which. The most effective engineers are those who maximize the amount of time they spend picking the right point in the trade-off at the right times. Choosing a preferred point on the continuum and sticking to that at all times simplifies decision making (itself a useful thing!) but it's not the optimal strategy.

There are a couple ways out of this conundrum. One is to try to get really good at picking the right point on the continuum as much as possible, which is essentially a forecasting problem (and thus it's really hard!). I think the somewhat easier choice is to pick roles that align well with your style. If you have a deliberate and near-perfection preference, you can seek to work on projects where there is no question of the importance of correctness. If you prefer the opposite, you can work on prototypes and zero-to-one type projects, and that will be more satisfying (and less catastrophic).


Agree and disagree.

There have always been software companies that care about quality, and those that don't.

Many who don't care about quality exist because their products are forced onto their users. (Due to footholds from enterprise relationships, regulation, etc.) I bet slop will abound in these kinds of companies, but their codebases and products were already terrible anyways.

---

But research reliably shows users do care about things Just Working™ and feeling polished. With few exceptions, if software feels at all buggy or doesn't look visually amazing, you won't acquire/retain that many users.

Natural selection will teach hard lessons to the industry. Customers will notice things feeling "off" on products where AI slop is allowed to abound, and they'll flee to companies with sane approaches.

A sane approach: Humans actually guide the direction of the code which means they have to understand + review the code and course correct bad decisions. This doesn't mean agentic coding goes away, but it means this mad rush for insane velocity goes away.

---

Compare vibe-coded apps you've interacted with against world-class polished apps like Spotify, Gmail, Slack, etc. Those apps aren't obviously showing signs of AI slop, because the organizational structure is in place in those companies to prevent engineers from just throwing slop over the fence. Those engineers are doing agentic coding but are being forced to go at a sustainable pace.

The industry will eventually be forced (by the reality of business results) to recognize that this is the only approach that will lead to success.


Not an anti-AI view at all, but right now people is exaggerating a bit on the "AI is solving math". For now they are good at finding holes on theories, proving by negation, not proving for all cases, nor coming up with new theories.


> currently

A few years ago they couldn't do basic arithmetic. Is there any reason to think that capabilities flatline from now?

> proving by negation, not proving for all cases

I'm finding 2.2k "∀" symbols in the Navier-Stokes proof repo:

https://github.com/search?q=repo%3Aopenai%2FNavierStokesAndE...

It's not like can't proof universal properties.


Yeah that's why I said "right now people is". Then, ∀ for intermediate steps is not the same as ∀ for the final solution of Millennium Prize Problems' level. Fable exists for some 6 months now, internally, so the frontier kind of is a bit old right now, we will see how fast things keep going.


> there any reason to think that capabilities flatline from now?

4 years ago ChatGPT created better slop than current Claude Opus 5. It's a regression: things good objectively worse. You can find multiple threads here or on Reddit about that. Models won't necessarily get better.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: