Suggestions
Milo Todorovich
Milo Todorovich is the Vice President of Engineering at Screencastify, a company known for its screen recording and video editing tools. He has over 30 years of professional experience in software development, highlighting a long-standing career in the tech industry. Based in the Greater Chicago Area, he has built a substantial network with over 500 connections on LinkedIn.
Throughout his career, Todorovich has emphasized the importance of shipping software efficiently and iteratively delivering quality products to customers. He has shared insights on his LinkedIn profile regarding software development practices and the evolution of project timelines in the industry, noting how he has adapted to faster release cycles over the years. His posts reflect a commitment to continuous improvement and innovation in engineering practices.1234
Highlights
“Wherever you pass blame is where you give power to.”
- Alex Hormozi
The key to a rewarding career as a software developer?
Taking RESPONSIBILITY for EVERYTHING.
Let me emphasize that little differently.
TAKING responsibility.
It's on you, it's a choice, for how much responsibility you accept.
And don't kid yourself: the responsibility is their either way. Even if you try and cover it up with blame.
You will go a lot farther when you accept the power rather than giving it away.
It will become contagious. Excellence breeds more excellence.
To get started, choose just one small area, focus on doing the best that's possible, and then expand.
Don't know where to start? Try getting to meetings on time.
- when you accept a meeting invite, set an alert 2 minutes before the meeting.
- check that your alerts show on the screen, AND make a sound.
- when the alert goes off, take 30 seconds to finish your current thought.
- then join the meeting before anyone else.
You will exude preparation and respect, and the rewards will start to stack up.
Excellence breeds more excellence.
🚀 Are you ready to start Delivering Daily?
Like, share, and follow for tips and techniques about Software Engineering, Engineering Management, and Leadership.
Execution is the key to success. In any field.
So what's the right amount of execution, say, compared to planning.
Most experts agree that you would spend 5-10% of your energy planning, and use the rest towards execution.
What does this look like in practice?
Well, let's assume a 40-hour work week. (Acknowledging that this is the wrong formula for most knowledge work, but it keeps the math simple).
In a 40 hour work-week, 2-4 hours per week should be dedicated to planning, and at least 36 hours per week towards execution. Roughly 7-hours per day, on average. (Again, probably less for intense knowledge work, but I hope you see the gist here).
How do you do the planning? Here's how I would start:
-
Schedule 2x 90-minute planning sessions a couple days apart, for example 9am Monday and 2pm on Wednesday. 📆
-
During those sessions, plan out the next 3 days of work for your team. On Monday, plan out through the end of Wednesday, and on Wednesday plan out until the end of the week. 📋
-
Develop a queue for incoming work. When something comes up between planning sessions, add it to the list, then get back to executing. 📝
-
During planning sessions, review your projects and the list of ideas, and pick out what you can do in the next three days. 📓
This simple formula, you maintain a balance between long focused chunks of deep work, and the nimbleness to take in new ideas.
I'd bet most of your stakeholders would be happy to hear: "That's a great idea! We may be able to get started in the next day or two. I will update you after our next planning session on (Monday | Wednesday)." 📣
⚖️ - How are you balancing planning and execution?
🚀 Are you ready to start Delivering Daily?
Like, share, and follow for tips and techniques about Software Engineering, Engineering Management, and Leadership.
