I’ve written on this topic before in a few places (actually quite a few times based on a quick search of this site). But I decided to expand on it a bit for a recent LinkedIn article. If you’re building software, if you want to build great software, you need to start with trust. To take from the article… Software Built on Trust starts with Development but it permeates it’s way through Product Management, Sales,…
How many are in your queue? When are you going to start them? Set a date, jump in, and get going. You paid for it, might as well use it and learn something new. Otherwise, give it away to someone who will. (Not sure you can gift courses in this way, but that would be a cool popup kick to getting going this way).
We all have one. It’s our internal guide for when we start a new team, a new project, a new job, a new something. It’s the four to fourteen steps on what we do when starting up. If you’re a leader it might look like this; Meet TeamFigure out what I do.Meet Manager.Figure out what I need to do.Where is code?Schedule One-On-Ones And the list goes on and on, however long it is for you…
You can’t be everything to everyone. It’s impossible. I realized this a number of years ago as a developer when new frameworks started popping up every day. I couldn’t learn them all and be good at all of them. But I could be good at some of them. Real good. Awesome good. Find your niche, own it, make it your own. Don’t be everything to everyone.
On any project I lead, I encourage Devs to log bugs. Log them all day, every day. That’s the job. You find an issue, you log it. You break something, you log it. No one has an infallible memory and if you are never logging bugs, all you are doing is making yourself look like a slow developer on that one task or story you are desperately trying to complete. Show them what you are…