Matt Aimonetti. Back to articles list
How to become successful rubyist
Matt Aimonetti, a Rails veteran, serious Ruby addict, Merb core team member and now Rails Team member.
I was working in a company that was frustrated by the technology we were using. We looked at different technologies, including Python and Ruby and the engineering team decided to go with Ruby after we fell in love with its syntax and philosophy.
Where, and how, do you search for work now? Can you give me some advice on the best ways to find Ruby related work?
Most of my clients find me by referrals, or because they read my blog or heard me talk at a conference/meeting. Word of mouth is very important in our business and it's probably the best way to keep working on exciting projects. My advice would be to start a blog, write interesting stuff, release an open source project or contribute to other projects.
What advice would you give a Ruby beginner without any projects ready to show?
Get started! If you want to get a job or find clients, you need to be able to prove yourself. Nothing speaks better of a developer than the code he can write.
What books, or sites, or recipes, or whatever else you can recommend (they may be about productivity, or negotiation, or thinking - anything you think will help me live a better life as a programmer)?
How much time per week do you work? How do you keep yourself productive and focused?
My wife and I don't seem to agree on the definition of "work". I bill around 35 hours of work per week. However I probably spend 80 hours developing software. So half of my development time is paid for, the rest is for fun or to help the community. I keep myself productive by working with people challenging me. I'm the most focused when I'm facing a hard problem. Otherwise, take some short breaks, enjoy your weekends and learn to relax to be more efficient when working.
I don't think I have any special organization or tools I use. I try to keep my desk tidy so I don't get distracted ;)
How do recommend becoming a successful and profitable programmer?
These are two different notions. Choose your priorities, if your goal is to make lots of money, you chose the wrong career ;)
My only advice on the topic: be passionate.
What should every programmer know?
That your own knowledge will always be limited, learn how to adapt and solve problems you never encountered, that's what makes good developers.
Thank you!
