They really thought they can sprout gibberish and mic drop. Discount Ben Shapiro over here.

Every single post about ad blockers will be someone talking about how “good” Brave is. Drives me crazy.

I’m laughing way too hard at this.

Honestly this is the best answer.

Like, use the tools that work for your use case?

I fucking hate macs but man using a video editor on windows was a pain back in the day. Where I would rather set up a server on Linux, than use whatever the hell windows servers operate.

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.

For those out of the loop:

1. There’s WordPress (the non-profit and open-source software), and Automattic (which runs for-profit companies like a paid WordPress, Tumblr, Gravitar, etc).

2. Automattic (Matt’s company) pays their devs to support the open-source software.

3. Lots of companies sell WordPress hosting.

4. Matt is calling out WP Engine for not just using WordPress without a lot of contribution back to the open-source software, but also selling a chopped up experience.

The metaphor would be: imagine if a company selling tablets contained VLC, bragged about all the movies you can watch, gives back very little to VLC, and you can’t use the playlist feature.

Also, not trying to shit on WP Engine. This is the post everyone should get to see.

https://www.briancoords.com/the-wcus-closing-i-wish-wed-had/

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)

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.

I’m not as much vitriol as others about Clean Code, but I will argue that engineers who preach the book as some sort of scripture are really obnoxious.

I love the Single Responsibility Principle, in theory.

What I don’t like is when devs try to refactor everything to that idea to achieve “Clean Code”. I’ve seen devs over-architect a solution, turning one function into many, because they don’t want to break that rule. Then point to this book as to WHY their code is now 20x longer than it needs to be.

It also doesn’t help that every recommendation about good programming books include this.

It’s like recommending a Fitness book from the 70s - information made sense at the time, but new research has made a lot of the advice questionable.

My main issue is the whole “Uncle Bob” persona. Robert C Martin is sexist and a racist, and has been uninvited by conferences. We don’t need that type of toxicity in the industry.

Is there a article about this I can find more info about this?

It’s a brand new topic for me and I just read this one from a previous comment. And trying to learn more.

Oh that’s super helpful and incredible.

I’m not familiar with that side of Linux as I’m primarily a user. But that’s how our devops pipelines work to ship apps/websites. We’re shopping the entire working package with every update, and rolling back with issues. It’s a fantastic system since as a developer, I can isolate problems.

I never thought about that on a OS level. And I support it!

Sorry I’m too stupid to understand this joke. Someone explain?

Average Linux solution.

“Got an emergency? It’s so EZ. Just open up the terminal and copy/paste [long string of unreadable text]. Btw fuck windows.”