scuff3d

In my experience the real answer is almost always "just don't do that other stuff". Most of the complexity Postgress is claiming to fix here doesn't need to exist in the first place.

"Management fucked up, and now you all get to pay for it. Have a nice day :)"

Usually I bounce between the Zig and Odin discords, as well as the Handmade Network discord.

Why I've moved more to a couple of language/software dev discords and away from Hacker News. Way too much uninteresting AI nonsense on here for a while now.

Oof, that price point is rough. I hope this does well for them, but I'm not sure who this is for.

On a semi-related note, I bought a Pixel phone about a month ago, and I'm shocked by how unpolished it is. I've had so many little annoyances pop up, issues I never had on other android phones. Keyboard hiding/appearing when it's not suppose to, bluetooth dropping, WiFi dropping, network switching taking forever, screen becoming unresponsive... It's mostly all small things, but they really start to add up after a while.

Seriously, just switch to Go or something

Rust didn't have nearly the industry adoption it does now back in 2020, but it was gaining traction in various parts of the community. If you learned it back then it was either because you love it, or you thought it had staying power.

I think Zig does, specifically because of its build system and it's C interopt story. Plus Zig has the added advantage that learning it teaches you about how the computer works, how memory gets laid out, etc. So even if it never gets wide adoption the skills are highly transferable.

Can't. It's a worse case scenario. It got vibe coded but I don't have access to AI tools to undo it. Basically the company was running a test on some tools, one engineer went ham and the thing ended up getting used, then the company decided to drop the ban hammer on the tools.

Literally in the middle of ripping apart a vibe coded mess at work to figure out what's even worth keeping. Not fun :(

There's a lot of little things that just added up, but I think the clearest example was the exchange regarding Andrew's pay from the foundation. I don't have an issue with him being paid for the work, or the amount he's taking, I would be surprised if anyone really did, but the way the interview asked the question came off as "Oh you're only making x? You should be paid so much more", and Andrew even commented in it saying "...it sounds like you're implying I deserve more...". I'm of course paraphrasing, but that's the impression I walked away with.

The questions also had a tendency to be somewhat shallow. There were a lot of places where it felt like the interviewer was queuing Andrew to respond to criticism or explain controversial choices made for the language or tool chain, but the interviewer doesn't really follow up on them are point out what the issues might be.

It might have been expectations I guess. I was hoping for an interesting technical interview and instead it seemed like a fluff piece.

I have a lot of respect for Andrew, and I really enjoy Zig, but God that interview was awful. Andrews answers were fine, but the whole thing felt very sycophantic.

As far as I'm concerned Bun has been extremely irresponsible with this entire rewrite, and it calls into question their entire development philosophy. Any project that cares about stability and reliability should steer clear of Bun for a while.

Congratulations to everyone who uses Bun. You're now working as alpha testers for Anthropic... for free.

Anyone using Bun should consider migrating away immediately. Not because of the LLM angle, but because of how insanely irresponsible this is.

Thank you for so aptly demonstrating what I deal with at work.

The annoying thing about Rust, or at least the hype around Rust, is that people want to in use it for bloody everything.

We have absolutely no need for it at work. We're writing micro services that run in K8s with no extreme performance requirements. Nobody on the team knows the language (I know it better than the people arguing for it, and I don't know more then the basics). And yet, every couple of weeks, I'm having to talk someone out of switching certain services over to it. It's like a damn disease.

I feel like this article was circling a point it never actually got to. All the advice in here (except controlling scope creep) is specific to a TUI with an elm like architecture.

But here's the thing, you almost never know what the architecture is up front. If you do you probably aren't the one writing the actual code anymore. Writing the code, with or without an AI is part of the design process. For most people it isn't until they've tried several times, fucked it up a bunch, and refactored or rewrote even more that you actually know what the architecture needs to be.

This is awesome! I'll have to try reading through the code when I have more time.

It would be awesome to read a blog post about the project. Your approach, lessons learned, unexpected stuff, etc.

You missed the point.

People want to use stuff like this as somehow evidence for AI being able to write entire software systems in a few days. We saw the same shit with the "compiler" they made with a bunch of agents. Literally the only reason it's possible is because the hundreds of thousands of man hours and God knows how much money that was poured into the reference projects befoes the AI got anywhere near it.

To replicate this kind of thing with a green field project would take an absolute ton of spec work and requirements derivation, which will substantially eat into any savings from having AI generate it.

The accomplishment itself is interesting, and unlocks opportunities to do work no one would have bothered with before, but it doesn't represent what a lot of people desperately want it to.

Three out of four of the top comments don't even directly engage with the point of the article. They're focusing on nitpicking elements of it or just going off on a tangent only somewhat related.

Not to mention to even attempt something like this from scratch would take hundreds of hours if spec work. I see it all day everyday in the aerospace sector. Software engineers have absolutely no idea what deriving a design document and all its associated artifacts actually looks like, and they're in for a rude surprise if the industry really does shift hard that direction

Look what it can do in 6 days!

Ignore the hundreds of thousands of hours put into the original architecture and test suite that made it possible in the first place.

Lol. What a goofy take.

You read an article like this, and despite some flaws, it restores your faith in humanity a little bit. Maybe I'm not the only one looking at the shitshow in horror.

Then you come to the comment section and are immediately reminded why the whole god damn world has lost its mind.

"Hey use our thing! It's totally going to replace all humans! It's so awesome it can do your job for you!

...

BTW, it hallucinates... Like all the time.. and if you don't fact check our product you're responsible. Not us! We stole all your data to train it, we're making billions and billions of dollars off that theft, but you own all the liability"

We don't hear anything about it because the Republicans are in charge. If a Democrat was in the White House right now you wouldn't be able to shut Fox News and it's ilk up about how the national debt is a harbinger of doom for the entire country.

That's because "agentic engineering" by and large is a term made up to make people feel better about the fact that their just vibe coding.

So you're saying the market is weaker with more competition?

So then no, you don't have anything to back the statement and your just guessing wildly. You can just say that.

Was just talking to my wife about this yesterday. Our son is 10 months old so we're still in the diaper stage, and it's really not a big deal. Since disposable diapers and baby wipes became a thing, not really sure why anyone complains about it.

Compared to trying for hours to get him to sleep, or dealing with the sheer panic we felt when we had to have him rushed to the hospital, a poopy diaper is nothing.