People are defined by the people around them. Make sure they have a good group of friends. Friends they can depend on, friends they learn from and vise versa and most importantly friends with morality that make the right choices in life.

Deep in the valley

deleted by creator

Don’t, you’ll lose money on it.

Username checks out.

One I saw 8 times when it came out is E.T. Hadn’t seen it mentioned yet.

More recently I loved coming back to Lost in Translation.

Sounds like a win/win!

Sodium ion batteries have less energy density as opposed to Lithium ion (100-150 WH per Kg instead of 150-250). I’m curious how much these “wet” batteries improve that. The article doesn’t say.

Nonetheless, even if it’s not the new battery for your car, it could be useful as energy storage for the grid, storing green (solar) energy for the night, and desalinating seawater at the same time.

The EU would lose a bottomless money pit.

Have a look at onedev.io. it’s local Git hosting but it includes cicd and even an issue tracker.

Well, we can certainly agree to disagree. I’m not oblivious to having a blind spot here and there. In fact, I very much enjoyed our discussion here, and your perspective. It almost feels like a 2000s era forum discussion, before all the sour people got access to the internet. So thanks, and get well soon!

Thanks for your reply. I get the pros you mention, and auditing is more relevant for bigger shops than smaller ones of course.

Your remark on peer review reminds me of a situation where I had to change a database scheme. So that’s in a database project, and I have to do a PR on that. Now I can’t deploy it because argocd won’t allow me to manually scale down the pods of our application, and I need the database to be idle. It will revert to the defined state, so I’m unable to update without also doing a second PR on the infrastructure yaml. Then after the update I have to reverse the situation again and do a third PR.

So now I’m waiting for two approvals, and I haven’t even touched any code yet. It just seems like so much overhead for doing something that used to take two minutes. I think this is a question of trust and the bigger the organization, the harder it is to trust everyone. That’s why small shops can get a lot more done in less time.

I get CLI users, sometimes using the cli is faster and more efficient.

However I have had frequent discussions with people (all of them also avid CLI users) that set up infrastructure as code. I prefer the super understandable Gui of a tool like octopus deploy over hundreds of yaml files whose content can only be understood by doing a year long deep dive any day.

They always use the same two arguments: Infrastructure as code allows you to rebuild your entire software deployment from scratch, and the code can be versioned, thereby providing an audit trail for deployments.

In decades of software development I have exactly had to redeploy an entire network from scratch 0 times. If you’re in that stage the cause is most likely hardware and re-provisioning that will probably take the bulk of your time.

About the versioning: I’m not arguing against storing deployments as yaml files, but writing them by hand is insanely inefficient. There should be a nice GUI that generates and writes these yaml files, so you don’t have to know every option an value and every validation rule by heart.

Also, I am relatively certain that a tool like octopus deploy also has auditing of who deployed what software in which location.

Honestly, just ditch Instagram already. And convince your friends and family to do the same. It’s better for your time, your privacy and mental health. The demise of these platforms starts with people like you and me never visiting these places all together.

I agree, but if there’s no alternative now, let’s encrypt could be used to bring most of the internet down in an instant.

We especially need a European alternative for let’s encrypt. Almost all websites, web applications and APIs rely on it.

I’ve written thousands of lines of untyped python code for a system (still) used daily by hundreds of users, handling time critical as well as financial data. It made the company I worked for millions and it worked. Was it bug free? Nope, bugs would appear in production from time to time, but they were very easy to detect, and very quickly solved, especially because of the fact that python is an interpreted language. In 7 years of working on that application there was only one bug that caused data corruption and required us to reprocess some data that took a day or three. That was the worst thing to happen in the entire lifetime of that codebase. I totally agree that if you structure your code properly, log properly and give your developers the trust and permissions to actually solve stuff in production quickly, you might even get a competitive advantage.

How did you solve the problem that phone IP addresses are essentially all NATted? I was looking into this myself, but the fact that phones don’t have a public IP address stopped me.

Can’t say it surprises me with the way Trump is running that country into the ground.

What am I, a caveman?