We just (as in, just finished this afternoon) had a whole 2 days of almost exactly this -- realestate.com.au (REA group) has quarterly "hack days", where we work, either independently or in spontaneous teams, on whatever we feel like doing. Mostly, it's related to and guided by technical or product ideas that would benefit the company.
However, what always, always strikes me is that no matter the good idea, and no matter how well thought out and planned it is, it's always going to need a heap of work to make it move beyond the initial concept phase into something that has half a hope of standing the whims and vagaries of a real production environment, with real users.
Whatever project wins the day, gets company support to continue development -- and so far, months of solid work from extremely high-functioning and skilled teams is what it's taken to get anything that can actually be deployed and used consistently. There is no such thing as a quick win, even with a quick good idea.
It all goes to show, hard work always wins in the end, and execution is more often than not the downfall of so many otherwise great ideas.
The project written about in the linked article, which might seem like a simple piece of controllable hardware, will require months of significant time and effort from many, many dedicated folks to reach reality as a manufacturable product, but that's the same as almost anything that successfully sees the light of day. TANSTAAFL, indeed.
The interesting thing about modern systems of involvement is that it's entirely possible to assist a project along its way, without having to be a marketing genius, technical whiz, or market playing venture capitalist. As we see in our hack days, lots of little pushes can make more difference in some cases than one big push.
I would have thought that support for this architecture would have been useful to keep, since a lot of rad-hardened systems (think space, satellite applications) still use it.
However, what always, always strikes me is that no matter the good idea, and no matter how well thought out and planned it is, it's always going to need a heap of work to make it move beyond the initial concept phase into something that has half a hope of standing the whims and vagaries of a real production environment, with real users.
Whatever project wins the day, gets company support to continue development -- and so far, months of solid work from extremely high-functioning and skilled teams is what it's taken to get anything that can actually be deployed and used consistently. There is no such thing as a quick win, even with a quick good idea.
It all goes to show, hard work always wins in the end, and execution is more often than not the downfall of so many otherwise great ideas.
The project written about in the linked article, which might seem like a simple piece of controllable hardware, will require months of significant time and effort from many, many dedicated folks to reach reality as a manufacturable product, but that's the same as almost anything that successfully sees the light of day. TANSTAAFL, indeed.
The interesting thing about modern systems of involvement is that it's entirely possible to assist a project along its way, without having to be a marketing genius, technical whiz, or market playing venture capitalist. As we see in our hack days, lots of little pushes can make more difference in some cases than one big push.