joenada

1. The average human software-generator sucks at security. 2. LLMs are trained on human-generated software. 3. Therefore, LLMs suck at security.

Log4J4PHP

It goes into the soil and can take a long-ass time to get back into any our supply. Yes, it's still on earth, but it's no good to you if it's locked up in the soil or the polar icecaps. And that's not to mention the ridiculous ways we pollute water that make it very difficult if not impossible to recycle. This stuff really isn't as simple as just drain the lakes and rivers. We absolutely could run out of fresh water, and pumping it into data centres is a terrible idea.

This attitude is why the world is fucked.

Statistically speaking, compared to non-fresh water and compared to how much we actually use as a species, there is very, very little fresh water available to us.

Your question is already answered in the comment you're replying to.

It matters because there's almost none as it is, and you don't collect 100% of the water you use just because it rains. Water gets polluted, trapped underground, locked up in glaciers.

Because you're the only person on earth who matters, clearly.

Also, it's not 3% of 2/3. It's more like ~1% of 3% of 2/3. Most of the fresh water on earth is locked up in glaciers or trapped deep underground. You can absolutely lose surface water, too - when pipes leak, for instance. And that happens all the time because a lot of the water infrastructure is ancient. Where I live, there are still thousands of miles of Victorian-era pipes. These crack all the time. You don't just get that water back straight away when it next rains.

That's fresh water in general. Most of it is frozen. The amount you can actually use is a sliver.

The difference is that automated tasks are (or should be) deterministic and reproducible, and taking up time devs could be using to do their actual job (writing code, solving technical problems, etc).

This is satirical, right? They use fresh water, which is a tiny, tiny % of all water on earth.

This thread is very depressing. Web dev bootcamps and product managers have done untold damage to the field of software engineering. And it's our own faults. We had it so good for so long. There was a period of time when programmers were the new "rockstars" (for better or worse). We should have used that respect and those resources to unionise and build some kind of institution responsible for teaching, mentoring, standards, etc - a software engineering guild of some sorts.

Quality is, was and always will be job one. There's obviously a place for AI tools (providing the economy doesn't melt), but can we please just slow down for a second and think about what we're actually doing?

You sound like a person who's never had their app pen tested. The attack surface is anything but small if you're working with any kind of sensitive data.

Yes, that's fair. I'd argue, though, that the training required to get your team up and running should be fairly minimal - Kotlin is a very easy language to pick up, especially for people coming from TS - and will pay off dividends in the medium to long term.

This is only anecdotal, but I had a review on a brand new app turned around in ~6 hours 2 days ago. A lot of it has always been luck of the draw, though, granted.

Your assumptions are very outdated. App Store review times are typically < 24 hours and have been for the last couple of years. And KMP makes cross-platform a real thing now, rather than hacking a web view into a native shell, which was always the worst possible user experience.

The age of "programmer tyranny", as you call it, was over long ago. Product manager tyranny has been the de facto regime in Big Tech for years. That's how we ended up with subscription models everywhere, enshittification, and infinite data tracking. Imagine that x1000. That's where we're heading, IMO.

Obj-C and Autolayout were absolutely awful to work with. SwiftUI is at least the right idea for a UI framework, it's just been implemented horribly.

Burnham down the house.

Going? I think we got there a long time ago. I'm sure we all try our best but our industry doesn't take quality seriously enough. Not compared to every other kind of engineering discipline.

Go code is outrageously ugly, and they'd rather you not highlight it.

This guy writes.

Not a technical project in the typical sense, but I finally started working on a satirical faux-exposé series about my years working in the industry.

If anyone's interested in that kind of thing:

https://massiveimpassivity.substack.com/p/softcore-how-nobod...