Here's another one, catch!

I’m a mathematician by training who has worked extensively (and exclusively) in the software field. While I realize I’m probably biased here, I think I write very solid code and have rarely received any complaints from trained software engineers about it.

I did however also take quite a few computer science classes in college and have spent a lot of time learning how to write better, more readable and maintainable code. Having had quite a few jobs at the start of my career where I was the only programmer on a project and therefore forced to eat my own dog food has certainly also helped.

Instead of starting your own project, have you considered simply contributing to an existing open source project instead?

I’m not sure that’s a bug, that’s always been like this IMO. Every tab has its own history, so if you switch tabs and later go back, it’ll be at the same place you left off. I.e. if you last had the “Unread” box open when you were on the inbox tab, that’s what you’ll see when you go back there.

IDK, virus scanners and malware detectors could do these things before AI.

You could search for stuff like directly accessing the ~.ssh directory, or any invocations of wget or curl to download external scripts and run them through an interpreter and flag those for closer inspection.

If you want to get fancier, automate installing packages in an isolated environment (like a container or VM) and keep track of every file system access and network request they make.

Sure, eventually they'll figure out ways to obfuscate those things, too, but it could at least prevent people from doing things in such blatantly obvious ways.

You can run DOOM on an Arduino, no problem.

https://github.com/daveruiz/doom-nano

If a literal toaster can do it, I'm sure this thing probably can as well.

Bah humbug, just hook it up to the cloud, WCGW?

Iron Maiden would like to have a word with you

It really doesn’t matter. Literally a Raspberry Pi will do for a beginner.

How do you calculate those numbers though?

It's not like your colleagues will be keeping track of how much time they've wasted writing ineffective code. If anything, they'll try to hide that by arbitrarily inflating sprint points etc.

I've worked in environments like that and the issue almost always isn't that people wouldn't LIKE it if there were tests, it's that they

1. Don't want to have to learn something new in order to do the same job they're already comfortable with
2. Are worried that if they convince management to let them invest X amount of time into doing something that will improve productivity, they'll be expected to be more productive in the future

And of course, all of this for no extra money. Unless you work at a place where management prioritzes developer happiness over how many sprint points the team can knock out every week (and those are rare), the sad truth is that it'll likely be about as popular as leftover food growing mold in the community fridge.

This means you don't want to work there anyways.