Professional Development – 2017 – Week 22

Dates covered: May 29-June 4, 2017 (week 22 of 52) Career The Engineer/Manager Pendulum (via Software Lead Weekly) A Framework for Learning for Programmers (via Software Lead Weekly) Recovering from a Toxic Job (via Alan Barber) .NET Rocks! 1446: Banish your Inner Critic with…

Professional Development – 2017 – Week 21

Dates covered: May 22-28, 2017 (week 21 of 52) Career Doing the Wrong Thing (via The Software Mentor) .NET Rocks! 1444: Ditching the Hourly Crusade with Jonathan Stark (via .NET Rocks!) Culture Quit Measuring Employee Engagement (via Signal v. Noise) Management The Biggest Mistake…

Outsider’s Architecture Review

  TL;DR — There are several benefits to you, your team, and your project by doing an end-to-end review of a “slice” of an application in which you have no prior experience. Context Our team at work has been assigned…

Professional Development – 2017 – Week 20

Dates covered: May 15-21, 2017 (week 20 of 52) Career How to Improve at Work When You’re Not Getting Feedback (via Harvard Business Review Audible Channel) Communication How to Communicate Effectively as an Engineer Without Resorting to Management Speak (via Software Lead Weekly)…

Professional Development – 2017 – Week 18

Dates covered: May 1-7, 2017 (week 18 of 52) Career Software Entrepreneurs: Stop looking for itches to scratch (via The Software Mentor) .NET Rocks! 1438: The Evolution of Software Development Careers with Erik Dietrich (via .NET Rocks!) Culture The 9 questions that uncover the…

RPM 74 Review

Here’s my quarterly RPM review post giving some details and thoughts about the 2017 Q2 release, RPM 74. I’ll start with my general thoughts for the release, and if you’re interested in a track-by-track breakdown, keep on reading. General Thoughts…

Professional Development – 2017 – Week 17

Dates covered: April 24-30, 2017 (week 17 of 52) Career Software Craftsmanship as Good Business (via Erik Dietrich) Communication How to Reliably Get Your Team to Write Articles for Your Engineering Blog (via Software Lead Weekly) Collaboration Overload Is a Symptom of a…