Chief Roadblock Remover and Learning Enabler | Software Development Expert | Leadership & Career Coach | Speaker | Author | Building great products, building great teams!

🎯 I'm a result-driven 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗟𝗲𝗮𝗱𝗲𝗿, 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁 𝗘𝘅𝗽𝗲𝗿𝘁, 𝗖𝗼𝗮𝗰𝗵, 𝗧𝗿𝗮𝗶𝗻𝗲𝗿 𝗮𝗻𝗱 𝗖𝗼𝗻𝘀𝘂𝗹𝘁𝗮𝗻𝘁 with 20 years of professional experience in different domains, including the 𝗳𝗶𝗻𝗮𝗻𝗰𝗲 𝗶𝗻𝗱𝘂𝘀𝘁𝗿𝘆, 𝗯𝗮𝗻𝗸𝗶𝗻𝗴, 𝗲𝗻𝗲𝗿𝗴𝘆 𝘀𝗲𝗰𝘁𝗼𝗿, 𝘁𝗿𝗮𝗻𝘀𝗽𝗼𝗿𝘁𝗮𝘁𝗶𝗼𝗻, 𝗶𝗻𝘀𝘂𝗿𝗮𝗻𝗰𝗲 𝗮𝗻𝗱 𝘁𝗲𝗹𝗰𝗼. 

🚀 My mission is to provide 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗲𝘅𝗰𝗲𝗹𝗹𝗲𝗻𝗰𝗲 focused on architecture, the best agile practices, passionately 𝗯𝘂𝗶𝗹𝗱 𝗵𝗶𝗴𝗵-𝗽𝗲𝗿𝗳𝗼𝗿𝗺𝗶𝗻𝗴 𝘁𝗲𝗮𝗺𝘀 𝗮𝗻𝗱 𝗼𝗿𝗴𝗮𝗻𝗶𝘇𝗮𝘁𝗶𝗼𝗻𝘀 to deliver innovative, 𝗵𝗶𝗴𝗵-𝗾𝘂𝗮𝗹𝗶𝘁𝘆 𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝘀, working closely with customers and developing software products on different platforms.

🎓 As a 𝗿𝗲𝘀𝗲𝗮𝗿𝗰𝗵𝗲𝗿, I published 20+ papers and book chapters in international conferences and journals (having more than 440+ citations and h-index 11 on Google Scholar), obtaining 𝗣𝗵.𝗗. 𝗶𝗻 𝗖𝗼𝗺𝗽𝘂𝘁𝗲𝗿 𝗦𝗰𝗶𝗲𝗻𝗰𝗲𝘀. Also, I have been involved as a 𝗿𝗲𝘃𝗶𝗲𝘄𝗲𝗿 𝗮𝗻𝗱 𝗽𝗿𝗼𝗴𝗿𝗮𝗺 𝗰𝗼𝗺𝗺𝗶𝘁𝘁𝗲𝗲 𝗺𝗲𝗺𝗯𝗲𝗿—member of ACM, the IEEE Computer Society, and GOAI Research group. 

🧑‍💼 I work as a professional 𝗛𝗶𝗴𝗵-𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝗮𝗻𝗱 𝗖𝗮𝗿𝗲𝗲𝗿 𝗰𝗼𝗮𝗰𝗵 for people in engineering leadership positions.

✍🏻 Additionally, I am a 𝗽𝗮𝘀𝘀𝗶𝗼𝗻𝗮𝘁𝗲 𝗮𝘂𝘁𝗵𝗼𝗿, who helps more than 400,000 engineers, managers, and architects to build great careers, products, and teams through various platforms and channels.

𝗘𝘅𝗽𝗲𝗿𝘁𝗶𝘀𝗲:

📌 Leadership
📌 Team building
📌 Making things efficient
📌 Creating self-contained systems
📌 Be highly organized and make others too
📌 Focus on strategy/goals
📌 Make things happen
📌 Career Coaching
📌 Mentoring
📌 Line management
📌 Effective client communication
📌 Software Architecture
📌 DevOps mindset
📌 Cloud (Azure)
📌 .NET/C# (ASP.NET/WPF)
📌 SQL Server/NoSQL
📌 Agile methods (Scrum, Kanban, SAFe)
📌 Product/project management

📲 Feel free to contact me here via LinkedIn (DM)!

Dr Milan Milanović

Developers don't like legacy projects

But, in software, legacy means it makes money

'Greenfield' means 'no revenue' (yet)

Legacy code is messy because it has survived user contact

Greenfield is clean because nobody's tried to break it

The code you hate is funding your salary

The code you want to write isn't

Chief Roadblock Remover and Learning Enabler | Helping 400K+ engineers and leaders grow through better software, teams & careers | Author | Speaker | Leadership & Career Coach

The best engineers I know delete more code than they write

Junior engineers add features. Senior engineers remove complexity

Every line of code you write is a liability. It needs to be maintained. It can break. It adds cognitive load to anyone who reads it later

The best pull requests I've seen in the last year? Half of them deleted more than they added. Someone refactored three classes into one. Someone replaced 200 lines of custom logic with a library function. Someone removed an entire abstraction layer that wasn't pulling its weight

Deletion is a skill. You have to know what's safe to remove. You have to understand the system well enough to see what's redundant, over-engineered, or just wrong

Next time you open a file, ask: What can I remove?

The best code is the code you don't write

𝗗𝗼 𝗻𝗼𝘁 𝗹𝗲𝘁 𝗽𝗲𝗼𝗽𝗹𝗲 𝘁𝗵𝗶𝗻𝗸 𝘆𝗼𝘂 𝗱𝗼𝗻’𝘁 𝗯𝗲𝗹𝗼𝗻𝗴

As former President Obama said in the podcast, when you sit with people at fancy places (Harvard, US Senate, etc.) with people with fancy titles and talk to them, you will learn one thing...

They are nothing special; they are just a normal person like you.

They just have confidence that they belong to something.

Give that confidence to yourself and sit at that table.

And when you get a seat at the table, make room for someone else who has never had a seat.

I wish you a great week ahead 👋!

Video: Pivot Podcast.

#management #personaldevelopment #success #career #leadership

If you're a developer who ships code daily, remember these:

- First, make it work; nobody cares how elegant broken code is
- Then make it fast, slow code that works still frustrates users
- After that, make it pretty, so that your teammates read code more than they write it
- Add tests that actually catch bugs, not just boost coverage metrics
- Refactor when you finally understand what you're building (usually the second time through)

Perfect code on the first try is a myth. 

Fast iteration beats slow perfection every time

If you're a senior software engineer, here is an incomplete list of engineering practices you must know:

- Source control / GIT
- Tests (check Test Pyramid)
- Clean code
- Pair / Mob programming
- Design Patterns
- Refactoring
- TDD / BDD
- YAGNI, DRY, KISS, SOLID
- Automatic code analysis
- Code reviews
- Documenting

Anything else to add?

𝗔𝗣𝗜 𝗚𝗮𝘁𝗲𝘄𝗮𝘆 𝘃𝘀 𝗟𝗼𝗮𝗱 𝗕𝗮𝗹𝗮𝗻𝗰𝗲𝗿 𝘃𝘀 𝗥𝗲𝘃𝗲𝗿𝘀𝗲 𝗣𝗿𝗼𝘅𝘆

Regarding a system design, we often need clarification about the roles of a Load Balancer and an API Gateway. Most of our resources are about their implementation rather than real-life use cases.

𝗔𝗣𝗜 𝗚𝗮𝘁𝗲𝘄𝗮𝘆 

It sits between a client and a group of backend services. It serves as a reverse proxy, accepting all application programming interface (API) calls, aggregating the services needed to fulfill them, and returning the appropriate results. 

User authentication, rate limits, and statistics are typical duties that API gateways handle on behalf of an API service system. Also, the API gateway can handle faults (circuit breakers), logging, and monitoring.

𝗟𝗼𝗮𝗱 𝗕𝗮𝗹𝗮𝗻𝗰𝗲𝗿 

It is a service that distributes incoming traffic across many servers or resources. Usually, we have two or more web servers on the backend, and it 𝗱𝗶𝘀𝘁𝗿𝗶𝗯𝘂𝘁𝗲𝘀 𝗻𝗲𝘁𝘄𝗼𝗿𝗸 𝘁𝗿𝗮𝗳𝗳𝗶𝗰 𝗯𝗲𝘁𝘄𝗲𝗲𝗻 𝘁𝗵𝗲𝗺. 

Its primary purpose is to use resources optimally. A more equal task allocation and increased capacity can enhance the system's responsiveness and reliability. 

There are three load balancers at a high level: hardware-based, cloud-based, and software-based.

𝗥𝗲𝘃𝗲𝗿𝘀𝗲 𝗣𝗿𝗼𝘅𝘆 

A server sits in front of backend servers and forwards client requests to them. Reverse proxies are typically used to enhance security, performance, and reliability. 

A reverse proxy receives a request from a client, forwards it to another server, and returns the response to the client, giving the impression that the first proxy server handled the request. These proxies ensure that users don't access the origin server directly, giving the web server anonymity. 

They are usually used for Load balancing, where we need to handle incoming traffic and distribute it across multiple backend servers, or for caching.

So, the main thing that differs these two is that an 𝗔𝗣𝗜 𝗚𝗮𝘁𝗲𝘄𝗮𝘆 𝗶𝘀 𝗳𝗼𝗰𝘂𝘀𝗲𝗱 𝗼𝗻 𝗿𝗼𝘂𝘁𝗶𝗻𝗴 𝗿𝗲𝗾𝘂𝗲𝘀𝘁𝘀 to the appropriate service and it handles requests for APIs, while a 𝗟𝗼𝗮𝗱 𝗯𝗮𝗹𝗮𝗻𝗰𝗲𝗿 𝗶𝘀 𝗳𝗼𝗰𝘂𝘀𝗲𝗱 𝗼𝗻 𝗱𝗶𝘀𝘁𝗿𝗶𝗯𝘂𝘁𝗶𝗻𝗴 𝗿𝗲𝗾𝘂𝗲𝘀𝘁𝘀 𝗲𝘃𝗲𝗻𝗹𝘆 between a group of servers and handles requests that are sent to a single IP address, which works at protocol or socket level (TCP, HTTP).

Some 𝗲𝘅𝗮𝗺𝗽𝗹𝗲𝘀 of API Gateways are Amazon API Gateway, Ocelot (.NET-based), Tyk, or Apache APISIX, while Load Balancers are Azure Load Balancer, HAProxy, or Seesaw.

An example of reverse proxy services is 𝗔𝗽𝗮𝗰𝗵𝗲 𝗣𝗿𝗼𝘅𝘆, 𝗡𝗴𝗶𝗻𝘅 𝗼𝗿 𝗜𝗜𝗦 with additional modules (Url Rewrite).

Glovo

Software Engineer

La Salle BCN

- Evaluate, design and develop solutions in several R&D&I national and EU projects ranging from e-health, industry 4.0, sustainable energy communities,  AI for mental health, and IoT (ATHIKA, Planet4, CEUIS, MENTALTIC, HTPAI).
- Mentor, co-design, solve technical problems and review (e.g., code reviews) final thesis projects of BEng and MSc students, including business solutions (e.g., Tenders SaaS, Web3 payment app). (Java, Spring, Scala, AWS, Node, React, Linux, Docker, Flutter, SQL, NoSQL)
- Lead researchers and participate in competitive EU and national grant proposals (conceptualization, time management, budget allocation).
Coordinate and lecture several International BEng web-related courses, manage lecturers and assistants, and lead and develop the upgrade of  teaching materials with new technologies (e.g., Docker, Cypress, Design Patterns, CI/CD).
- Guest Editor of scientific Journals (industry 4.0).
- Collaborate with software companies (AWS, Docker, Clean Architecture).

Software Engineer & Senior R&D Computer Engineer

Lecture and develop up-to-date materials in the Master in High Performance Web Programming (Online). Courses:
- Web Environments
- PHP
- Javascript
- Efficient Software Development
- Web Frameworks
- Final Master Thesis

Software Engineer & Lecturer of the Master of Science in High Performance Web Programming (Online)

Coordination of the Master of Science in High Performance Web Programming (Online), managing related lecturers and students.
- Coordination
- Management
- Communication
- Teamwork
- Leadership
- Planning
- Mentoring
- Teaching staff and candidate interviews

Coordinator of the Master of Science in High Performance Web Programming (Online)

- Design, develop, and test a scalable and distributed architecture for the IoT and Web of Things, focusing on energy communities (Smart Grids) using the Scala stack. The project uses Akka and organizes actors in layers (protocol-specific, core) to bridge between IoT protocols such as MQTT, WebSocket and HTTP. These actors are per device and are distributed among regions, using a distributed PubSub Cluster to communicate. MongoDb and Neo4j are used as the persistence layer. E2E/unit testing with Scala, data analysis with Python.
- Design, develop, and test a clustering algorithm and a rescheduling algorithm for the Social IoT, focusing on energy communities (Scala stack). The clustering algorithm groups prosumers by load shape compatibility, the partially distributed (two-phase) rescheduling algorithm minimizes energy consumption peaks. Unit testing with Scala, data analysis with Python.
- Mentor, co-design, solve technical problems and review (e.g., code reviews) final thesis projects of BEng and MSc students, including business solutions.
- Design and mentor research assistants in developing a Web-based IoT middleware to create web-things using the actor model and finite-state machines described using web ontologies (Scala, Java, Akka, HTTP, OWL).
- Coordinate and lecture in the Master in High Performance Web Programming, manage related lecturers and lead the creation of cohesive, up-to-date materials (Clean Code & Architecture, CI/CD, Web Frameworks).

Software Engineer & PhD Student

Professor Assistant in helping students to develop web projects

Software Engineer & Professor Assistant

Software Engineer & Research Assistant

Cobuc

Junior Software Developer (Internship)

Web & Backend · Cloud & Edge Computing | Senior R&D Software Engineer | PhD in Computer Engineering

A Software Engineer with a PhD in Computer Engineering specialised in web development, Internet of Things and R&D for over 6 years. I thrive in roles centralising innovation, creativity, and technical problem-solving with a passion for mentorship and teamwork. I can learn swiftly and autonomously as a self-described hard-working and proactive individual. My primary interests reside in software architecture, system design, automation, and deployment, forming the basis of my engineering endeavours. I specialise in web backend with strong frontend knowledge. I am a Cloud and Edge Computing group member at La Salle - URL.

taplio

The Battle

Dr Milan Milanović

Víctor Caballero

Followers

Posts

Engagements

Likes

Performance ScoreDr Milan Milanović's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Dr Milan Milanović

Víctor Caballero

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Dr Milan Milanović's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreDr Milan Milanović's LinkedIn Performance