Oh man same!

2000s, with permission from the HS computer teacher, I was installing Red Hat on a few computers. It was ROUGH. Like, yeah we got it to show a desktop, but it was a nightmare to use anything but the basic applications. Windows just worked and after a few months, went back to that.

Only during the pandemic did I finally go Linux. Started with ElementaryOS (highly recommend for old people) and went through a dozen other flavors. What really pushed me to expert level was setting up Linux servers.

I no longer code on a Windows machine (unless I have to), and absolutely would recommend Linux to any end user. And now with Steam Deck/SteamOS, it’s only getting better. My gaming computer is still Windows, but I’m going to let it sunset. I barely use it except to play high-spec games that aren’t on Steam Deck. But that’s getting rarer and rarer.

Hey, I was wondering if you can update your commit with a punch in the face, if possible? No pressure thanks for contributing!

Working in open-source, frequent issues do end up being future feature requests.

I took it as software engineers tend to build for scalability. And yep, IT often isn’t prepared for that or sees it as wasted resources.

Which isn’t a bad thing. IT isnt seeing the demands the manager/customer wants.

I’m glad you’ve done both because yeah, it’s a seesaw.

If IT provisions just enough hardware, we’ll hit bottlenecks and crashes when there’s a surprise influx of customers. If software teams don’t build for scale, same scenario, but worse.

From the engineer perspective, it’s always better to scale with physical hardware. Where IT is screaming, “We dont have the funds!”

Accurate!

Developers are frequently excited by the next hot thing or how some billionaire tech companies operate.

I’m guilty of seeing something that was last updated in 2019 and having a look of disgust.

This is like saying before you can be a writer, you need to understand latin and the history of language.

. I think to be a good software developer it helps to know what’s happening under the hood when you take an action.

There’s so many layers of abstractions that it becomes impossible to know everything.

Years ago, I dedicated a lot of time understanding how bytes travel from a server into your router into your computer. Very low-level mastery.

That education is now trivia, because cloud servers, cloudflare, region points, edge-servers, company firewalls… All other barriers that add more and more layers of complexity that I don’t have direct access to but can affect the applications I build. And it continues to grow.

Add this to the pile of updates to computer languages, new design patterns to learn, operating system and environment updates…

This is why engineers live alone on a farm after they burn out.

It’s not feasible to understand everything under the hood anymore. What’s under the hood grows faster than you can pick it up.

Rough and that sucks for your organization.

Our IT team would rather sit in a room with developers and solve those problems, than deal with hundreds of non-techs who struggle to add a chrome extension or make their printer icon show up.

Absolutely agree, as a developer.

The devops team set up a pretty effective setup for our devops pipeline that allows us to scale infinity. Which would be great if we had infinite resources.

We’re hitting situations where the solution is to throw more hardware at it.

And IT cannot provision tech fast enough within budget for any of this. So devs are absolutely suffering right now.

I switched to Linux a few years ago and you are not wrong.

Windows is a nightmare with directory organization.

Saved games can go:

• My Documents/
• My Documents/Games
• My Documents/My Games
• <app>/saved-games

Still waiting on approval for more resources. It’s not a priority in the company.

I swear we have like 4 runners on a raspberry pi.

Envious. It averages 15-30 mins

Losing their jobs? Uh what?

Welp time to spend 3 hours rewatching all the Strongbad emails.

At my job, we have an error code that is similar to this. On the frontend, it’s just like error 123.

But in our internal error logs, it’s because the user submitted their credit card, didnt fully confirm, press back, removed all the items out of their cart, removed their credit card, then found their way back to the submit button through the browser history and attempted to submit without a card or a cart. Nothing would submit and no error was shown, but it was UI error.

It’s super convoluted. And we absolutely wanted to shoot the tester who gave us this use case.

Too real.

We had a consultation last year to better structure our code base to look more like the first picture. Then it slowly evolved back into the second picture.

Haha! Complete opposite.

Giant monorepo that’s delicately balanced and one wrong move can cause the whole thing to flip over.

(Not arguing over what is better. That’s just my life in the past few years, and It’s a stupid argument)

A lot of these old-fashion types are oblivious to social justice and get upset at even the thought that Institutional racism even exists, because they can point to their one black friend in tech who owns a mansion.

I used to get into arguments why master and slave was a problematic word to engineers. That’s how ignorant they are.

Those folks are dying out, especially as more diversity exists. Which is humourous because these folks will also rage about that too.

During the George Floyd Protests, Robert gives us a beautiful take that police stopping black people isn’t racist, it’s just math.

It’s mostly based on what he feels is good.

One of my main issues is, seeing his code in the past decade… It feels like this guy hasn’t coded in a collaborative environment in years.

His personal opinion tends to get on the way with code that’s easier to read from a team perspective. And “Uncle Bob” pushing that as the defacto way to code.

This happens from Influencer types who are so detached from the industry for decades and are no longer aligned with problems real engineers hit.

It’s not that he’s wrong. It’s that his perspective is outdated.