How many manual steps are there in the life cycle of a feature to deploy not related to coding. Logging on to a machine to run 3-5 shell scripts is not fun.
How long on average does a small change take to go through idea to production. If it takes 2 weeks that's probably not good. However, 2 minutes is also not good.
How many people need to be involved in an update. 16 people from 8 teams is too much. But if I am expected to do it all myself without reviews that's also not good.
Also checking code quality and practices but that is more specific.
Last but not least, how well is the team working together. I do not care much about following agile or scrum or any other buzz words. I just want to know if they communicate and mesh well. No internal disputes, no issues with management, everyone is working that sort of stuff. Odds are, if anything is wrong with the team, it is reflected in the project.
I am a hands-on technical consultant w. a focus on cloud application development (specifically AWS) & product development and my goal is to help technical leadership deliver better software.
Location
McLean, VA
Education
BS in Computer Science @ Loyola University Chicago, MS in Computer Science @ Illinois Tech
Work
Consultant Principal Engineer & Senior Software Architect at Coherent Logic Limited
As a developer I like to know a few things.
These are all excellent and thanks for sharing.