| A few starter concepts to consider: ============================== Didn't find relevant HN article(s) covering age / creativity and software productivity and why software engineers tend to be under 30. *** Does Creativity Deline With Age? : https://ogg.osu.edu/media/documents/courses/700.04A/pdf/does_creativity_decline.PDF
==============================-- Miscelaneous blurbs from recent HN posts about software design to keep in mind: *** Great scientists follow intuition and beauty, not rationality. : http://www.theintrinsicperspective.com/p/great-scientists-follow-intuition
*** Software Design is Knowledge building: http://olano.dev/blog/software-design-is-knowledge-building/
*** Design leader Dilemma : http://www.smashingmagazine.com/2024/12/the-design-leader-dilemma/
*** On design prototyping : https://medium.com/design-bootcamp/on-design-prototyping-fb655e715f29
==============================-- Different approach methods: ** Google 20% rule
http://www.cnbc.com/2021/12/16/google-20-percent-rule-shows-exactly-how-much-time-you-should-spend-learning-new-skills.html
** One-on-Ones as way to figure this out
http://hypercontext.com/one-on-one-meeting-guide
http://www.dave-bailey.com/blog/one-on-ones
http://lattice.com/articles/the-ultimate-managers-guide-to-leading-effective-one-on-ones
==============================Use "google 20% rule" with employee suggested exploratory ideas/topic(s) from one-on-ones. |
The real missing part is discussed in the "knowledge building" link. I'm on board with Peter Naur's idea of building software, but it's very difficult to share individual knowledge with a team as it is being formed.
For example, reading someone's implementation as a work in progress is a different than reading an implementation that is a complete idea.
A work in progress is a lot easier to read with a design document in hand, but that design document that is full of assumptions that might be better explored in short feedback loops on production.