Profits over productivity. If replacing people with AI, as impractical as it may be, leads to higher profits then CEOs have an obligation to do so. Poverty, sickness, and homelessness are none of their fucking concern.

The other day I asked an llm to create a partial number chart to help my son learn what numbers are next to each other. If I instructed it to do this using very detailed instructions it failed miserably every time. And sometimes when I even told it to correct specific things about its answer it still basically ignored me. The only way I could get it to do what I wanted consistently was to break the instructions down into small steps and tell it to show me its pr.ogress.

I’d be very interested to learn it’s “thought process” in each of those scenarios.

I’m finally starting to pull the trigger on dumping Google (specifically because of this event). For me at least it’s been a combination of, “They’re not that bad,” and, “This is basically like moving to another state.”

The guides I’ve seen lately about what replaces what is a good start but there should really be more in-depth guides for either moving over your data or just how to get started. Just naming alternatives is about as helpful as suggesting “raising chickens” as an alternative to high egg prices.

Cool idea! AFAIK emails are just sent as text but the client renders them when you read them. Theoretically it wouldn’t be hard to send markdown and add a header that indicates the body is markdown. Hard part is integrating support into the client. Since HTML is more verbose than markdown, and you can often mix markdown and HTML, this could actually lead to space and data savings!

I’d say it’s the tooling that sucks more than anything. I’ve had installations fail because of bad caches (and resolved it by doing things NPM advised me not to do), installations that take forever and seem stuck on one dependency, conflicts with ES and Common modules, node_modules folders that dwarf other folders in size, nobody makes proper use of devDependencies, some odd dependencies on Java or Python, and so on. I think the ease of learning JS has done it a disservice as you get millions of devs contributing but not all are trained as devs or computer scientists and you get a flood of libraries that all do the same thing and often even reproduce built-in functionality.

I really do enjoy coding in it more than any other language but when it comes time to run or build is when my rage kicks in.

Wait… what were we talking about? Oh, yeah.

Shitty web apps aren’t really the fault of the underlying tech. This is a problem of design and I don’t think the programming language really has much of an effect on the usability.

Disproportionate punishment is another of course. They probably lump pedophiles (a person with a psychiatric disorder) and child molesters (a person that actually harms children) into the same group and you deserve to die for simply thinking the wrong things.

And if you haven’t found any pedophiles yet, well, I guess you’re not trying hard enough. Or maybe… you are one of them… 😠

Can’t believe this needs an /s

Spotify is pretty fucking bad too. They don’t get a pass for not being Google.

It’s a verbose language but I don’t know if there’s any real language that encourages highly readable code beyond low-level syntax. You want to create a God-class in Python with nonsensical variables and 5 levels of nesting? The language won’t stop you.

They want to make buttloads of money from a rewrite, and it would cost buttloads to do this. They probably also want things to run like shit and cause misery for retired Americans.

Other than hardware issues, which someone else mentioned, it has a lot of enterprise-grade functionality that make it more secure and auditable than a lot of other languages. And despite, or maybe because of, its large memory footprint it’s actually faster than most languages.

I totally get any hate about writing Java though. It is a verbose language. Using Kotlin instead helps with that.

Jokes aside, nothing wrong with rewriting in Java. It is well-suited for this kind of thing.

Rewriting it in anything without fully understanding the original code (the fact they think 150yo are collecting benefits tells me they don’t) is the biggest mistake here. I own codebases much smaller than the SSA code and there are still things I don’t fully understand about it AND I’ve caused outages because of it.

Louisianans probably aren’t up in arms because wtf does this even mean? Seriously, you need to spell it out these days.

“When the enemy is making a false movement we must take good care not to interrupt him.”

I’ve said it before: there’s good and then there’s good enough. Content that’s “good enough” but easier to access will overshadow content that’s maybe light-years better but harder to acquire. That and attention spans are getting shorter. My kid has the entire Disney library at his fingertips but he’d rather flip between YouTube channels.

Hardly even noticed I cancelled Netflix.

Or restart. When you first boot your device the drive is encrypted until you enter your code or password.

As far as improving your corner of the code goes I would say a consistent style is important but having 500 lines per function is not a style. If someone will complain about efficiency (function call stack etc) then someone needs to identify what parts are truly time-sensitive. It’s likely not the entire codebase.

Wrangling a monster code base really requires a product owner. If one person doesn’t own the application as a whole then there’s no hope of consistency in the first place.

Or at the very least, so long as its http driven, put a proxy in front and on the backend break up common features into microservices. With a proxy the consumers will have pretty much no idea they went from talking to one service to a dozen.

It’s been the hardest thing for me to instill good testing practices in devs. In a function with 23 paths devs usually burnout and only do 9 or 10. Most never consider that making the function smaller is an option.