Jim has been building solutions for clients in the cloud on Microsoft Azure since 2012 and building solutions in general for 20 years or more. Now, he heads up information technology for biBerk Insurance, overseeing both software development and IT operations. Most of Jim’s experience is in consulting or enterprise with a few forays into product development.
Following the path of least resistance, Jim ended up working primarily with Microsoft tools. The tool you know is the usually best tool to use, so the Microsoft path offers less and less resistance for Jim as time goes on.
On the side, Jim is working on jimsrules.com to share experience and shaky opinions about teamwork and leadership in software development.
Topics of Discussion:
[03:33] There is a shortage of software leaders out there.
[04:22] Jim’s career progression.
[05:26] Pulling back from leadership roles.
[06:54] Recognizing the need to be hands-on and fill vacuums in leadership roles.
[08:35] Embracing T- or V-shaped development.
[11:34] If it isn’t tested, it is broken.
[16:47] Know who your customer is and what your product is.
[18:10] The Innovator’s Dilemma and the importance of asking why things are the way they are.
[21:21] No matter how much experience you have, there is something you can learn from someone with less experience.
[23:29] What we can learn from teen YouTubers.
[24:25] The 10 specific rules; Rule 77 — Minimum Viable Products (MVP) are the start, not the end of a program.
[26:26] Rule #7 about microservices.
[27:52] Applying Conway’s Law.
[33:18] Rule 37 — Automated tests are my pillow.
Rule 59 — A leader’s job is to support the team. Most org charts are upside-down.
Rule 68 — No one is a zero. They either add to the team or take away from it. The question is whether those who are taking away are growing towards a positive contribution.
Rule 74 — Keeping standards high ultimately creates a better work environment.
Rule 75 — When you prepare to teach something, you usually learn more than your potential students.
