https://osmarpetry.dev/tags/career/Recent content in Career on Osmar PetryHugoen-USTue, 15 Apr 2025 00:00:00 +0000https://osmarpetry.dev/blog/software-engineer-decisions-2015/Tue, 15 Apr 2025 00:00:00 +0000https://osmarpetry.dev/blog/software-engineer-decisions-2015/<h2 id="abstract">Abstract</h2> <p>Based on 59 interviews with senior Microsoft engineers (Meyer, Zimmermann, Fritz, ICSE 2015). Identifies 53 characteristics grouped into personal qualities, decision-making, team impact, and product impact. Focus here is on decision-making skills that differentiate top engineers.</p> <h2 id="key-points">Key points</h2> <ul> <li>Deep knowledge of organisational context (people, priorities, constraints).</li> <li>Ability to switch between big-picture vision and low-level details.</li> <li>Balancing short-term deliverables with long-term maintainability.</li> <li>Evaluating risks and trade-offs before committing to technical choices.</li> <li>Creating shared context: ensuring stakeholders understand constraints.</li> <li>Fostering psychological safety so teammates surface concerns early.</li> <li>Anticipating future needs; keeping options open for future change.</li> <li>Honesty and transparency in communicating limitations or unknowns.</li> </ul> <h2 id="connections">Connections</h2> <ul> <li>Aligns with soft-skill emphasis: empathy, collaboration, cultural awareness.</li> <li>Supports literature on leadership, team coordination, and human factors in project success.</li> <li>Critiques traditional curricula (ACM/IEEE) for insufficient real-world detail.</li> </ul> <h2 id="questions">Questions</h2> <ul> <li>How to cultivate these 53 traits under tight deadlines?</li> <li>Which traits matter most in startups vs large enterprises?</li> <li>How to measure and reward decision-making soft skills in performance reviews?</li> <li>How much does organisational context enable or limit development of these traits?</li> </ul> <h2 id="personal-reflections">Personal reflections</h2> <ul> <li>Excellence extends beyond technical mastery; requires self-development, empathy, systems thinking, and collaboration.</li> <li>Leaders must build psychologically safe environments to encourage healthy decision-making.</li> <li>Curriculum reform should focus on practical, context-aware training.</li> <li>Use findings to guide career development and performance evaluation discussions.</li> </ul> <h2 id="references">References</h2> <ul> <li>Meyer, A. N., Zimmermann, T., &amp; Fritz, T. (2015). <em>What Makes a Great Software Engineer?</em> ICSE Proceedings. <a href="https://www.researchgate.net/.../What-Makes-a-Great-Software-Engineer.pdf" target="_blank" rel="noreferrer">https://www.researchgate.net/&hellip;/What-Makes-a-Great-Software-Engineer.pdf</a></li> </ul>https://osmarpetry.dev/blog/teach-yourself-programming-ten-years-2001/Tue, 15 Apr 2025 00:00:00 +0000https://osmarpetry.dev/blog/teach-yourself-programming-ten-years-2001/<h2 id="abstract">Abstract</h2> <p>Peter Norvig critiques promises of learning programming in weeks. Drawing on research in chess, music, and sports, he argues true mastery requires about ten years of deliberate practice—progressive challenges, feedback, and continual improvement. There are no shortcuts: success comes from sustained effort and critical self-analysis.</p> <h2 id="key-points">Key points</h2> <ul> <li>Questions the abundance of “Learn X in 24 Hours/21 Days” books.</li> <li>Excellence in any complex field typically demands ~10 years of deliberate practice (citing K. Anders Ericsson’s work).</li> <li>Historical examples (Mozart, Beatles) show their peak came only after years of intense practice.</li> <li>No magical formulas; commitment to long-term learning is essential.</li> <li>Practical advice: explore multiple languages, seek challenges, learn from peers, blend theory with real projects.</li> <li>Books alone are insufficient; hands-on experience is irreplaceable.</li> </ul> <h2 id="connections">Connections</h2> <ul> <li>Ties to deliberate practice theory and Malcolm Gladwell’s “10,000 hours” popularisation.</li> <li>Informs discussions on computing education and depth vs superficial knowledge.</li> <li>Supports lifelong learning and career development perspectives in tech.</li> </ul> <h2 id="questions">Questions</h2> <ul> <li>How to balance theory and deliberate practice?</li> <li>Does the “ten-year” model apply uniformly across computing domains?</li> <li>How to maintain motivation through multi-year learning journeys?</li> <li>Which strategies accelerate progress without sacrificing depth?</li> </ul> <h2 id="personal-reflections">Personal reflections</h2> <ul> <li>Reinforces patience and persistence when building programming expertise.</li> <li>Relevant to today’s culture of immediacy—reminds us depth takes time.</li> <li>Agrees that combining study, deliberate practice, and real projects yields steady growth.</li> <li>Encourages valuing the learning process rather than chasing quick wins.</li> </ul> <h2 id="detailed-notes">Detailed notes</h2> <ul> <li>Abundance of quick-learning resources doesn’t reflect real mastery requirements.</li> <li>Deliberate practice: constant challenge, error analysis, improvement.</li> <li>Role of mentors, community, and diverse language exposure.</li> <li>Suggested languages: Python, Scheme, JavaScript, Alice, Squeak, Blockly (depending on learner profile).</li> <li>“Ten years” is illustrative; the key is sustained, deliberate work.</li> <li>Original essay: <a href="https://norvig.com/21-days.html" target="_blank" rel="noreferrer">https://norvig.com/21-days.html</a></li> </ul>