Microservices:
Several instances of the top panel each doing one of the steps on the bottom panel.
Microservices:
Several instances of the top panel each doing one of the steps on the bottom panel.
Oh, man, the people that design most REST APIs got loose!
Hum… The US is imploding in general, but there’s nothing on the horizon that could collapse the IT job market.
Yeah, doesn’t look like APL to me, but I don’t know it well enough to tell for certain.
Either way, that much code in a language that is at least as concise as APL… what is this? a full office suite?
You should really not need to do a PR across multiple repos. If you need, you are breaking your code wrong. Some functionality may require multiple PRs, but you should always be able to do those at different moments and test them separately.
The monorepo tools are exactly software that emulate the features of a multi-repo so that you can have thousands of people on the same repository. We also have multi-repo tools that emulate the features of a monorepo, but people don’t hype those online because they are simple and free.


Yeah, let’s pretend the vibe-coder creates praiseworthy code when everything is working…


I hope all those companies go bankrupt, people hiring those CEOs lose everything, and the CEOs never manage to find another job in their lives…
But that’s a not bad second option.
Early 80s: High level structured languages (Hello COBOL!)
Late 80s: 4th generation languages
At least before that people just assumed everybody that interacted with a computer was a programmer, so managers didn’t have a compulsion when hearing the name and decided to fire all programmers.


Well, if anybody can do a “terminator 2” and literally walk out of it, it’s him.


Looks like just a good policy to me.
Yes, I’m not doing almost any of the things we do at work in my network.
I’m absolutely not running the same software. I’m not organizing the information the same way. I’m not using the same infrastructure abstraction, and even less configuring it in any similar way. I’m not writing the same languages.
The work environment is dictated by consensus between many people, with varying expertise, and weighted by how much work one is willing to put into each aspect of it. Each of those parts lead to bad tech, even though they lead to good people organization.
“Everything I do at work, I try out at home first.”
Absolutely no fucking way! And anything that touches work is isolated, their opsec sucks so much they didn’t even realized they mandate “security solutions” with known backdoors.


Hum… The brain links are way less direct, that’s for sure.


Looks like you are trying to describe the Federation…
One edits files in place, interactively. The other edits streams i.e.batch processing.
You want sed -i -f -
ed is also the precursor of sed, and of some other dozen of commands.
No, we don’t. This is a completely unrelated problem.
Keep your requirements orthogonal, people!!!
Somehow, despite being the standard it doesn’t come installed by default in any distro I’ve tried.
They all insist you use sed… that bloated thing!
To be fair, the biggest footguns are the trigraphs, and now that I tested those do require a flag in gcc.
The digraphs are just hard to search, never used operator symbols.
The examples on the meme don’t bind any variables. If those are lambdas, the Haskell version is just the part.
Following the modern C conventions, the text following the series of (gnu) doesn’t matter and you can write anything you want there.