sometimes the worst part of being a dev is:
LEGACY CODE.

Trying to explain my family what I do for a living.

The best part of being a dev is that no matter how long you take to solve a problem, you know that even after a whole night of solving issues it will be worth the effort because you will deliver a functional product and there is no best feeling.

Am I the only one crying because heroku is having deployment issues?

That awkward moment when your reputation on DevRant is better than your reputation on StackOverflow... I've failed the community :(

I will always be grateful to those friends that were patient enough to show me how WordPress worked when I had no idea, to the one that encouraged me to start learning rails, etc.

Because I've meet such great programmers that are just horrible persons and I've learn to appreciate my friends who have always been there everytime I couldn't get things around.

I'll always be grateful to you guys :)

Deadline for tomorrow. All I see in my head is:
HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX HOTFIX

When you gotta work on a project you made a year ago and see the bad practices you use to have...

Since I started living by Sandi Metz rules for devs, i feel like my code has really improved.

My favorites:

* Classes can be no longer than one hundred lines of code.
* Methods can be no longer than five lines of code.

I hope you find them as usefull as I did.

Don't you feel sometimes like you may not be as good dev as you think you are? Like all you do is search for chunks of code in stackoverflow so you can assamble a semi functional project.

I'm having one of those days, and it just feels like shit.