Things I Learnt The Hard Way - Take Responsibility For The Use Of Your Code

This is hard. Very very hard. It's the difference between "freedom" and "responsibility".

Read more  ↩︎

Things I Learnt The Hard Way - If It Doesn't Run On Your Computer, You Have A Problem

I've seen a lot of systems that would never run on a isolated computer, like the developer tool, 'cause the system requires running on a specialized environment. Those things are wrong.

Read more  ↩︎

Things I Learnt The Hard Way - Learn To Say No

Sometimes, you'll have to say no: No, I can't do it; no, it can't be made in this time; no, I don't feel capable of doing this; no, I don't feel comfortable writing this.

Read more  ↩︎

Things I Learnt The Hard Way - When It's Time to Stop, It's Time To Stop

Learn when you can't code anymore.

Read more  ↩︎

Things I Learnt The Hard Way - Companies Look For Specialists But Keep Generalists Longer

If you know a lot about one single language, it may make it easier to get a job, but in the long run, language usage dies or loses its charms and you'll need to find something else. Knowing a bit about a lot of other languages helps in the long run, not to mention that may help you think of better solutions.

Read more  ↩︎

Things I Learnt The Hard Way - Keep A List of Stupid Bugs That Took More Than 1 Hour To Solve

If it took you more than one hour for you to figure out what went wrong, it is a good idea to put it on list, 'cause these things have the tendency to appear again.

Read more  ↩︎

Things I Learnt The Hard Way - Units Makes Things Clear

You know what's one of the worst function names ever? sleep().

Sleep for how long? It is seconds or milliseconds?

Read more  ↩︎

Things I Learnt The Hard Way - Think About The Users

Think how the data you're collecting from your users will be used -- this is more prevalent on these days, where "privacy" is a premium.

Read more  ↩︎

Things I Learnt The Hard Way - Code Formatting Tools Are Ok, But No Silver Bullet

One thing a team may decide to fix the continuous flux of code style comments in a code review is to use a code formatting tool to auto-format the code. That's ok, but they should never rely on it.

Read more  ↩︎

Things I Learnt The Hard Way - Code Reviews Are Not For Style

When doing code reviews, do not focus on style; focus on design things that look a bit weird.

Read more  ↩︎