How to get better at developing software
“We are uncovering better ways of developing software by doing it and helping others do it.” - Manifesto for Agile Software Development, 2001
Do it. Help others do it. The first words of the Agile Manifesto.
RubySteppers are doing it and helping others do it. We started by organizing as a group and gathering the courage to work on something new and unknown. We pushed 40 lines of code to GitHub, a simple artifact of the real-time collaboration taking place.
Fast-forward a few weeks and a few more mobbing sessions and we have an open source project well underway. We’ve added new features that we use every time we mob. We’ve refactored the code to be modular. We’ve created acceptance tests and unit tests. We’ve added features and fixed bugs using TDD. We’ve helped one another learn, and we’ve helped others learn by sharing videos and source code. The best part? We’ve only gotten started.
Tutorials and videos have you spend some time making software, but most of your time is spent reading tutorials and watching videos - NOT DOING IT.
Code schools focus on practice, but make you go through a “learning how to program” phase first before you can start to make software. They pretend there’s some magical point where you’ll be ready to make software for real - conveniently, at the end of their curriculum. As for me, I’m still scratching my head wondering how to afford $17,780 for three months tuition on top of San Francisco room and board. NOT DOING IT.
Your learning will never end. Given that understanding, your next move is to cut out everything that stands between you and working on real software projects. RubySteps helps you get better at making software by giving you a place to work on real software, with real people who are committed to learning and sharing.