I like draw.io for process diagrams.
I like draw.io for process diagrams.
When I’m prototyping some model deployment/application/backend, I choose Ubuntu. I’ve also chosen Debian Stable before.
When te decision has been made to actually write the fucking thing for real enterprise deployment, it’s always Alpine Linux so that we have fine control over literally every aspect of the image.
I’d never recommend Alpine for any other use case, tbh.
It was /c/amotio? Pitchforks out; GET ‘EM!
I figure I can probably convert about 10 kg into manure before it autoconverts into compost. Which is maybe even a worse problem.
Would you rather have 100,000 kg of tasty supreme pizza, or 200 kg of steaming manure?
Choose wisely.
I’ve worked for startups too; everyone does everything all at the same time! Let the chaos reign! But it is fun in its own way.
I work for a large company now after the startup I worked for was acquired. Hierarchy, bureaucracy, layers, we’ve got it all. For worse and for better though, it allows me to focus and specialize on what I’m awesome at and furgeddaboddit (ahem! delegate) the stuff that I suck at to those who excel at those tasks.
No, this is incompetent management.
Senior engineers write enabling code/scaffolding, and review code, and mentor juniors. They also write feature code.
Lead engineers code and lead dev teams.
Principal engineers code, and talk about tech in meetings.
Senior Principal engineers, and distinguished technologists/fellows talk about tech, and maybe sometimes code.
Good managers go to meetings and shield the engineers from the stream of exec corporate bs. Infrequently they may rope any of the engineers in this chain in to explain the decisions that the engineers make along the way.
Bad managers bring engineers in to these meetings frequently.
Terrible managers make the engineering decisions and push those to the engineers.
Some people use git to flog, though. See
git blame
Hmm. Attorney charges by the hour and at least 3 discovery hours will be attributed to the time spent learning to exit vim let alone exit with preserving changes.
Still some paperwork in a divorce so you’d probably want :wq!
Not the best choice of typos.
You were born to deploy K8s clusters.
OMG my sides. kubectl delete --all --all-namespaces
I’m a Linux user and fan for a lot of years now. Software engineer by profession.
It’s not ready for widespread adoption to the less tech-savvy masses.
It misses some functionality that is really hard to get right but is absolutely expected to get right. For example: graceful suspend and wakeups. It happens so often even to me that I close my Linux laptop for the day, next morning open it up to a bunch of warnings and error messages about Bluetooth adapters or whatever the device of the day that wants to malfunction is that prevents a sound S2 S3 sleep.
I don’t get freaked out about it. But grandma sure would. And yet my 10 year old MacBook Pro gets it right every single fucking time; completely flawlessly. This is the bar of usability that Linux has to achieve for widespread adoption as a true, polished, personal computing experience.
edit: meant S3 sleep.
Apparently most of their code is not open source.
Hate them or love them, Teslas are run on Linux.
Between the Buried and Me for a representation from the more prog-side of metal. Highly recommend.
Pop!_OS uses flatpaks, not snaps. It’s a good thing.
It’s probably the only Distro I’ll use from now to the end of time, because I’m quite content with it.
Or you’ve invested so much time setting it up that you don’t dare abandon it (sunk cost).
I jest but there may be a grain of truth to it anyway. We humans tend to get comfortable with what we know and when we spend so much time installing, configuring and tinkering a system that we use daily, we end up knowing it pretty well.
I like to try a new distro on a personal computer every year or so, just to keep my agility of computing systems nimble. But still I usually end up back to Pop!OS and MacOS. Although that practice did pull me away from Fedora to Pop!
Also PRISM. Maybe the third—wait, wrong side of the array—worst.