161–170 of 1001 posts
Code quality and architecture still matter, because they also make it easier for LLMs to reason about the system. That said, Opus 4.8 and Codex 5.5 both can write code that is higher quality than your average engineer. They are not quite there yet in terms of code re-use, but I think that's a solvable problem.
Earlier quoted context omitted.
Posting this under a burner so I don't dox myself: I work in FinTech on a regulated product. We have access to Mythos. Mythos identified part of our codebase that it confidently asserted was not complaint with a particular regulation and we were at grave risk by allowing it to operate the way it was. Except this was not the case, it had of course hallucinated what the regulation actually required (I know this because…
Is that all that Mythos did? Did it find any real potential issue, optimization/simplification opportunities, or sparked any thought-provoking discussion within your organization? Or was it purely a net negative experience?
The only thought-ptovoking discussion should be "why the hell do we have this stochastic parrot anywhere near out codebase"
Earlier quoted context omitted.
Lol thats brave on your part, given that a mistake can cost thousands and you have no accountability (punch!) from an LLM
Your account has no accountability. Do your taxes wrong and the tax payer is liable. Ask me how I know.
Earlier quoted context omitted.
The corporations and executives are already winning if you swallowed the concept of 'rockstar' engineer. Sure there are more and less experienced engineers, but even interns can and often do provide good input and spot mistakes made by seniors. The 'rockstar' engineer at most tech companies simply equates to the somewhat autistic guy with a brown nose who's working 15 hour days for a pat on the head from management (…
Even if we forget "rockstar", there are certainly different levels of engineers. More experience doesn't automatically mean better either. That is not to say experience doesn't matter. It matters quite a bit. Sure , good interns can sometimes have good feedback or spot mistakes. But not consistently enough. All of this to say that it's not just experience that makes one a better engineer.
The last sentence in the article is correct: "Maybe I should consider transforming my woodworking hobby into a profession." As an AI optimist, I think all forced labor should eventually be done by AI. People can then spend their time pursuing their own hobbies. Just as many people still play Go after AlphaGo appeared, because they genuinely love the game. In the future, coding may return to being an art form. People…
> As an AI optimist, I think all forced labor should eventually be done by AI. People can then spend their time pursuing their own hobbies. Just as many people still play Go after AlphaGo appeared, because they genuinely love the game. And what sort of economic system do you imagine will be in place to support billions of people being able to just play Go all day long? How do you imagine the large capitalistic global…
If automation makes producing food so cheap that it is almost free than it is ridiculously easy to acquire it. Similarly automated construction.
The way I see it the economy will point towards outer space. That’s where most jobs and flow of economy will be.
However most people will have 10x times uplift in purchasing power compared to today so their relative poverty will be ridiculous for us to call it the poverty but they will still think they are poor and troubled.
Generally I don’t think it will be utopia for the people living in that moment but if you look from medieval times at today it looks like utopia for serfs from the past. You however wouldn’t call it an utopia because your standards grew as fast as your purchasing power.
I think that rich and poor will be separated by accessibility to anti age treatment and other bodily improvements.
The tragedy of the poors in the future will be living measly 80 year old life like a today millionaire and that will be considered lower class. Those people with wrinkles we don’t want to look at because of uncomfortable pangs of guilt.
Earlier quoted context omitted.
> Domain knowledge can be learnt much quicker than how to apply good engineering principles. There was an entire thread a week ago about how domain expertise has always been the real moat: https://news.ycombinator.com/item?id=48340411
And I'd still question it. The experience of just… knowing how a good architecture looks like without being able to really put it in words is what makes a good engineer to me. These people can pick up relevant regulations or industry terms and deliver value quickly enough.
I thought about going back to college, learning Math, Statistics, advanced Machine Learning and applying for research role at a frontier lab.
That's a super silly take. As much as I did math and even course on machine learning back in the days and I was making basic perceptron in code at university - to get back and be able to do so on frontier level that's years I don't have anymore.
Anthropic is doing all that also with their LLMs so that ship sailed.
Big thing is — business people are not going to spend time prompting LLM to make an application. If they do then they will become "programmers" and we all (experienced developers) know — you touch it you own it — they (business) will not bother running or taking responsibility.
Right now on r/sysadmin there was bunch of posts where admins have "vibe coded apps" requested to be "productionized". Those business types requesting don't know yet — you touch it you own it — they think they can vibe code app drop it at ops and it is all fun and games. When people will start requesting features, start nagging about bugs, start cursing on whatever changes they introduced it will be back to "hey maybe we will just get someone to do that for us".
You might not need as deep software dev knowledge but with deep software dev knowledge you still will be faster operating LLM to build systems than non-dev