1. Slack. Pretty good chat app for dev companies, I use it to prevent people standing next to my desk 40 times a day.

2. Unit testing tools, especially when fully automated using a git master branch hook, something like codeship/jenkins, and a deployment service.

3. Jetbrains IDEs. I love Vim, but Jetbrains makes theming, autocompleting & code style checks with mixed templating languages a breeze.

4. Urxvt terminal. It's a bit of work at the start, but so extremely fast and customizable.

5. Cinnamon or i3. Not really dev tools, but both make it easy to organize many windows.

6. A smart production bug logger. I tend to use Bugsnag, Rollbar or Sentry.

7. A good coffee machine. Preferably some high pressure espresso maker which costs more than the CEO's car, using organic fairtrade hipster beans with a picture of a laughing south american farmer. And don't you dare fuck it up with sugar.

8. Some high quality bars of chocolate. Not to consume yourself, but to offer to coworkers while they wait for you to fix a broken deploy. The importance of office politics is not to be underestimated.

Savage designers....

So true. But alas, my team doesn't believe in documenting code! 😢

“Our code is our documentation - it’s produced in such a way as to be explanatory, logical and clear, and annotated if/where needed”

Really?? That's the reply you give me when I asking API documentation for handover ?

Gameboy dev kit has parts like these in it's documentation...

Effect of documentation!!!

I find it super annoying, this trend where no one wants to write learning documentation anymore, but instead put up a bunch of demo videos and video "training courses."

I don't want to spend 5 minutes watching you do something that would take me 10 seconds to read. I can't search for terms in your video, and I can't use them as a general reference manual. I can't go at my own pace, easily keep my place between devices, enter code as you go, the list of cons goes on and on.

I would rather pay you money for a good eBook (and no, PDFs don't count), than to have the only realistic way to learn about your software be a playlist on your YouTube channel.

This, however, this...

Went to check out Ansible again, because I've heard good things lately and it's been a couple years since I've looked at it.

Took me a while to find their docs because there's almost no mention of anything on the home page except trying Tower for free.

Found the docs. The first item there is the Quick Start Video and I think, "Cool. That's a good use of video, showing off the product."

I dig out some headphones, click play:

"Ansible is a powerful" BOOM!

Enter my email to watch the video?!

Ah, forget it. Maybe I'll see you next time, Ansible.

Every fkn 3 to 4 days, some random dev shows up in my office really really fkn confused and frustrated about something he doesn't understand - because I have a dark secret.

Sometime, in cold lonely nights, when no one is watching, I write my documentation before the actual code.

Somehow, sometimes documentation without code attached to it makes it to production.

Today someone yelled at me for wasting his time because he wasted 3 hours trying to find the code the documentation belongs to - and demented I stop the practice from now on.

Agh.

May the force be with you

How to play video games on Mac