What is life for? To follow your passion. What is my passion? I find myself frustrated with the closed source, closed development nature of many professional projects; and on the flip side equally frustrated with the trivial nature of academic "toy" problems designed for "learning".
I love the "in principle" openness of the academic sphere and the "reality bites" of real professional projects. I say "in principle" about academic openness, because while the results of many experiments are made freely available, sharing the source code and data (let alone allowing openness as to the process) is often an afterthought if it is there at all. The MOOC revolution has exposed the contents of many university courses which is a fantastic step forward, but the contents themselves are often removed from the reality of professional projects, being "toys" created for the purpose of learning.
Toy problems for learning makes sense if we assume that learners will be intimidated or overwhelmed by the complexity of a real project. Some learners might be ready to dive in, but others may prefer to take it slow and step by step. That's great - I just don't personally want to be spending my time devising toy problems, or at least not the majority of my time. Also it seems to me that the real learning is the repeated compromises that one has to make in order to get a professional project out the door; balancing the desire for clarity, maintainability, readability and craftsmanship against getting features delivered and actually having an impact that someone cares about.
Professional projects are typically closed source, closed development; although there are more and more open source projects in the professional sphere; the basic idea seems to be: we are doing something special and valuable, and we don't want you to see our secret sauce, or the mistakes we are making along the way. Thus it might be considered anti-competitive for a company to reveal too much about the process it uses to develop its software products. That said, companies like ThoughtBot publish their playbook, giving us an insight into their process and perhaps increasing our trust that their process is a good one. Even so we don't get to see the "actual" process, and so that's not ideal for others trying to learn, but then most companies are not trying to support the learning process for those outside.
Personally I want to have a global discussion that everyone can take part in, if they want to. I want an informed debate about the process of developing software where we have real examples from projects - real processes - where we can all look at what actually happened rather than relying on people's subjective summaries.
Maybe this is just impossible, and an attempt at the pure "open development" process of AgileVentures is destined to fail because by exposing exactly how we do everything we can't build up value to sustain our project? That's what professional companies do right? They have a hidden process, focus attention on the positive results of that process and then increase the perception that they have something worth paying for. To the extent that they are successful they are building up reputation that will sustain them with paying customers, because those customers are inclined to believe the chance is good they'll get value for money.
If the customer had total transparent access to every part of what goes on, they could just replicate it themselves right? :-) Or a competitor could provide the same service for less? However there's a strength in openness - it shows that you believe in yourself and you demonstrate that you've followed the hard path through the school of knocks and maybe you are the right people to be able to adapt fast to the next change, even if others could copy aspects of what you do.
Everyone should have the opportunity to learn and boost their skills by taking part in such an open process. The shy might not want to participate directly, but they can learn by observing a real process that they won't have till they can actually start in a job. It's the old catch-22 "no job, no experience; no experience, no job".
This is what I stand for, what AgileVentures stands for. An open process beyond open source, we call it "Open Development". Meetings with clients, planning meetings, coding sessions, everything is open and available to all. Where customers have confidential data, that is hidden, but otherwise we are as open as possible. Of course that generates too much material for anyone to absorb, and we need help curating it, but the most amazing learning happens when new folk engage and take part in the process - thinking about the code in their pull requests in relation to the needs of a non-technical client being articulated by a project manager who cares about their learning, but also about the success of the project. Come get involved, be brave, be open and get that experience that you can't get without a job, or that you can't get in your current job.