1. You don't code to add a feature or whatever. You do it to solve Users' problems. It's a User-centric system.
2. You read more code than you write. So help yourself and write code intended to be read.
3. If people don't know you did something, you did nothing!
4. Never answer a call at 3 am if you're not paid to be on night call-duty. You'll become the guy who answers at 3 am.
5. Remember the big difference between you and me is that I failed to do stuff more times than you have tried to do.
6. When you start shaving the yak, stop!

"shaving a yak shaped peg to fit into a moose shaped hole" 😅 What a strange commit message.

RabbitMQ's claim "RabbitMQ is the most widely deployed open source message broker."

They should amend that line to read "..unless you are trying to install on Windows, then you're screwed .ha ha ha ha"

Two hours fighting permissions, missing (and wrong) paths, having to modify *their* batch files, and still can't access the management UI (and yes, the mgmt plugin is enabled).

I hate this 'shaving the yak' exercise.

Yak shaving...

I have an idea for a fun little web game... A small little learning project.

So of course the first thing I do is write a CLI database change management tool.

Ah Monday. Time for another whole week of meetings, Yak Shaving, Bike Shedding and Can Kicking.

After spending time trying to work in frameworks and new popular environments on my Windows machine(😵), I now don't hate ASP.NET.

After one too many Yak shaving experiences, I am just so happy that it doesn't break the moment I change something. 😭

Let's Shave that Yak!