The trackpad is head and shoulders above anything I’ve ever used. For me, that’s worth the price of admission alone.

I always find this argument odd - I absolutely hate Mac touchpads. Maybe I’m just too used to non-apple hardware or something. Not arguing with you, just pointing out that this may not be a “bonus” for everyone.

It scanned a large amount of text and found something.

How hilariously reductionist.

AI did what it’s supposed to do. And it found a difficult to spot security bug.

“No big deal” though.

The author has completely misunderstood the advice to “not reinvent the wheel”. Or they’re just being needlessly literal in their interpretation.

If your job isn’t making wheels, then you use somebody else’s wheels when you need wheels, so long as those wheels do what you need them to do for a cost that is acceptable.

There is a high cost to reinventing things. So you don’t tend do so unless there is a compelling reason to do so.

If you’re just exploring and learning nobody will tell you not to.

Jesus Christ, it would be fewer steps to install Debian and then rust + vscodium.

It’s not uncommon to have your Dockerfile curl https://host/file.tar.gz and then tar xvf file.tar.gz into the filesystem somewhere.

You don’t want to use snaps in docker containers. They need systemd and stuff that are going to be a real pain to get working.

I’m a big fan of both AI and automation but this is just 😬

Generally speaking I would avoid combining critical networking infrastructure with other services. Just from a reliability standpoint.

Let your router be just a router. Simple = reliable.

My dude, I very code other humans write. Do you think I’m not verifying code written by AI?

I highly recommend using AI. It’s much better than a Google search for most things.

“I use Nix, btw”

The problem is that you really only see two sorts of articles.

AI is going to replace developers in 5 years!

AI sucks because it makes mistakes!

I actually see a lot more of the latter response on social media to the point where I’m developing a visceral response to the phrase “AI slop”.

Both stances are patently ridiculous though. AI cannot replace developers and it doesn’t need to be perfect to be useful. It turns out that it is a remarkably useful tool if you understand its limitations and use it in a reasonable way.

It’s exactly the sort of “tedious yet not difficult” task that I love it for. Sometimes you need to clean things up a bit but it does the majority of the work very nicely.

“Hey AI - Create a struct that matches this JSON document that I get from a REST service”

Bam, it’s done.

Or

"Hey AI - add a schema prefixed on all of the tables and insert statements in the SQL script.

I’ll admit I skimmed most of that train wreak of an article - I think it’s pretty generous saying that it had a point. It’s mostly recounts of people complaining about AI. But if they hid something in there about it being remarkably useful in cases but not writing entire applications or features then I guess I’m on board?

Have you used AI to code? You don’t say “hey, write this file” and then commit it as “AI Bot 123 [email protected]”.

You start writing a method and get auto-completes that are sometimes helpful. Or you ask the bot to write out an algorithm. Or to copy something and modify it 30 times.

You’re not exactly keeping track of everything the bots did.

I’ve seen similar issues with ansible and terraform. It’s much better with more traditional languages though. Works great with core go-lang, Python, Java, Kotlin, etc. Ymmv when it comes to some libraries as well. I think it’s mostly to do with the amount of training data.

It can buy food, water and shelter though.

The execs are floating the idea that AI can be used to replace or supplement the people leaving.

I’ve been thinking about going into consulting. Companies like this are going to be a gold mine in a few years.

You say “The Windows Memory Subsystem” not “The Windows Subsystem for Memory”.

Windows Linux Subsystem would likely be most clear.

I build my infrastructure with the terraform, Ansible and helm charts. The code is it’s own documentation as well as comments in that code explaining why I’ve done things if it’s not obvious.