I see you’ve met my ex wife.

I think I’d just get tired of bacon.

Only the original is delicious

Wait, cyber trucks hava a liver?

I never expected something to take that from the Pontiac Aztek

Wait, you’ve never wanted to drive a doorstop?

The worst is when you start to have conversations in your head in multiple voices. It gets crowded sometimes.

Why, can’t you ask yourself? 😁

Micro services alone aren’t enough. You have to have proper observability and automation to be able to gracefully handle the loss of some functionality. Microservice architecture isn’t a silver bullet, but one piece of the puzzle to reliable highly available applications that can handle faults well

Like if everytime someone mentioned the usa people were like “Oh are you afraid of being shot? bet you have to constantly watch out for being shot huh? shot?”

As an American, I kinda am…

Poseidon?

It’s not innovative anymore, but it sure was when it released. But they kept it near its peak instead of making it utter horse crap.

I’ve been sick… I’m pretty sure I may have bought this toilet paper.

I can’t disagree with this… After basing the size off of the vertical pixel count, we’re now going to switch to the horizontal count to describe the resolution.

1gb symmetrical $70 a month…

You aren’t wrong… But everything with extended use needs to be maintainable. Making a change in 5 places sucks.

Plus, that’s what open-closed principle is all about. Instead of adding additional functionality to current working code, you extend and modify.

(☞ﾟヮﾟ)☞

Like this:

ᕕ( ᐛ )ᕗ

The thing to think about is reusability. Are you copying and pasting code into multiple places? That’s a great candidate to become a class. If you have long lived projects (i.e. something you will use multiple times over a lot of years) maintainability is important. Huge functions and monolithic applications are very hard to maintain over time.

Break your functionality out into small chunks (methods and classes). Keep it simple. It may take a while to get used to this, but your time for adding additional functionality will be greatly improved in the long run.

A lot of great programmers were terrible at one time. Don’t let your current lack of knowledge of principles stop you from learning. One of the biggest breakthroughs I had as a programmer is changing how I looked at architecting applications. Following SOLID principles will assist a lot in that. Don’t try to understand and use these principles all at once, take your time. Programming isn’t what you make your living with, it’s a tool to help you be more efficient in your current role.

Realize that becoming a more effective programmer is different for everyone. Like you, I was self taught. I was a systems and network engineer that decided to move into software development. I’ve since moved into a role that takes advantage of all the skills I’ve learned through the years in SRE. like you, a lot of what I write now is about automation and analysis.

Taylor Hawkins?