TehPers

In the meantime, we can expect AI to be at the center of more layoff announcements —whether people believe the job cuts are solely the results of AI or not.

If the AI bubble pops, you can bet the layoffs will be the result of AI, though not in the way people usually mean by this. Honestly, as much as I don’t want to see what it does to the world, I’m still curious what would/will happen.

You simply cannot replace people with AI. The statement itself is nonsense. Even so-called “agentic” AI cannot replace an employee in all aspects of work. You would need AGI to approach that.

Like the article mentions, it’s just an excuse to fire people.

Mixins are composition! They don’t describe what a type is (“circle” is a “shape”, etc) but rather what they can do (“circle” can have its area calculated, it can be drawn, it can be serialized, etc). Mixins in Python just so happen to be implemented by adding base classes.

Inheritance itself isn’t really a problem. It usually only matters when you have unnecessarily deep hierarchies, where a change in a base class can change functionality in dozens of classes in an unintentional way. Similarly, it can add complexity once the hierarchy is deep enough, but only really if you throw too much into the base classes.

Python’s ABCs are more of interfaces though, which is why despite Python using base classes to “inherit” them, a lot of that is really composition (or putting a class together from parts) rather than inheriting and overriding implementation details from a parent/grandparent/etc type.

OOP debates usually turn into inheritance vs composition which is weird because every modern used language has objects and most OOP languages lean towards composition these days.

The core OOP concepts are universal and important.

What might benefit you here is a proper GC. There are a few libraries to do this in Rust, though I don’t have any good recommendations since I haven’t needed this myself yet.

That’s $3500 for drives with style.

I’ll stick to my refurbished 12TB HDDs though.

I miss the days when it was simpler as well. Back before there were botnets with hundreds of thousands of compromised routers across several countries that could send tens of terabytes per second of data to your server for a sustained period of time. Back before there were thousands of bots crawling every IP and domain imaginable for exposed, abusable ports and wp-admin endpoints. Back before people started to compete in how many 9s of uptime they supported (before killing that all with LLMs anyway).

Sadly, we can’t go back to those times. Doing so with a production service would not end well.

The issue is not npm. Npm is a solution to a problem, even if it isn’t perfect.

The issue is we live in a different landscape.

Eclipse was great, having used it in the past, but its features are not exclusive to Eclipse. I can do the same inlining and extracting of code in vscode with code actions. The compile times weren’t seconds for me in the past, but they are for me now. Vite helps that even more (though that’s comparing JS to Java).

This is why it’s important that governments can shop around and negotiate as well. What the fuck do you mean it costs $78m for Accenture to redesign a website? I’ll gladly do it by myself for half of that.

I agree in general with the list, but there is some stuff I disagree with still. For example, the very first section: “Work on more than one thing”.

Like a CPU thread, if you’re responsible for multiple streams of work, you can deal with one stream getting blocked by rolling onto another one.

This is written from the perspective of the developer, not the stakeholders. Compared to a CPU, you are a single thread. You cannot work on two things at the same time. What this is referring to is not parallelism, but a form of concurrency. Like a CPU thread, when two tasks are being executed concurrently, one task is always blocked. This means that while you, the developer, are always working, you also are always blocking at least one task, meaning you are also always blocked on at least one task.

Instead of working on two tasks at once, pick up the second task only when the first becomes blocked.

I believe this might be what the author was trying to convey, but the title, some wording in the section, and the bullet point at the end (“Working on at least two things at a time, so when one gets blocked you can switch to the other”) contradict that and give the impression that you should always be working on two or more things at a time.

use as normal a developer stack as possible.

This, I mostly agree with, but I disagree with the wording. You should be using the same tools as the rest of your team when the tool matters. However, using different Git interfaces shouldn’t matter. I’d argue the same holds true for editors as long as the editors all have the features needed for the project.

For application work, some variety in dev environments can help you find bugs sooner even. Using different environments for development lets you test different environments naturally. For services, this is less relevant.

This is a super interesting approach to JS. Conceptually, it’s really cool. In practice, I don’t think I’d do it (at least for any projects I can think of) because explaining it to others would be difficult and representing complex logic as “commands” sounds a bit difficult.

In a weird way, it reminds me of actor frameworks though. The difference is of course the separation of effects.

One thing I wish the author would have done, though, is add some type hints. I know it’s about JS, but even some jsdoc types would have helped. It was a bit hard to know at first what the input types were to these functions.

The problem is not a lack of transparency, because being “transparent” doesn’t actually matter. The only thing revealed by this transparency is that social media companies do not give a fuck about this.

Pretty much sums it up. Toxic social media platforms which rely solely on advertising are destroying society to make a couple people more money. Nobody seems to care.

Nah they’re referring to a different Kevin Williams.

I never need to send files or data from my phone to someone else’s phone. All the files I care about are on my PC.

I’m not saying AirDrop or Quick Share are useless. I’m saying I don’t use them, but do understand they’re used, and I’m glad the support exists now soon.

For a feature I’ll likely never use, I couldn’t be happier this happened. Great job, EU!

Yep. This was the difference between a silent, recoverable error and a loud failure.

It seems like they’re planning to remove all potential panics based on the end of their article. This would be a good idea considering the scale of the service’s usage.

(Also, for anyone who’s not reading the article, the unwrap caused the service to crash, but wasn’t the source of the issues to begin with. It was just what toppled over first.)

is Windows a drug?

No. Drugs can give you a good time. Windows can’t.

s/OpenBSD/TempleOS

Cloudflare’s dominance is a huge problem exactly for this reason. Having a single point of failure is a huge risk, and it’s surprising that governments don’t view this as being a matter of national security.

As a side note, and not to “well ackshully”, but Cloudflare isn’t a backbone provider. But your point still stands lol.

monitoring how they are used is good to identify if people are actually more productive with it

Unfortunately, many jobs skipped this step. The marketing on AI tools should be illegal.

Far too many CEOs are promised that their employees will do more with less, so of course they give their employees more to do and make them use AI, then fire employees because the remaining ones are supposed to be more productive.

Some are. Many aren’t.

Like your comparison, the issue is that it’s not the right tool for every job, nor is it the right tool for everyone. (Whether it’s the right tool for anyone is another question of course, but some people feel more productive with it at times, so I’ll just leave it at that.)

Anyway, I’m fortunate enough to be in a position where AI is only strongly encouraged, but not forced. My friend was not though. Then he used it because he had to, despite it being useless to him. Then he, a chunk of his management chain, and half his department were fired. Nobody was hired to replace them.