funkyboy

Go out with your friends and have fun. You'll have plenty of time to spend coding in front of a screen :)

Just released a companion Chrome extension to affiliator.io. 5 new spots are available for beta testers. Sign up here: http://www.affiliator.io/signup.html

I am building affiliate links manager for bloggers and podcasters and I am looking for beta testers.

Sign up here :) http://www.affiliator.io/signup.html

True, the point is that you are learning a moving target.

Some people in the community are excited by this, because they have something new to learn.

Others are pissed, because code that worked yesterday doesn't work anymore.

I am working on https://www.podrover.com. It's totally self funded. I didn't quit consulting yet, but I am happy with how it's going. My suggestion is to start your side project right away, regardless of whether you think it will be profitable or not.

I feel the only "tool" to make email less painful is to teach people how to use it.

Everything mentioned (IDEs, typing, automation) is a great advice. But the greatest advice I have been given is "the best code is the one that you don't write". And that's true in my experience. More code means more mess when you have to debug. It also means more time for another developer to get acquainted with your project. So before writing something I often ask myself "do I really need this?" It can be a function, a class, a module or even a graphical asset. It helped me a lot, both on client and personal projects.

Before you jump to the “he made it so I can make it too” conclusion let’s put those numbers besides other facts/numbers ...

I wrote a little post to put those numbers in perspective: http://www.upbeat.it/2015/01/16/putting-marcos-numbers-in-pe...

Why?