When I was in university, I remember one of my teachers asking the class… “Does a leader need to know the business they are in to lead?” No middle-ground, no sitting on fences – YES or NO. The answer is/was No. Sure it helps to have some background knowledge in the business and industry, but it’s not required, it’s not a necessity. So what do they need if not knowledge of the business? They need…
Well this one was tricky to write because I’m at fault of this so many times, so I thought I’d take a step back and see what really is holding me back. https://www.lifehack.org/475679/how-to-eliminate-distractions-for-achieving-your-goals
Of course. Whether you’re an architect, lead developer, senior developer or anything else that focuses more on the technical solutions where you have no direct reports it’s not an optional skill, it’s a requirement. You take the lead in the architecture, the design,the creation – but also in the selling of that vision to your team, in the education of the team in how to use a component, in the deployment of that code to…
Understanding the solution… Learning the solution… Breaking the solution… That’s the hard part, because now it’s more than blanket acceptance, now it’s learning, growing, questioning, evolving. The worst answer in a newly implemented solution when it breaks. “I don’t know, I never looked into it” Don’t accept the solution, break it down, figure it out, own it, make it yours. Only then should you deploy it.
The Bulldozer has an idea, a vision, a goal and they are not going to let anyone or anything get in their way. They know how to get from A to B and they aren’t about to let anything or anyone stop them. Have a better route? The Bulldozer doesn’t want to hear it, they want to keep on their path. Have a different idea? See above. Want to try something different? See above. Have…