psnosignaluk

Pre-cloud pets vs cattle approach. We ran a few pets, but had DC's worth of cattle thanks to PXE, TFPT and Ansible. No Terraform required, as there was no need to control the state of multiples of cloud cruft. Good times. Except when something would pack up in the middle of winter in the wee hours and it was a bollock-cracking motorbike ride to the DC to spit on the offending black box.

This is applicable to far more than stroke victims. Any manner of brain interference should have the same ruleset. Reading through the comments, this ruleset should apply to everyone regardless of their medical situation. Chiming in with a +1 to fitness, and diet. It helps, massively.

Captain Obvious chiming in here, but as one of those boring douche canoes whose concerns are data privacy, data locality and generally the ability to understand how AI trains off of and manipulates the data we feed it, I'm resistant to the tech. We're testing the use of AI to aggregate and explain patterns in the data we have, but this is limited to our ticketing systems and Slack. Until our current choice of AI provider can guarantee that our transactional data won't be stored outside of the EU, the people driving this internally and those keen to make the sale externally can take a long walk off of a short pier. I can almost smell the aroma of the coffee machine from the chamber in which an EU subcommittee is working on the Artificial Intelligence Act (AIA) (EU) 2025/xxxx to add to the raft of regulations that financial entities in Europe need to concern themselves with. Maybe they'll be nice and just append it to an existing act.

AI might be great. AI might be terrible. I'm not all convinced that most data aggregation features baked into AI and used by most normal companies couldn't be implemented in R or SQL (disclaimer: I couldn't code my way out of a wet paper bag if the tool I was told to use was an axe). It's just wanted so that someone can crawl over data sets to ask simple questions like 'how many merchants exceeded n number of transactions between a and b date' or 'My customer needs an eIDAS certificate. What do I ask them to send us without having to talk to Captain Obvious?'. I mean, we're busting a gut on revamping our developer docs, but given that the spec is already public, I'm pretty sure that developers can already vibe code against that. Going to test that and see how it gets on.

I am a walking, talking, laughing, smiling result of the effects of immunotherapy. I was on Pembrolizumab on a six week cycle across eighteen months, administered at Charing Cross Hospital in London, after diagnosis in early 2022. It effectively dealt with my lung and brain cancer, with minimal side effects. This year, I returned to the gym and am sucking up every last opportunity to extract as much fun as I can with my wife. I am amongst the luckiest of souls, and feel deeply sorry for everyone who is losing to or has lost someone to cancer.

I was recently diagnosed with cancer. I've had brain surgery to remove 2 x tumours, targeted Gamma Knife radiotherapy to isolate treatment on an additional 18 lesions in my brain, and a week ago, started immunotherapy for my lungs. All of this has been handled through the NHS, some very clever blood tests and a ton of scans and cross checks. I welcome the additional work being done by the NHS and Cancer Research UK to improve the diagnostic and treatment quality of the disease. Very thankful that I happen to live in the UK as I go through this.

Amen brother, amen.

At a company like the one I work for, it's a hill noone can afford to die on. PCI-DSS demands at least some control over employee laptops to ensure that certain secure configuration standards are met. That entails dropping command and control agents on machines. Say what you will about PCI and credit card cartels, but no accreditation, no business.

That said, as I work from home, my work laptop lid remains closed for all but a fortnightly company all-hands meeting, and I ensure that I keep zero personal data on it. I'd be an absolute no if the demand ever morphed to always on video or activity trackers. That's a bridge too far.

As it stands, I understand the need for some policy enforcement/remote control of their assets, but will make whatever moves I must to ensure that policy doesn't infringe on the rest of my environment.

I'm just going to jump in with an utterly pointless "woohoo!" As a gRPC shop, this is going to open up a lot of options for both our own infra and make it easier to support clients on AWS. Now if only Azure would make it easy to implement solutions that leverage gRPC...

I think it depends heavily on what you're doing. My world is full of YAML/HCL/cnf files, and if I'm writing code, Go, where code is for software that runs from the command line, a daemon, or a no frills API/web service. Atom/VSCode and other IDE's were wasted on me, so I found myself gravitating back to Vim for its ease of use for those use cases. That said, vim-bootstrap did save me effort of getting a pretty solid editor out of Vim without having to think too hard about it.

Thanks. Having a look at Codacy.

Commenting to add languages: Java, Go, JavaScript, PHP and C# primarily. gRPC in Java services, tooling in Go and SDK's in all languages. Not much in the way of typical frameworks.

I somehow read that initially as RedHat as well. Curious as to how my habit of skim reading and incorrectly logging information has filled by brain with bitrot over the years.

Heh. Know of a team of engineers who deliberated over a brittle system for months. Mission critical, world ending stuff if it failed. Their manager got tired of waiting and sent a mail to the team that ran the data centre asking for the machine to be disconnected from the network. By CoB, nobody else had even noticed. Thanks to the nature of big businesses, that mission critical application had been programmed into obsolescence years before by other teams shifting their own workloads off of the server.

It's been an interesting year for AMD in the DIY builder space. The every man chip that seems to get recommended at every turn is the 3600X (or 3600 if you're partial to Gamers Nexus). Most of big ticket builds seem to be opting for a 3900X these days. That, however, is a fickle market and subject to the kind of fandom where lines are drawn on brand loyalty that no manner of contrary evidence will shift. As an enthusiast market, let 'em have at it. The saltiness in comment threads can be comedy gold. The day that Intel launches a 12-core + CPU on 10mm, it'll be the belle of the ball for all of the next-gen big ticket builds. Swings and roundabouts.

AMD are starting to make some waves in the hyperscale DC with EPYC Rome. The real fun starts if that progress translates into your corporate workhorses starting to opt for EPYC over Xeon in their data centres. Intel are a big company to take down a peg, and have had little motivation to innovate any more than needed. AMD also have a bit of a history of doing amazing things and then dropping the ball in spectacular fashion, which is a candle that no corporate buyer wants to be holding when they've pumped a ton of capex into a 5 year deal pinned on fleet maintenance. Intel might not be dynamic, but at least you know what you're buying into. I think that the same translates to those making the purchasing decisions for corporate users. For enthusiasts, what your machine runs on is a big deal. For everyone else, as long as it switches on and lets you get through a working day without going tits up, who cares? And if it does, it needs to be fixed or replaced before you start falling behind on work. That also trends toward buying patterns that focus on known good config.

It's a fun market to watch. If I were back in my old role, I'd be looking for EPYC solutions in my servers and attempting to wrestle a few test laptops with Ryzen 4000 CPU's next year, even if only to worry my boss.