Dr Milan Milanović — Chief Roadblock Remover and Learning Enabler | Helping 400K+ engineers and leaders grow through better software, teams & careers | Author of Laws of Software Engineering | Leadership & Career Coach
Chief Roadblock Remover and Learning Enabler | Helping 400K+ engineers and leaders grow through better software, teams & careers | Author of Laws of Software Engineering | Leadership & Career Coach
Dr Milan Milanović ranks #101 of 14,983 LinkedIn creators in Information Technology & Services, and is a standout voice in Serbia. They have 273.5K followers and published 50 posts in the last 30 days at a 0.1% average engagement rate.
- 273.5K followers
- 50 posts / 30d
- 0.1% avg engagement
- — follower growth / 30d
The roast
Milan calls himself a Chief Roadblock Remover, which is a poetic way of saying he spent twenty years in every industry just to figure out that the only thing stopping progress was people like him. He’s written the Laws of Software Engineering for a quarter-million people who all know exactly how to ignore them.
About Dr Milan
I help engineers, architects, and engineering leaders make better decisions about software systems, teams, and careers.I’m the author of Laws of Software Engineering, a book about the principles and patterns behind successful software systems, products, and teams.I’ve spent 20+ years in software engineering across finance, banking, energy, transportation, insurance, telecom, and product engineering.My work has covered architecture, engineering leadership, delivery, cloud systems, team performance, and organizational change. I’ve worked as an engineer, architect, engineering leader, coach, trainer, and consultant, which gives me a wide view of how software succeeds and why it often fails.Today, I write for more than 400,000 engineers, managers, and architects across LinkedIn, X, my blog, and my newsletter.I write about software architecture, engineering leadership, technical decision-making, career growth, team performance, and the hard parts of building software in the real world.My goal is simple: help technical people build better systems, stronger teams, and more successful careers.Alongside writing, I work as an engineering leadership coach, trainer, and consultant. I help engineering leaders improve strategy, communication, decision-making, focus, team performance, and career direction.I also hold a Ph.D. in Computer Science. I’ve published 20+ papers and book chapters in international conferences and journals, with 440+ citations and an h-index of 11 on Google Scholar.I’ve served as a reviewer and program committee member, and have been involved with ACM, IEEE Computer Society, and GOAI Research Group.Topics I write and work on- Software architecture- Engineering leadership- Technical decision-making- Building high-performing teams- Engineering strategy- Product and project delivery- Agile methods- Career growth- Coaching and mentoring- Cloud and Azure- .NET and C#- DevOps cultureFollow me for practical ideas on software engineering, architecture, leadership, career growth, and building better teams.For coaching, consulting, speaking, or collaboration, send me a LinkedIn DM.
Highlights
- Big Audience — 273,472 followers · top 1%
- Top 1% in Information Technology & Services — Ranked #10 of 1652 creators
- Consistent Creator — 50 posts in 30d · top 5%
- Top 5% in Serbia — Ranked #2 of 77 creators
Recent posts
Most codebases don't need a rewrite. They need a thousand small fixes that nobody schedules. That's the 𝗕𝗼𝘆 𝗦𝗰𝗼𝘂𝘁 𝗥𝘂𝗹𝗲: 𝗹𝗲𝗮𝘃𝗲 𝘁𝗵𝗲 𝗰𝗼𝗱𝗲 𝗯𝗲𝘁𝘁𝗲𝗿 𝘁𝗵𝗮𝗻 𝘆𝗼𝘂 𝗳𝗼𝘂𝗻𝗱 𝗶𝘁. Robert C. Martin popularized it in his book Clean Code (2008). This term comes from Scouting: leave the campsite cleaner than you found it. How does this look in practice: You open an old module to add a feature, but inside you find a processData() method that has more than 200 lines, and some blocks of commented-out code. You could add your feature and leave it. The rule says 𝗶𝗺𝗽𝗿𝗼𝘃
84 reactions · 16 comments · 0 reposts
𝗪𝗵𝘆 𝗮𝗿𝗲 𝘄𝗲 𝘄𝗿𝗶𝘁𝗶𝗻𝗴 𝗯𝗮𝗱 𝗰𝗼𝗱𝗲? You may have seen some bad code in your work. We saw different sides of such code, and the root causes differ. It can be due to 𝘁𝗶𝗺𝗲 𝗽𝗿𝗲𝘀𝘀𝘂𝗿𝗲, 𝗹𝗮𝗰𝗸 𝗼𝗳 𝘀𝘁𝗮𝗻𝗱𝗮𝗿𝗱𝘀, 𝗿𝗶𝘀𝗶𝗻𝗴 𝘁𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗱𝗲𝗯𝘁, 𝗼𝗿 𝗲𝘃𝗲𝗻 𝗸𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝗴𝗮𝗽𝘀. The consequences of writing such code are bad code organization, reduced team morale, and increased technical debt. What is bad code? 🔹 𝗡𝗼𝘁 𝗲𝗮𝘀𝘆 𝘁𝗼 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱 𝗮𝗻𝗱 𝗰𝗼𝗻𝗳𝘂𝘀𝗶𝗻𝗴 🔹 𝗖𝗹𝗮𝘀𝘀𝗲𝘀 𝗮𝗿𝗲 𝗰𝗼𝘂𝗽𝗹𝗲𝗱 🔹 𝗡𝗼𝘁 𝗲𝗮𝘀𝘆 𝘁𝗼 𝗰�
62 reactions · 10 comments · 0 reposts
𝗘𝘃𝗲𝗿𝘆 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿 𝗹𝗲𝗮𝗿𝗻𝘀 𝘁𝗼 𝗱𝗲𝗯𝘂𝗴 𝗰𝗼𝗱𝗲, 𝗯𝘂𝘁 𝗮𝗹𝗺𝗼𝘀𝘁 𝗻𝗼 𝗼𝗻𝗲 𝗸𝗻𝗼𝘄𝘀 𝗵𝗼𝘄 𝘁𝗼 𝗱𝗲𝗯𝘂𝗴 𝘁𝗵𝗲𝗺𝘀𝗲𝗹𝘃𝗲𝘀 There is one trait every superintelligent person has: metacognition. It's just noticing your own thinking as it happens. You catch the thought instead of getting carried off by it. The time flows, and you just go with it. Sometimes, you get defensive in a code review before the comment has even landed. Sometimes you're three hours into a bug, and something in you refuses to walk away from it. Someone floats an idea in a meeting, and you've
71 reactions · 3 comments · 0 reposts