oldmanwillow21

I encourage you to do this and applaud your sentiment, but only if you’re ok with this taking a year at minimum. And then, only if you’re zealous and single-minded.

Did my comment make it seem like I was in support of the war? There goes my pedantry again.

Haven’t read the Old Testament, eh?

A HIDS like ossec does exactly this. I just use a high port for my own stuff but have deployed this into company environments.

You can't always change how other people behave, but you can always change how you respond to their behavior.

12 year old mailserver. Only went down because it was hosted for free by an old employer and they phased out the hardware it was running on.

25 years ago I started buying books and cheap, recycled computers. I learned networking, systems administration and programming in my bedroom. I've worked professionally for just shy of 20 years. Sometimes, all it takes is the will to accomplish something.

Yeah, my kid can type and do basic programming like a champ. He is 7 ... As a society, we do a serious disservice to our kids by assuming they're too young to handle things like this.

It really depends on the requirements of the project. The main common factor is that no matter the environment the aim is to perform initial setup and, to the greatest extent possible, forget about it. It doesn't matter whether it's bare metal, a VM or the cloud. I'm currently working on a kubernetes-based project. As I build the app, I use docker compose for rapid feedback in the same containerized environment it'll run in in production. I can run tests locally and be confident that I won't need to worry about things like configuration drift or version mismatches. I'm using Flux to automatically update the dev/prod cloud resources whenever I push to the main branch. CI/CD builds new images for feature branches, does things like security scanning, secrets detection, testing and linting against a test database, and tagging the new :latest on merges. It also enforces the agreed-upon configuration and disallows ad-hoc changes. The only way it can be changed is through consensus and merge request, barring emergencies. The infrastructure itself is defined in Terraform this time, but I'll use Terragrunt where it makes sense to. This defines the network, the cluster and all its dependencies, the database, DNS zones, CDN, object storage, etc. It enables every bit of tuning that working on a live server does, but does it under a codified contract that is easily repeatable. That's just one example. I could have talked about IaC plus config managment like Ansible, Puppet or Salt for a VM-based architecture. I could have talked about Packer for building a custom AMI to be provided to an MSP in an airgapped govcloud environment. Or using The Foreman with config management and a local package registry. The one common factor is that everything is written in code and serves to provide stability maintainability so I can sleep through the night and stop thinking about any of it whenever I want/need to.

I spent 7 years building and configuring actual servers, and another 13 years writing systems to do it for me. Much of my work has involved going back and unfucking hand-built systems or ones built with things like Packer. I'm not claiming that Packer is useless, but outside of very specific cases where a custom AMI is preferable it's rarely the right architecture decision today in my experience. You've probably worked in niche shops that require a lot of custom work or tuning. Or I don't know, maybe you're one of the many curmudgeons who just insist the old way is better. Things used to work the way you're describing here but now, in 2025, the industry has moved on. At least as this is written, trivializing it with "ami=" seems to belie a lack of real understanding of how modern systems work.

Everyone that upvoted this is either a tool, a moron or both: a middle manager still trying to justify their existence.

Yes. The tried and true tradition of hating things you don't understand.

I was interviewing for a role a few years ago. Thought I was doing well, but the interviewer suddenly said to stop and ended the interview abruptly. After I started he said he'd seen enough and didn't want to waste time.

I don't remember typing this message. On topic: I've wound up stuck back in corporate jobs at times, but consulting has been my favorite way to work. I work when I want using mostly my own creativity and discretion. I finish the job and then move on to a different set of challenges. It's not always smooth. I communicate well, but I'm introverted and don't have a large network to draw on. Work dries up, especially in the past year. I'm making an effort to get out more and talk to more people, I feel like it's the key to making this kind of lifestyle work.

Caesars (sports betting) puts you through a 6 hour in one day final round interview at the end of a multiple 1hr round interview process. Mutual feedback that it went very well. They promised an answer either way within a certain time frame, then ghosted before sending a LinkedIn rejection 2 weeks later. I'll never do another ridiculous process like this again.

MCS is clearly the superior choice.

Most of the languages here aren't underrated. If you want a real underdog, look no further than Perl.

$perl++ though Raku (new nae for "Perl 6") is a living, breathing thing now.

Pun intended?

Perl was one of Matz's favorite languages, and he used it as inspiration when creating Ruby. I don't know this for a fact, but it stands to reason that Ruby's unless may have been inspired by Perl's.

Perl because there's more than one way to do it, and because its first-class regexes are the granddaddy of most interpretations in use today.

Everything I care about (and that I don't expect anyone else to work on) is still written in Perl.

Read about who created Ruby.

Only answer needed.

Something something Homer bushes. That sounds like a better option than storing comma-separated lists, though.

Stop paying Microsoft and switch to an RDBMS that supports JSON fields? Happy middle path, maybe. I'm a pedant for structure, but normalizing 30k elements sounds brutal if there's not a high degree of consistency across records. If a lead has a problem with pushback or their opinions being questioned, that's what I'd call problematic.

A lot of people use neocoties to avoid modern standards that they may feel have degraded, if not outright destroyed, all the things that were enjoyable about the web. More power to them.

It shows up in odd places. Fluentbit (similar to fluentd) uses LUA for writing custom filters, for example.

I don't drink, but I'll drink to all of that

Yep. Democrats are not left-wing.