dpc_01234

Testing is almost unquestionably a benefit (at least to a point) and is something that can be introduced with minimum initial investments and right away gives big benefits. I'd start with that for low effort, big impact.

Then CI (but not CD) is like that too. Just have the test executed on every commit/PR to gain some confidence.

CD requires a whole culture around it, and not everything fits into this culture.

There's really nothing wrong with deploying stuff via SSH. It's not most fashionable, but if done via script and works, it's OK. No need to fight it.

Docker can be great, but people often shove it where it is not needed. E.g. if I was deploying Java (standardized VM) or Go (static bin), I might not bother. It really was invented for Python, where it is impossible to get the Python app running on anything but the developer's computer.

k8s ... mixed bag. Hefty price in complexity, for some benefits that are sometimes important, sometimes not.

The profit, which is what actually matters is up.

> I'm not sure a few 19 year olds are going to do better than this organization. It's hard work.

The problem was never technical. Ever tried to get stuff done in a bloated corporation full of incompetent people that just want to keep their jobs and don't want you to expose how relatively incompetent they are, especially the management? Things that a competent engineer in a startup could do in a day, are impossible to do. And in a government it's probably 1000-fold so.

Dumping some data from legacy system to a modern one is not a problem. The problem is firing people that can't deal with change. "You don't know what you're doing. Everything is sooo complex. You're going to break it. I've been doing it for 50 years, I know what's right."

I also trust government workers to give fair representation of their work. And what you SWE write on their resumes or what OKRs when filling time to justify paycheck. :D

They're a couple of database "tables" and formulas, what else they would supposed to be, think about it. They might be archaic, they might gnarly, limited etc. but they are no match for a modern next.js with react, in a docker container on a VM, running in a AWS datacenter, managed by Terraform, yadaydayda...

People believing what they want to belive.

Not to mention that you talk about revenue and users, because it's hard to deny that technically Twitter is still working just fine, and now even has some new features, while in the past they were coasting tweaking their html for years.

On this very websites, all the "experts" in the industry were bidding how quickly Twitter will collapse after Musk fired all these "irreplaceable" people. Same ones that after 15 year still don't understand how Bitcoin works, or how it can have beneficial impact on the energy market.

To me, just because most of my workflow doesn't need to change irrespective if I'm working locally or via ssh, is already making terminal multiplexer a win.

Also, there's something to be said about terminal just being a more productive way to work with computers. The constrains that a terminal puts on software used in it, make the individual pieces compose with each other way better, precisely because text composes better than graphic interfaces. (That's why "visual programming" will always suck.)

My workflow for decades now is entirely terminal with terminal multiplexer and a browser window. The graphical interface works better for exploratory work when I'm mostly navigating and consuming information, like clicking around the web, the textual interface works better for actual precise control and interaction with software. The "GUI" for me is just for changing if my browser/terminal are displayed side by side or maximized and switching between them.

Let's the take one from #5 in the article. If someone instead of painting this diagram wrote: "Drupal Load Balancer inside Drupal VPC load-balances traffic between Drupal Instances inside two Availability Zones: AZ1 and AZ2" it's way faster to read, more precise, and leaves me without a doubt that I misunderstood or missed some detail.

It's even worse on more complex and busy diagrams. Takes me a while to just visually parse everything, figure out relations between elements, arrows, and even after I scan everything I'm not sure if I understood everything.

On top of it, just creating and later maintaining them is such a hassle, comparing to just editing text.

``` [profile.release] panic = 'abort' ```

A lot of FOSS users conflate freedom with "I get free shit in perpetuity forever" and then whine when they see something that they don't get for free, even if nothing was taken away from them.

Best wishes to the Matrix project.

> In a warning to workers internationally, since the fascist Milei’s government (...)

:D

:D

:D

The way things to do things is very dependent on the project. They way one maintain, debug, test e.g. a math library vs embedded sw vs a video game vs a database vs a enterprise app vs a service in a distributed system are all just different.

Almost all advice should be qualified by "in this domain, one this type of project ...".

I recommend Broken Money for history and analysis how it came to be that things are how they are.

BTW. Somewhat similiar (better sometimes) result can be achieved simply with:

(echo "first"; sleep 1; echo "second"; sleep 0.5; echo "third") | ts -i "%.S"

00.000004 first

00.987787 second

00.501363 third

However, I assume he is some type of an "asshole". And "he'd be even more successful" if he wasn't is just very wrong, IMO. From my experience the top of any organization is completely overrun by assholes. Some smart, some dumb, some more moral, some less, but generally assholes. Being an asshole is selected for in hierarchical organizations and simply required. Part of the reason why leftists dream about some socialist utopia, when attempted in practice is ruined by some asshole(s) taking over power and turning the social utopia into totalitarian distopia.

Unlike most people praising the idea of egoless I don't need to like the guy to learn from him.