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 #61 of 18,566 LinkedIn creators in Information Technology & Services, and is a standout voice in Serbia. They have 274.7K followers and published 51 posts in the last 60 days at a 0.1% average engagement rate.
- 274.7K followers
- 51 posts / 60d
- 0.1% avg engagement
- 1.2K 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
- Top 1% Audience — 274,720 followers
- Top 1% in Information Technology & Services — Ranked #3 of 1910 creators
- Top 1% Creator — 51 posts in 30 days
- Top 5% in Serbia — Ranked #2 of 77 creators
Recent posts
Some people learn system design Others learn the laws of human nature The second group will go much further in life
20 reactions · 2 comments · 0 reposts
𝗨𝗿𝗴𝗲𝗻𝘁 𝗶𝘀 𝗻𝗼𝘁 𝘁𝗵𝗲 𝘀𝗮𝗺𝗲 𝗮𝘀 𝗜𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁! Urgent tasks require immediate attention. Important tasks have an outcome that leads to achieving goals. What matters here is to distinguish between "urgent" and "important" tasks. To do this, you can use 𝗧𝗵𝗲 𝗘𝗶𝘀𝗲𝗻𝗵𝗼𝘄𝗲𝗿 𝗠𝗮𝘁𝗿𝗶𝘅. It is a simple decision-making tool. It helps you separate important, unimportant, and not urgent tasks. It divides tasks into four boxes. They rank which tasks you focus on first, and which you delegate or delete. When you get a task, you put it in one of 𝘁𝗵𝗲 𝗳𝗼𝘂𝗿 𝗾𝘂𝗮𝗱�
100 reactions · 7 comments · 0 reposts
𝗪𝗵𝘆 𝗶𝘀 𝗖𝗿𝗶𝘁𝗶𝗰𝗮𝗹 𝗧𝗵𝗶𝗻𝗸𝗶𝗻𝗴 𝗮 𝗚𝗮𝗺𝗲 𝗖𝗵𝗮𝗻𝗴𝗲𝗿 𝗙𝗼𝗿 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀? I was often asked whether pursuing a Ph.D. was worth it, given that I left academia for industry. The clear answer is yes, because there I learned skills that, as a developer, I wouldn't have had otherwise, such as how to write, collaborate, and think critically. By far the most important is 𝗰𝗿𝗶𝘁𝗶𝗰𝗮𝗹 𝘁𝗵𝗶𝗻𝗸𝗶𝗻𝗴. And it comes deep from my nature: "we always do it this way" is usually not a good enough explanation for me. In our industry, we always need to test the benefits and d
69 reactions · 12 comments · 16 reposts
Last updated 2026-08-01