I forked yesterday for the first time. I'm pretty thrilled. Not about the few lines of code that I posted. If anyone notices and thinks the feature is a good idea, they'll re-write my bit from the ground up.* What's thrilling is seeing this ecology in operation, for the software development ecology is now where the most rapid learning happens on the planet, outside the brains of infants. Compare how ideas and know-how used to propagate in the software world. It used to be that you worked in a highly collaborative environment, so it was already a site of rapid learning. But the barriers to sharing your work beyond your cube-space were high. You could post to a mailing list or UseNet if you had permission to share your company's work, you could publish an article, you could give a talk at a conference. Worse, think about how you would learn if you were not working at a software company or attending college: Getting answers to particular questions - the niggling points that hang you up for days - was incredibly frustrating. I remember spending much of a week trying to figure out how to write to a file in Structured BASIC [SBASIC], my first programming language , eventually cold-calling a computer science professor at Boston University who politely could not help me. I spent a lot of time that summer learning how to spell "Aaaaarrrrrggggghhhhh." On the other hand, this morning Antonio, who is doing some work for the Library Innovation Lab this summer, poked his head in and pointed us to a jquery-like data visualization library. D3 makes it easy for developers to display data interactively on Web pages (the examples are eye-popping), and the author, mbostock, made it available for free to everyone. So, global software productivity just notched up. A bunch of programs just got easier to use, or more capable, or both. But more than that, if you want to know how to do how mbostock did it, you can read the code. If you want to modify it, you will learn deeply from
The general principles of this rapid-learning ecology are pretty clear.
First, we probably have about the same number of smart people as we did twenty years ago, so what's making us all smarter is that we're on a network together.
Second, the network has evolved a culture in which there's nothing wrong with not knowing. So we ask. In public.
Third, we learn in public.
Fourth, learning need not be private act that occurs between a book and a person, or between a teacher and a student in a classroom. Learning that is done in public also adds to that public.
Fifth, show your work. Without the "show source" button on browsers, the ability to create HTML pages would have been left in the hands of HTML Professionals.
Sixth, sharing is learning is sharing. Holy crap but the increased particularity of our ownership demands about our ideas gets in the way of learning!
Knowledge once was developed among small networks of people. Now knowledge is the network.
Listen up, budding Masters of the Universe about to start boot-camp week at business school (and sign away $100,000 over two years). For all the wonderful instruction at places like Harvard, Wharton and my alma mater, the Stern School of Business at NYU, remember that making money involves so much more than columns in a spreadsheet and the ever shifting assumptions behind them. Keep in mind:
1. If it ain't broke, still fix it. One of the hardest decisions business owners have to make is turning their backs on cash when it's flowing. But that's exactly what you must have the courage to do at times to protect your franchise.
Article Controls
EMAIL PRINT REPRINT NEWSLETTER COMMENTS SHARE 2. Unless you end up at Goldman Sachs, forget what you learned about finance. "In a 12-year finance career with large respected companies," says one of my former classmates, who is finance chief for the unit of a large manufacturing firm, "I can count on two hands the number of IRR [internal rate of return], DCF [discounted cash flow] and NPV [net present value] analyses I have completed." He adds: "A career in corporate finance is nothing like what is taught in school. The job is largely to be the conscience of the business--expecting and demanding explanation for decisions and [being] well versed in most topics."
3. Take your financial models with a boulder of salt. "Too often people in business rely upon a model demonstrating projections out 15 to 30 years," says another biz-school mate, now a health care consultant. Really? In school we worked in more modest 3- to 5-year increments, with an understanding that anything beyond that was magical thinking. "Believe it or not," he went on, "I have seen some done out that far for deals [acquisitions] and often for public-private partnerships."
4. Overpromise and try to deliver. Underpromising and overdelivering may work on conference calls with Wall Stree
This is an aggregator Nancy curates. (I have a similar set-up on Working Smarter, www.workingsmarterdaily.com)
You can search for particular topics from among the sources Nancy tracks.
This question came up in an online seminar this morning. "How can I demonstrate the value of Informal Learning?"
First of all, understand that you're not buying informal learning. It's already going on in your organization. In fact, three-quarters of the learning on and about how to do one's job is informal.
The natural learning that occurs outside of classes and workshops is vital but it probably flies under your corporate radar. No manager is accountable; no department is committed to making improvements; there's no identifiable budget. Hence, one of the most important functions in an organization, keeping up with skills to prosper in the future, is left largely to chance.
Even though most large corporations have a training and development function they are always somewhere on the periphery. For employees, managers and executives alike, training and development is looked on as a nice to have luxury and not as an essential tool of business strategy execution. The general belief is that it helps individuals get better, not the organization as a whole.
In the American and many other Western cultural contexts, individuals are supposed to develop themselves and take responsibility for their own career advancement. The firm has little responsibility to develop employees, relying on the competitive nature of employment and learned self-sufficiency to provide any needed skills. Individual employees as well as managers operate under the belief system that those who take the initiative to learn will and should get promoted. However, reality is often very different with personal prejudices and organizational politics dictating more promotions than merit.
Most corporate learning remains traditional, formal, and follows patterns laid down decades ago by firms such as GE and IBM. While it is hard to fault the content of these programs, as they are usually generic and seem to make sense; there is also little evidence that they make a huge difference to profits, success, or productivity. It is much easier to show that a quality program or a process improvement initiative have more impact than a learning program.
Formal classes and training programs are still the mainstay of corporate learning functions. Instructional designers and professional presenters spend thousands of hours designing training that should, in theory, transfer the needed skills to leaners as fast as possible. Unfortunately there is little evidence that these classes work very well.
This question has implications for the superfluid platform…
Should projects exist in perpetuity or should they be organized around a specific goal?
How open or closed should projects be? How fluid?
What should be the defaults?
Should 'sequels' be assumed or should they require an active reconstitution of a project team?
The point is, it is the most interesting, attractive, high-margin work that spans boundaries and requires a network approach. Firms large and small can comfortably do process work internally, but to get the ground-breaking work they must learn to use open innovation and build external networks into the core of how they work.
Updated design principles
Speed of change, ubiquitous connected networks and intensified complexity arising from abstract, distributed knowledge flows are key features of the emerging wave of smart working. Design principles for performance environments therefore additionally need to focus on complexity, the changing nature of knowledge as power, network viability, mobility and social learning.