Knowledge is never enough. But sometimes is hard to know which piece comes first or which step we have to take next.

This is not a comprehensive guide about what to study to become a good developer, and, of course, this is not all the material I have read during my career; most of the things I know come from university degree, courses or direct experience.

This is a small collection of some material I studied and I use to suggest to anyone wants to start to learn something I’ve already learnt or simply needs an advice about what to read to improve in a particular field.

The categorization is totally personal and arbitrary, and the order is almost free. Each content has linked a talk I gave or a summary written by me; hope you’ll find them useful!

Ruby On Rails

Ruby On Rails

Easy, effective and mature; the best language to start to learn OOP.

Follow the path

Good Practices

Good Practices

Good manners, habits and practices ar what makes the difference between a good developer and a great one

Follow the path

Peopleware

Peopleware

Be a good leader is not so easy as it seems.

Follow the path

Javascript

Javascript

The ubiquitos language; no matter where it’s used, a solid background it will always be a good help.

Follow the path

Tecniques

Tecniques

Deal with the past and be prepared for the future is the day-to-day real work

Follow the path

Arquitecture

Arquitecture

Good code is a starting point, good architecture is the right way

Follow the path

Databases

Databases

It’s all about data, and the places where they are stored.

Follow the path

Technologies

Technologies

More stuff I needed to get used to.

Follow the path

Entrepreneurship

Entrepreneurship

We don’t make art, we make money

Follow the path