During my first year of working, I was offered to work part-time at another company. I actually took it to my supervisor and asked for his advice.

He began with a sigh, he knows that I like programming so much and wants the job because I wanna do more programmings. He gathered his thoughts and said calmly, "Look, I cannot stop you if you want to, but think about this, you already are doing programming for five days a week here. Take those extra times you have to develop other parts of yourself. Go learn public speaking or something" or something along that line.

I gave it a deep thought, took the advice, and rejected the offer. I eventually went on to commit myself on volunteering for the next two and a half years, and secured a promotion about a year from that conversation because my supervisor sees improvements in my communications with others and my soft skills in general (unlike programming, you can't volunteer in an organisation without speaking to people).

Sometimes we programmers only wanna code that we forget that what we're building are for humans and involves other humans. You wanna be the best at work? Try to grow on your horizontal axis, too.

If I'm a package.json "coffee" will be listed in my "devDependencies"

My company provides license for Intellij IDEA Ultimate but I've customised my Vim for development according to my convenience so I use Vim instead.

Except for changing variable names across multiple files. IDEA's refactoring is the only thing I am using IDEA for.

I sit right behind the board games table. While it was nice that my company provides games and doesn't mind us playing for destressing, my colleagues played and laughed so loud at the table that sometimes they distracted my work discussions with the other colleagues. Usually when this happens I'll just join them.

One thing I learnt after over two years of working as a programmer is that sometimes making your code DRY is less important than making your code readable, ESPECIALLY if you're working on a shared codebase. All those abstractions and metaprogramming may look good in your eyes, but might cause your teammates their coding time because they need to parse your mini-framework. So code wisely and choose the best approach that works FOR YOUR TEAM.

The pain of using third-party library with unclear documentation.

"Oh just read the code"

well it would've helped IF THE CODECLIMATE RATING ISN'T 0.4. D: