m1keil

I don't think symantics really matter here. I largely think of "tech" as companies that produce mainly virtual goods in the form of software. Most of these software is largely skins over databases. In most cases, nobody will get hurt if their product will malfunction. This is the vast majority of tech companies today. Exceptions exists.

I would take under process any day of the week. From my experience, adding a process is far easier than removing it.

Folks let's be real. While the tech industry borrows terms and procedures from mature and inherently riskier industries like Aviation, 99% of the tech companies don't share the same risk profile.

This means that in most cases, these RCAs are the output of a long and over engineered incident review process that was designed to impress the higher echelon.

The problem is, that in a decently sized corporation, you have tens to hundreds of daily fuck ups (also known as "incidents") that completely suck out the free time out of engineers that have to navigate the long game of post incident management process.

The utilisation of LLMs on these cases are just engineered solution to the problem of organisational bureaucracy.

makes sense, thanks for the correction.

Yep.

I assume everyone already knows that, but shellcheck is great help if you need to go all the way down to POSIX since it will detect /bin/sh shebang and warn about any non-compatible bash-ism.

> I don’t know why I don’t hear this point get more airtime among people when discussing the pros and cons of Python/Perl as scripting languages.

But it is.

Perl and awk one liners are very common. Bash is used everywhere you have the (controversial) `sudo curl .. | bash -` install method.

Ansible, if I'm not mistaken, requires python3 installed on remote hosts.

If your environments are homogeneous enough, and you don't have a large matrix of operating systems, you should definitely use this advantage.

The troubles start when you have very heterogeneous environment, custom or hardened Linux distros and etc.

It might seem like this is not being utilised as much nowadays, but I suspect it's because the "classical" Linux sysadmin roles are rare and you don't hear about it as much.

Cosmo looks so cool. Are there any big projects out there that use it for distribution?

Why it has to be about excitement? Some of us read history books, for example, out of pure curiosity.

why not?

I think it's all of the above.

In large enterprises, there is usually some sort of global message bus on top of Kafka, AWS Kinesis or similar.

In smaller shops, the need for dedicated message bus is over engineering and can be avoided by using the db or something like redis. It is still a message queue, just without a dedicated platform.

I listened to the audiobook and didn't get the same impression. I wonder if it's audio related.

Not the same error. It seems like the arm64 dmg is indeed broken/corrupted. The amd64 build works (with Rosetta) - after bypassing the security warning.

Ah, that makes sense, cheers.

That's pretty interesting. What would be an example use case of this?

This article is largely feels like a 3 to 4 Cloudflare blog/articles summarisation. If you want more of this stuff, check CF's learning centre: https://www.cloudflare.com/learning/

Examples: https://www.cloudflare.com/learning/dns/what-is-dns/ https://www.cloudflare.com/learning/ssl/transport-layer-secu... https://www.cloudflare.com/learning/performance/what-is-http...

Yes, Oracle loves making money.

It is not Oracle who are using terraform, it is their customers. Terraform is the underline tech that powers the tooling suit that the customers use to manage their oracle cloud.

It makes perfect sense for them to push their customers to move to the more permissive licensing to avoid any legal issues.

Unrelated to crypto: Trying to select the word "entropy" (with the cool colour & wave effect) grinds Chrome to halt on Android.

Back when Mitchell left, I commented the following "I hope Hashicorp will manage to find its stride and not end up as some bullet point in a long "solutions" portfolio of some software conglomerate.".

Hearing about the intention to sell and now IBM... well, that sucks.

Never heard of Niri before. Will take a look, cheers.

Thanks, will take a look.

Does anybody knows about a tiling WM that allows customising the position of the first window you open? I have an ultra wide display, and I want the first window I open to be roughly 1/3 in screen width and placed in the centre. From memory of playing with i3/sway, it would allow different layouts but the 1st screen would always be full screen and I would have to do something like choose "thirds layout" and "open terminal, open app I want, open terminal".

Hardly an exceptional case. A lot of web shops use auto scaling as means to save money, not to respond traffic spikes like black friday's.

What is easier, having a bunch of powerful servers that provides you enough headroom or having to fight your auto-scaling group to have just enough capacity and in the end of the day still costing more?

I didn't claim there is a problem. The original comment made it sound as if docker will expire a cached layer because the (potential) result of apt-get is different, which isn't the case.

In Docker, if the layers are cached, the layer with apt-get won't be automatically invalidated (unless --no-cache or any changes to the upper layers).

I share similar caution with tools and multi-platforms (specifically Mac, Win & Linux). However, the format is interchangeable with other Ascii drawing apps and it isn't too expensive. So I'm totally fine with it.

Ah! I vaguely remember rage quitting over the crows but didn't remember which book was it. I should give this another try then.

Related: Command and Control by Eric Schlosser

Great book.

Apple's Terminal.app had similar functionality for a while: CMD+Up/Down to navigate between past commands and quick selection of command outputs.

Other terminals, like iTerm (MacOS only), Kitty, WezTerm and so on also have similar options, usually behind some sort of "shell integrations" feature.

I think it is perfectly fine to get angry at Apple in this case because the change is only in the EU...

I agree with you but I also don't see how using source control is a solution to any of it. In my experience, repos go orphan quite regularly in large companies. In the end of the day, documentation requires maintenance.

With that said, there are times where docs in source control are totally viable, especially when their scoped to the repo they are located in.