Lead/Senior Ruby on Rails Developer, Mentor
I've been developing in a variety of languages on different platforms over the last 15+ years and I'm still enjoying it. Programming is my lifelong passion. The things that excite me the most as a developer are those innovative, unique and technically tricky. The things I try to achieve as a team leader are just these: efficiency and harmony. I see a successful product as a harmonic combination of well-designed software AND a well-tuned team involved in its creation and subsequent development.
I believe that QUALITY is the key priority if you want sustained growth. I provide it, I motivate or otherwise make others provide it. It takes time? Yes, but... "Good cooking takes time. If you are made to wait, it is to serve you better, and to please you."
——— Keywords and samples ———
Solid, long-term, clean, well-documented, maintainable, resilient.
Please read my clients' reviews for more live keywords.
Also, please take a minute to look at my code samples: https://github.com/dadooda/code-samples. There are also some open source contributions in the neighboring GitHub repositories.
——— The DO statements ———
If any of these statements are relevant to you, please DO apply as we'd probably get along together nicely:
* "We had tough experience with Indian developers in our previous project. This time we want to begin by building a solid base which would guarantee us stable growth for the next 3-5 years."
* "We have an ongoing issue in our distributed team: every time a developer leaves, the new one spends weeks becoming familiar with the project. We need someone to take care of connecting new developers smoothly."
* "We like our current developers, but they seem to try new fancy things out of boredom or curiosity. We want to balance it somehow to stop losing momentum because of thoughtless fun experiments."
* "Our current developers are okay writing code, but they get annoyed when being asked to explain or describe something, even to one another. We want a lot more sustained awareness and shared vision between our team members."
* "One of our developers likes Apple, another one is a PC/Linux man. Both are great, but they keep arguing over their preferences which is a productivity killer. We want someone with authority to deal with them both."
——— The DON'T statements ———
If any of these statements sound true, please DO NOT apply since I'm probably not good enough for you:
* "We'll start our new project with cheap student developers. It's then easy to invite a senior guy for a week or two to correct all of their mistakes."
* "We don't need any written specs or documentation. We have Agile, Scrum, XP, pair programming and Slack chatroom instead."
* "Writing project description is a waste of time. We'll start posting Scrum stories right away. A good developer should read our mind."
* "We'll use NoSQL in our new project. Why? We don't know, but blogs are full of statements that it's better than SQL."
* "We've just completed the visual design of our new application. Now we need someone to write code for it, which is a trivial technical procedure."
* "We believe that this alone guarantees our code to be clean and solid: keeping methods shorter than 5 lines and keeping classes shorter than 100 lines."
* "We've had a lot of trouble managing distributed teams. This time we want ONE great developer to handle everything. We can definitely control one person."
Thank you for reading this far. If you're interested, post a job for me or send me a message.