3MD is a family owned company and a leading software provider of Transportation Management Systems (TMS), based in Chicago, US. The TMS platform includes solutions for transport companies and couriers of all sizes. The platform assists companies in planning, organizing, and billing rides.

In my role of CTO, I'm focused on following:

- Owner the technology vision and roadmap
- Laying the foundations of scaling the technical platform and scaling the teams.
- Establishing and executing technology strategy for delivering the most possible outcome for our customers.
- Growing a healthy, collaborative engineering culture in line with the company values.
- Driving engineering excellence and ensure teams are delivering high-quality results.
- Growing engineering team from 0 to 10+ exceptional talents.
- Driving collaboration with external partners.
- Delivering the flagship product according to expectations.
- Ensuring the product roadmap is well thought out and feasible for each team.
- Understanding the teams’ impediments and removing them.
- Defining clear career (progression) paths.
- Regular 1:1 meetings.
- Helping people grow and progress in their careers.
- Regular, constructive performance feedback.
- Conducting performance and salary reviews.
- Ensuring that individuals are energized and motivated by their work.
- Organizing training management.
- Solution architecture.
- Introduction of DevOps mindset.
- Implementation of .NET/Azure solutions / PoCs.
- Administration of Azure/Azure DevOps.
- Definition of QA procedures.

Projects:

- Trucking Hub platform
- Trucking Hub mobile apps
- VoIp system

Chief Technology Officer

TechWorld With Milan

I help more than 150.000 engineers, managers and architects to build great careers, products and teams.

Writing on the following platforms: 

- https://newsletter.techworld-with-milan.com/.
- https://milan.milanovic.org/#posts. 
- https://dzone.com/users/3859449/milanm.html.
- https://www.linkedin.com/in/milanmilanovic/recent-activity/shares/.
- https://twitter.com/milan_milanovic.

Author

Zühlke Group

Worked with different clients, from small startups, over large international companies to FAANG companies.

Accomplishments:

- Completed responsibilities as a thought leader with expertise in Software and solution architecture, .NET, Azure and Cloud.
- Acquired a thorough understanding of the ecosystems and fundamental guiding principles of software development.
- Supported the Zühlke Community and promoted a productive workplace where team members inspire one another. shared use cases frequently, ran technical trainings, and generated training materials to support ongoing professional development.
- Increased social media traffic and digital exposure by attending conferences, writing articles for LinkedIn, Blog and different magazines and portals.
- Offered customized mentoring for team members, sharing important industry insights to produce deeper comprehension and to considerably increase overall skill efficiency while taking on projects.

Worked on customer projects as a Software/Solution Architect and team lead in distributed teams with Switzerland, Germany, Austria, UK and Singapore. My responsibilities include:

- Creating the IT architectures for cutting-edge, ground-breaking software solutions and giving all clients in the domain high-level strategic advice.
- Cloud architecture (Azure).
- DevOps.
- Requirements engineering.
- Code reviews.
- Different roles in internal organization.
- Coaching less experienced colleagues / mentoring.
- Conducting technical interviews.

Customer projects:

- Advanced speech recognition engine (enterprise): Speech to text recognition engine in the Cloud. Tech stack: SAFe, .NET, Azure, Azure DevOps, WCF, SQL Server.

Principal Consultant

Accomplishments:

- Led a local Cloud topic group (CoP) for Serbia, Bulgaria and Portugal with 150+ people, making 20+ people certified for Azure and AWS, setting it from the ground up, as well as group-wide Azure and AWS teams with 170+ people.

- Led group-wide Azure and AWS teams (CoP) for UK, Germany, Switzerland, Austria, Portugal, Bulgaria, Serbia, and Singapore with 170+ people, enabling regular meetings and knowledge exchange.

My responsibilities included:
- Defining group mission and goals.
- Defining collaboration and communication channels.
- Organizing topic group events and internal organization.
- Sharing knowledge internally and externally.
- Defining tools to be used for communication and knowledge sharing.
- Engaging in regular communication with team members and others.
- Driving Cloud topic towards capability.
- Maintaining relations with other Cloud capabilities on the group level.
- Job profiles definition with HR.
- Searching for right people.
- Conducting technical interviews.

Regional Cloud Capability Lead

Accomplishments:

- Recieved overall score of 3.6/4 from peers.
- Got overall good feedbacks.

People management:
- Helping people grow and progress in their careers;
- Regular 1:1 meetings;
- Coaching and mentoring;
- Performance appraisal and feedback;
- Regular, constructive performance feedback
- Evaluations, defining goals, OKR's & SMART Objectives;
- Mediation and conflict resolution;
- Defining job profiles;

Team Lead / Engineering Manager

Accomplishments:
- Lead a team of developers from Belgrade side in a distributed setup with Switzerland colleagues.
- Enabled successful project distribution for a major client.
- Led Thought Leadership initiative for ZRS.
- Given multiple talks/workshops on different topics (architecture, cloud, testing, clean code, mentoring, goals, etc.).

Worked on customer projects as part of a distributed .NET DEV team with Switzerland and Singaporean colleagues. My responsibilities included:
- Team architect.
- Team lead (Beg).
- Requirement engineering.
- Code reviews.
- Coaching / mentoring.
- Software/solution architecture, design, testing and implementation.
- Conducting technical interviews.

Customer projects:
- Integrated investment advisory platform for relationship managers of a private bank. Tech stack: Javascript/TypeScript, C#/.NET, SQL Server, Entity Framework, Stored procedures, AngularX, RxJS, ngrx, Log4net, Jobbr. The biggest account and project in Zuhlke Group: 50+ people, 1mil+ LOC.

Lead Software Architect

Worked on customer projects as part of a distributed .NET DEV team with Switzerland and Singaporean colleagues. My responsibilities included:
- Software architecture, design, testing and implementation.
- Preparing bids for projects from technical side.
- Conducting technical interviews.

Customer projects:
- Insurance Portal for Corporate Customers. Tech stack: C#, ASP.NET MVC/Core/Web-API, Entity Framework, IdentityServer3, SQL Server Integration Services, RavenDB, Kendo UI, TypeScript, LESS, TFS. (november 2017.-june 2018.). 600k+ LOC.
- GUI for Media Processing System. Tech stack: WPF, MVVM, C#, Feature Based, FluentAPI, MVVMLight, ReFit, Aspose, SourceAFIS. (june 2018.-september 2018.)

Expert Software Engineer

First Principles Consultancy

I operated as an independent software development expert, software architect, mentor, trainer, programmer, speaker, and writer. As I have done in previous roles I’m assisting my international clients to modernize their software development. I am at my best working with projects and teams that need a boost, in collaboration, performance and in technology. Some examples of my work include:

- As an agile coach I turn-around organizations from traditional ways of working to Agile, Scrum, Kanban, and continuous delivery. 
- As a career coach, I guide engineers, engineering managers, tech leads, etc.
- As a Fractional CTO I implement new technologies in organizations, such as software architectures, modern modeling tooling, RESTful services, APIs, C#/.NET, functional programming, Cloud technologies, such as Azure and Azure DevOps.
- As an architecture coach I help organizations restructure unmaintainable legacy code base to new flexible and tested software architectures.
- As a software architect I create front-end and back-end frameworks and code, using technologies such as HTML5/CCS3, Bootstrap, Angular, C#, .NET, ASP.NET MVC, Xamarin, WPF.
- As a mentor and teacher I present seminars and (in-house) training courses on a variety of topics such as  Agile, Scrum, Kanban, Software Development, Software Architecture, Microservices, Continuous Delivery, Design Patterns, Domain-Driven Design, Modeling and UML, Clean Code, .NET and Testing.

Independent Consultant, Owner

Electric Power Industry of Serbia

Accomplishments:

I led an organization of 40+ people that worked on the development of different software solutions by using Microsoft and Java-based, as well as some legacy tech stack. Some of applications we implemented are:

• Vehicle maintenance management system (Web - 100+ users).
• Procurement solution, which includes elements of the plan to implementation of procurement, contracts, etc. (Web - 500+ users).
• Project management team member for SAP ERP implementation, acting as internal audit (june 2014.  - december 2015.).
• Oracle UCM - document management system (support lead).

I was responsible for:
• Leading main software implementation projects.
• People management of 40+ people.
• Helping people grow and progress in their careers 
• Regular, constructive performance feedback
• Harmonising engineering processes, driving consistent standards and approaches throughout the team.
• Product development.
• Keeping the team up to date with the latest software development technologies and methodologies.
• Coaching the team on agile software development best practices. 
• Developing short and long term strategy for the team to meet the company’s goals and objectives. Planning and monitoring the successful implementation of this strategy.
• Teaching and training software developers, organizing courses, etc.
• Overseeing internal product development.
• Supervising other software projects.
• Defining implementation times and deadlines (for development and support).
• Leading technical support.
• Defining new internal organizational structure.
• Internal staff recruiting.
• Planning and tracking procurements for a department.
• Management of the commission for the inventory of concessions, intellectual property and software in company.
• Administration and configuration of SQL Server 2008/2014 (backup, migrations, maintenance), Team Foundation Server and Application Server (IIS).
• Management of company internal portal and web site.

Head of Engineering

Software architect and a team leader for software engineers developing ERP-based applications using .NET stack and also:
• Built a team of developers and business analysts from 0 to 10+ people.
• Defined standards, tools and processes that were used for solution development within company.
• Line management.
• Teaching and training software developers, organizing courses, etc.
• Design of the solutions architecture.
• Framework design.
• Product development management.
• Defining new internal organizational structure.
• Internal staff recruiting.
• Scrum Master.

Implemented projects by using .NET technology stack: 
• Materials management (Web - 400+ users)
• Asset management (Web - 300+ users)
• Invoicing (Web - 10+ users)

Head of Technical Software Development Department

Senior software engineer and a team leader for following implemented projects (.NET stack):
• Storehouse calculation distributed application (Desktop), architecture and implementation (ASP.NET + C# + TFS + MS SQL Server).
• SQL Server Integration Services-based data migration from legacy system.
•  Administration and configuration of SQL Server 2008 (backup, migrations, maintenance), Team Foundation Server and IIS.
• Creation of procedures for data backup, programming style, user requirements form, etc.

Senior Software Engineer and Team Leader

Software developer for following projects (Java stack):
• Invoicing (Eclipse + EJB3 + Hibernate + Spring framework + Acegi Security + Struts 2 + JUnit 4 + JMock + JFreeChart + JasperReports + SVN + JIRA + Patterns).
• ArchiDoc Web Document Management System (Netbeans + EJB2 + Struts + JSP + JUnit 3 + Patterns).
• Other projects ( CMS for Web portal & CD presentation, E-commerce Web site implementation in PHP/MySQL,...) .
 • Teaching and training software developers, organizing courses, etc. Held Java course for 40 software developers (Basic, Advanced, Web, J2EE). Duration: one year.
 • Consultant for various Java projects.

Software Developer Consultant

GOOD OLD AI Research Network

- Worked as a researcher during post-graduate studies in the area of Modeling and metamodeling, Model transformations, Rule languages and Business models. 

- Published 20+ papers in international conferences and journals, received awards for best papers. 

- Involved in international conferences and journals as a editorial board member, program chair, reviewer and program committee member. 

- Cited 430+ times.

- Google Scholar h-index: 10.

- Member of ACM, the IEEE Computer Society and GOAI Research group.

Researcher

Abell Soft

Implemented projects:
• E-Store application for on-line selling of books in PHP/MySQL. 
 • Complete code and design of a business packages FinanceBusiness for small and medium companies in Microsoft Visual C++, using MFC, Win32, PHP and MS Access (DAO, ODBC). 
 • Coded, designed and managed multiple web sites using HTML, JavaScript, PHP, MySQL, visual editors like Macromedia Dreamweaver and Microsoft FrontPage so as other graphical tools. 
 • Active IT System consulting for large number of companies.

Junior Software Developer

Municipality of Lajkovac

System Administrator

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

🚀 My mission is in providing 𝘁𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝗶𝗰𝗮𝗹 𝗲𝘅𝗰𝗲𝗹𝗹𝗲𝗻𝗰𝗲 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 400+ citations and h-index 10 on Google Scholar), obtaining 𝗣𝗵.𝗗. 𝗶𝗻 𝗖𝗼𝗺𝗽𝘂𝘁𝗲𝗿 𝗦𝗰𝗶𝗲𝗻𝗰𝗲𝘀. Also, I have been involved as a 𝗿𝗲𝘃𝗶𝗲𝘄𝗲𝗿 𝗮𝗻𝗱 𝗽𝗿𝗼𝗴𝗿𝗮𝗺 𝗰𝗼𝗺𝗺𝗶𝘁𝘁𝗲𝗲 𝗺𝗲𝗺𝗯𝗲𝗿. Member of ACM, the IEEE Computer Society, and GOAI Research group. 

𝗘𝘅𝗽𝗲𝗿𝘁𝗶𝘀𝗲:
📌 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!

Don't worry. There will be a place for everyone.

Learn AI and use it as your leverage to improve your work.

#ai #artificialintelligence #technology #developers #work 

Dr. Milan Milanović

graphical user interface, text, application

𝗢𝘂𝗿 𝗹𝗶𝗳𝗲 𝗶𝘀 𝗻𝗼𝘁 𝗼𝗻𝗹𝘆 𝗼𝘂𝗿 𝘄𝗼𝗿𝗸

I saw much prioritization of work and only work, especially among top performers. While this sometimes led to better career paths, it was much more directed to burnout and other not-so-nice stuff. Even if you like your work very much, people are complex and social creatures that cannot only work and nothing else. A well-rounded life means improved mental and physical health, enhanced creativity, enhanced productivity, greater resilience to stress, improved relationships, and better work-life balance.

Here is my recommendation on 𝗵𝗼𝘄 𝘁𝗼 𝗰𝗿𝗲𝗮𝘁𝗲 𝘄𝗲𝗹𝗹-𝗿𝗼𝘂𝗻𝗱𝗲𝗱 𝗹𝗶𝗳𝗲:

🔹 𝗦𝗲𝘁 𝗯𝗼𝘂𝗻𝗱𝗮𝗿𝗶𝗲𝘀: Define your working hours and avoid unnecessarily taking work home or extending your workday. Clearly distinguishing between work and personal time will help you maintain a healthy work-life balance.

🔹 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗲 𝘀𝗲𝗹𝗳-𝗰𝗮𝗿𝗲: Dedicate time to caring for your physical, emotional, and mental health. Exercise regularly, eat well, get adequate sleep, and practice stress management techniques like meditation or mindfulness.

🔹 𝗖𝘂𝗹𝘁𝗶𝘃𝗮𝘁𝗲 𝗵𝗼𝗯𝗯𝗶𝗲𝘀 𝗮𝗻𝗱 𝗶𝗻𝘁𝗲𝗿𝗲𝘀𝘁𝘀: Pursue activities and interests outside of work that you're passionate about. This will help you explore different facets of your personality and provide a sense of fulfillment.

🔹 𝗕𝘂𝗶𝗹𝗱 𝗮𝗻𝗱 𝗺𝗮𝗶𝗻𝘁𝗮𝗶𝗻 𝗿𝗲𝗹𝗮𝘁𝗶𝗼𝗻𝘀𝗵𝗶𝗽𝘀: Invest time in nurturing relationships with friends, family, and significant others. Strong social connections are crucial for overall happiness and well-being.

🔹 𝗘𝗻𝗴𝗮𝗴𝗲 𝗶𝗻 𝗹𝗶𝗳𝗲𝗹𝗼𝗻𝗴 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴: Continuously seek opportunities to learn and grow, whether it's through reading, taking courses, or attending workshops. Expanding your knowledge and skills will enrich your life and enhance your personal and professional growth.

🔹 𝗣𝗹𝗮𝗻 𝘃𝗮𝗰𝗮𝘁𝗶𝗼𝗻𝘀 𝗮𝗻𝗱 𝗯𝗿𝗲𝗮𝗸𝘀: Regularly take time off work to recharge and relax. Plan vacations or staycations to explore new places, cultures, and experiences or spend quality time with loved ones.

🔹 𝗦𝗲𝘁 𝗽𝗲𝗿𝘀𝗼𝗻𝗮𝗹 𝗴𝗼𝗮𝗹𝘀: Establish short-term and long-term goals, such as health, relationships, and personal development. Then, regularly review and adjust these goals to stay motivated and focused on your overall well-being.

And remember to 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗲 𝗴𝗿𝗮𝘁𝗶𝘁𝘂𝗱𝗲. This can help you maintain a positive outlook and foster overall happiness.

👉 Take care.

#selfcare #personaldevelopment #career #techworldwithmilan #mentalhealth

Friday Developers Fun 🤣

My code is ready for production.

#developers #softwareengineering #meme #fridayhumor

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

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.

🔹 𝗔𝗣𝗜 𝗚𝗮𝘁𝗲𝘄𝗮𝘆 sits between a client and a group of backend services. It performs the function of a reverse proxy by accepting all application programming interface (API) calls, aggregating the different services needed to fulfill them, and returning the right outcome. 𝗨𝘀𝗲𝗿 𝗮𝘂𝘁𝗵𝗲𝗻𝘁𝗶𝗰𝗮𝘁𝗶𝗼𝗻, 𝗿𝗮𝘁𝗲 𝗹𝗶𝗺𝗶𝘁𝘀, 𝗮𝗻𝗱 𝘀𝘁𝗮𝘁𝗶𝘀𝘁𝗶𝗰𝘀 are typical duties that API gateways take care of on behalf of a system of API services. Also, the API gateway can handle faults (circuit breaker) but also do logging and monitoring.

🔹 𝗟𝗼𝗮𝗱 𝗕𝗮𝗹𝗮𝗻𝗰𝗲𝗿 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. As a result of an equal task allocation and the system's increased capacity, this can enhance the system's responsiveness and reliability. There are three load balancers at a high level: hardware-based, cloud-based, and software-based.

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.

_______
If you like my posts, please follow me, Dr. Milan Milanović, and hit the 🔔 on my profile to get a notification for all my new posts.

Grow with me 🚀!

#technology #softwareengineering #cloudcomputing #techworldwithmilan #api

#jobertywebinar I The new Joberty webinar is coming your way!

This time we're talking about clean code and how to make your C# code clean, and improve it day by day. You will learn what is good and what is bad code. What are code smells and how to get rid of them?

All this with Dr. Milan Milanović who has 20 years of experience in the software industry, working in various domains and several technology stacks, including web tier technologies, .NET and Java platforms, and mobile and distributed computing technologies.

REGISTER NOW!👊

View event: Joberty Webinar, Ha﻿nds on Clean Code development in C#

https://www.linkedin.com/events/jobertywebinar-ha-ndsoncleancod7068841594753314816/

𝗛𝗼𝘄 𝗹𝗼𝗻𝗴 𝗱𝗼 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝘀 𝘀𝘁𝗮𝘆 𝗮𝘁 𝗮 𝗷𝗼𝗯?

As a software developer understanding how too long to stay at one job can make a significant difference in your earning. Those who stay at one company for longer than two years end up earning 50% less over the span of their careers. Software engineers are paid a lot, but you leave money on the table if you don’t job-hop enough.

𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝘀 𝘁𝘆𝗽𝗶𝗰𝗮𝗹𝗹𝘆 𝘀𝘁𝗮𝘆 𝗮𝘁 𝗼𝗻𝗲 𝗷𝗼𝗯 𝗳𝗼𝗿 𝗮𝗻 𝗮𝘃𝗲𝗿𝗮𝗴𝗲 𝗼𝗳 𝘁𝘄𝗼 𝘆𝗲𝗮𝗿𝘀 𝗯𝗲𝗳𝗼𝗿𝗲 𝗺𝗼𝘃𝗶𝗻𝗴 𝘀𝗼𝗺𝗲𝘄𝗵𝗲𝗿𝗲 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁. 𝗧𝗵𝗲𝘆 𝘀𝗽𝗲𝗻𝗱 𝗹𝗲𝘀𝘀 𝘁𝗵𝗮𝗻 𝗵𝗮𝗹𝗳 𝘁𝗵𝗲 𝗮𝗺𝗼𝘂𝗻𝘁 𝗼𝗳 𝘁𝗶𝗺𝗲 𝗮𝘁 𝗼𝗻𝗲 𝗰𝗼𝗺𝗽𝗮𝗻𝘆 𝗰𝗼𝗺𝗽𝗮𝗿𝗲𝗱 𝘁𝗼 𝘁𝗵𝗲 𝗻𝗮𝘁𝗶𝗼𝗻𝗮𝗹 𝗮𝘃𝗲𝗿𝗮𝗴𝗲 𝘁𝗲𝗻𝘂𝗿𝗲 𝗼𝗳 𝟰.𝟮 𝘆𝗲𝗮𝗿𝘀.

It is interesting to notice if there were changes in these statistics after an extensive series of layoffs. 

Read the full text in the comments.

Credits: Developer PitStop.

#technology #softwareengineering #jobs #careers #techworldwithmilan

𝗠𝗶𝗰𝗿𝗼𝘀𝗼𝗳𝘁 𝗢𝗳𝗳𝗲𝗿𝘀 𝗙𝗿𝗲𝗲 𝗔𝗜, 𝗠𝗮𝗰𝗵𝗶𝗻𝗲 𝗟𝗲𝗮𝗿𝗻𝗶𝗻𝗴, 𝗮𝗻𝗱 𝗗𝗮𝘁𝗮 𝗦𝗰𝗶𝗲𝗻𝗰𝗲 𝗰𝗼𝘂𝗿𝘀𝗲𝘀

Recently Microsoft created a comprehensive suite of courses on these topics for beginners, which is an excellent foundation for understanding the fundamentals of these fields. In every one of these curriculums, you have more than 20 lectures to go through. 

The list of courses:

𝟭. 𝗔𝗿𝘁𝗶𝗳𝗶𝗰𝗶𝗮𝗹 𝗜𝗻𝘁𝗲𝗹𝗹𝗶𝗴𝗲𝗻𝗰𝗲 𝗳𝗼𝗿 𝗕𝗲𝗴𝗶𝗻𝗻𝗲𝗿𝘀 - https://lnkd.in/dt5QxbmX

𝟮. 𝗜𝗼𝗧 𝗳𝗼𝗿 𝗕𝗲𝗴𝗶𝗻𝗻𝗲𝗿𝘀 - https://lnkd.in/drQvkUxQ

𝟯. 𝗠𝗮𝗰𝗵𝗶𝗻𝗲 𝗟𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝗳𝗼𝗿 𝗕𝗲𝗴𝗶𝗻𝗻𝗲𝗿𝘀 - https://lnkd.in/dk_iHpjY

𝟰. 𝗗𝗮𝘁𝗮 𝗦𝗰𝗶𝗲𝗻𝗰𝗲 𝗳𝗼𝗿 𝗕𝗲𝗴𝗶𝗻𝗻𝗲𝗿𝘀 - https://lnkd.in/dfqtw4Jh

Image source: Microsoft.

_______
If you like my posts, please follow me, Dr. Milan Milanović, and hit the 🔔 on my profile to get a notification for all my new posts.

Grow with me 🚀!

#softwareengineering #ai #machinelearnig #iot #data

𝗔𝗹𝗹 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗘𝘀𝘁𝗶𝗺𝗮𝘁𝗶𝗼𝗻𝘀 𝗔𝗿𝗲 𝗪𝗿𝗼𝗻𝗴, 𝗕𝘂𝘁 𝗡𝗼𝗻𝗲 𝗔𝗿𝗲 𝗨𝘀𝗲𝗳𝘂𝗹

If you're working in a team using the Scrum framework, you use story points to estimate effort on your stories, tasks, etc. Yet, probably you're often mistaken with estimations. The main reason for this is that estimations are 𝗮 𝗳𝗼𝗿𝗲𝗰𝗮𝘀𝘁, and a forecast predicts an unknown future. Yet we all know it is impossible to see the end, but they tend to forget it and make commitments from estimations. 

In general, it is 𝗴𝗼𝗼𝗱 𝘁𝗼 𝗵𝗮𝘃𝗲 𝗽𝗹𝗮𝗻𝘀 because it's how we can iteratively work on something, continuously providing value to our clients. Yet, projects are usually very complex, involving many teams and dependencies between them. 

𝗪𝗵𝘆 𝗱𝗼 𝗽𝗹𝗮𝗻𝘀 𝗳𝗮𝗶𝗹? There are many reasons for that, such as not precise requirements, level of knowledge not being considered, etc.

Yet, there are some other things 𝘄𝗵𝘆 𝗲𝘀𝘁𝗶𝗺𝗮𝘁𝗶𝗼𝗻𝘀 𝗳𝗮𝗶𝗹:

𝟭. 𝗛𝗼𝗳𝘀𝘁𝗮𝗱𝘁𝗲𝗿’𝘀 𝗟𝗮𝘄: States that, "It always takes longer than you expect, even when you take into account Hofstadter's Law." It highlights the recursive nature of estimation, where considering the complexity of a task and human optimism often leads to underestimation.

𝟮. 𝗕𝗿𝗼𝗼𝗸'𝘀 𝗟𝗮𝘄: "Adding manpower to a late software project makes it later." This law emphasizes the negative impact of increasing team size to speed up a project. New team members need time to get up to speed, and overhead communication increases, further delaying the project.

𝟯. 𝗣𝗹𝗮𝗻𝗻𝗶𝗻𝗴 𝗙𝗮𝗹𝗹𝗮𝗰𝘆: This cognitive bias causes people to underestimate the time and resources required to complete a task. In software estimation, developers may need to pay more attention to potential obstacles or be optimistic about their abilities, leading to inaccurate estimates.

𝟰. 𝗕𝗶𝗸𝗲𝘀𝗵𝗲𝗱𝗱𝗶𝗻𝗴: This law states that people tend to focus on trivial details rather than critical aspects of a project. In software estimation, this can result in an overemphasis on understandable tasks while underestimating more complex tasks.

𝟱. 𝗣𝗮𝗿𝗸𝗶𝗻𝘀𝗼𝗻'𝘀 𝗟𝗮𝘄: "Work expands to fill the time available for its completion." This law suggests that if a deadline is too generous, developers may spend more time on a task than necessary, leading to inefficiencies and delays.

𝟲. 𝗡𝗶𝗻𝗲𝘁𝘆-𝗡𝗶𝗻𝗲𝘁𝘆 𝗥𝘂𝗹𝗲: "The first 90% of the code accounts for the first 90% of the development time; the remaining 10% of the code accounts for the other 90% of the development time." This rule highlights the difficulty of accurately estimating the time needed for bug fixing, optimization, and polishing.

Break down tasks by 𝗱𝗲𝗰𝗼𝗺𝗽𝗼𝘀𝗶𝗻𝗴 𝗹𝗮𝗿𝗴𝗲 𝗰𝗼𝗺𝗽𝗹𝗲𝘅 𝘁𝗮𝘀𝗸𝘀 into smaller, more manageable ones. For example, we found that jobs estimated up to 3 days of work are accurate.

#technology #softwareengineering #programming #techworldwithmilan #agile

Friday Developers Fun 🤣

Be aware what you ask.

#developers #softwareengineering #meme #fridayhumor

𝗪𝗵𝗮𝘁 𝗶𝘀 𝗥𝗲𝘃𝗲𝗿𝘀𝗲 𝗣𝗿𝗼𝘅𝘆?

Proxy servers act as a user's interface to a web server. As you may already know, many proxies are used for various tasks. There are, in general, two types of proxies: Forward and Reverse.

📌 𝗙𝗼𝗿𝘄𝗮𝗿𝗱 𝗽𝗿𝗼𝘅𝘆 sits in front of a user and acts as a mediator between users and the web servers they access. It indicates that the user's request passes via the forward proxy before it is forwarded to the website. After being retrieved from the internet, the data is forwarded to the proxy server, which then sends it back to the original requester. The request is made by the proxy server, not the user, in the eyes of the internet server. A forward proxy can also store data and utilize it to handle incoming requests in the future. They are used for accessing restricted geo-locations or ensuring anonymity.

📌 𝗥𝗲𝘃𝗲𝗿𝘀𝗲 𝗣𝗿𝗼𝘅𝘆 server resides in front of backend servers and transfers client requests to these servers. Reverse proxies are typically used to increase security, speed, and dependability. A reverse proxy receives a request from a client, forwards it to another server, and then returns it to the client, giving the impression that the first proxy server handled the request. In addition, 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 deal with incoming traffic flow so that we may distribute that traffic between multiple backend servers, or we can use them for caching too.

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

_______
If you like my posts, please follow me, Dr. Milan Milanović, and hit the 🔔 on my profile to get a notification for all my new posts.

Grow with me 🚀!

#technology #softwareengineering #programming #techworldwithmilan #api

𝗪𝗵𝘆 𝘀𝗵𝗼𝘂𝗹𝗱 𝘆𝗼𝘂 𝗯𝘂𝗶𝗹𝗱 𝗮 (𝗺𝗼𝗱𝘂𝗹𝗮𝗿) 𝗺𝗼𝗻𝗼𝗹𝗶𝘁𝗵 𝗳𝗶𝗿𝘀𝘁?

I've just released the new issue of my 𝗻𝗲𝘄𝘀𝗹𝗲𝘁𝘁𝗲𝗿 talking about why you should build a modular monolith first and not go with a microservices approach to more than 8.000 addresses.

In this issue, we talk about:

🔹 𝗪𝗵𝗮𝘁 𝗮𝗿𝗲 𝗠𝗼𝗱𝘂𝗹𝗮𝗿 𝗠𝗼𝗻𝗼𝗹𝗶𝘁𝗵𝘀?

🔹 𝗪𝗵𝗮𝘁 𝗮𝗿𝗲 𝘀𝗼𝗺𝗲 𝗮𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲𝘀/𝗱𝗶𝘀𝗮𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲𝘀 𝗿𝗲𝗴𝗮𝗿𝗱𝗶𝗻𝗴 𝗠𝗶𝗰𝗿𝗼𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀

🔹 𝗪𝗵𝗮𝘁 𝗸𝗶𝗻𝗱 𝗼𝗳 𝗺𝗼𝗻𝗼𝗹𝗶𝘁𝗵𝘀 𝗱𝗼 𝘄𝗲 𝗵𝗮𝘃𝗲?

🔹 𝗛𝗼𝘄 𝘁𝗼 𝗱𝗲𝗰𝗼𝗺𝗽𝗼𝘀𝗲 𝗺𝗼𝗻𝗼𝗹𝗶𝘁𝗵𝘀

Check it from the link: 
https://lnkd.in/dwPRaD5d.

#technology #softwareengineering #microservices #techworldwithmilan #softwarearchitecture

Do you use any AI coding tools in your daily work as a developer?

Write in the comments what your experiences are. What areas have you seen the most productivity gains? What are areas where this tool is not that helpful?

#technology #softwareengineering #programming #ai #artificialintellingence

𝗧𝗵𝗲 𝗧𝗲𝘀𝘁𝗶𝗻𝗴 𝗣𝘆𝗿𝗮𝗺𝗶𝗱

We all want our software to have no known or unknown defects. Some defects can be reduced when we have a built-in quality in our software development process. One of the most essential parts of a high-quality process is tests. They allow us to go faster and safer during our development process and provide critical feedback when we do something wrong.

Mike Cohn published a book in 2010. called "𝗦𝘂𝗰𝗰𝗲𝗲𝗱𝗶𝗻𝗴 𝘄𝗶𝘁𝗵 𝗔𝗴𝗶𝗹𝗲," in which he presented the concept of "The Test Pyramid." It is a concept that helps developers and testers rank different types of tests to create a balanced, efficient, and effective testing strategy. 𝗧𝗵𝗲 𝗽𝘆𝗿𝗮𝗺𝗶𝗱 𝗶𝗹𝗹𝘂𝘀𝘁𝗿𝗮𝘁𝗲𝘀 𝘁𝗵𝗲 𝗶𝗱𝗲𝗮𝗹 𝗱𝗶𝘀𝘁𝗿𝗶𝗯𝘂𝘁𝗶𝗼𝗻 𝗼𝗳 𝘁𝗲𝘀𝘁 𝘁𝘆𝗽𝗲𝘀, with the base representing the largest tests and the top representing the smallest number.

The Testing Pyramid has 𝘁𝗵𝗿𝗲𝗲 𝗺𝗮𝗶𝗻 𝗹𝗲𝘃𝗲𝗹𝘀:

𝟭. 𝗨𝗻𝗶𝘁 𝘁𝗲𝘀𝘁𝘀 (bottom level): These tests focus on individual components or functions of the software. They are small, quick to execute, and usually written by developers. Unit tests should comprise the largest part of the test suite, as they are the most granular and help catch issues early in development.

𝟮. 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻 𝘁𝗲𝘀𝘁𝘀 (middle level): These tests check the interaction between many components or subsystems within the software. Integration tests are more complex than unit tests, as they confirm that different parts of the system work together. They take longer to execute and must be more effort to maintain but they are essential for ensuring that the system functions as a whole.

𝟯. 𝗘𝗻𝗱-𝘁𝗼-𝗲𝗻𝗱 (𝗘𝟮𝗘) 𝘁𝗲𝘀𝘁𝘀 or System tests (top-level): These tests confirm the entire system, including the user interface, APIs, and external dependencies. E2E tests simulate real-world user scenarios and ensure that the system behaves as expected from the user's perspective. These tests are the most complex, time-consuming, and expensive to maintain, so they should be used sparingly.

There are also other different 𝘃𝗮𝗿𝗶𝗮𝘁𝗶𝗼𝗻𝘀 of this pyramid:

🔹 𝗜𝗰𝗲 𝗰𝗿𝗲𝗮𝗺 𝗰𝗼𝗻𝗲 𝗺𝗼𝗱𝗲𝗹: This anti-pattern inverts the testing pyramid, with many E2E tests, fewer integration tests, and even fewer unit tests. This approach is problematic because it leads to slow and brittle test suites that are difficult to maintain.

🔹 𝗗𝗶𝗮𝗺𝗼𝗻𝗱 𝗺𝗼𝗱𝗲𝗹: This model adds an extra layer for component or contract tests between the integration and E2E tests. These tests validate the contracts or interfaces between external services and the application, ensuring they adhere to the agreed-upon specifications.

🔹 𝗛𝗼𝗻𝗲𝘆𝗰𝗼𝗺𝗯: This model focuses on risk-based testing, where the number of tests in each layer depends on the application's risk profile.

#technology #softwareengineering #programming #techworldwithmilan #testing

𝗛𝗼𝘄 𝘁𝗼 𝗙𝗶𝗴𝗵𝘁 𝗜𝗺𝗽𝗼𝘀𝘁𝗼𝗿 𝗦𝘆𝗻𝗱𝗿𝗼𝗺𝗲?

I've just released the new issue of my 𝗻𝗲𝘄𝘀𝗹𝗲𝘁𝘁𝗲𝗿 talking about 𝗱𝗲𝗮𝗹𝗶𝗻𝗴 𝘄𝗶𝘁𝗵 𝗜𝗺𝗽𝗼𝘀𝘁𝗼𝗿 𝗦𝘆𝗻𝗱𝗿𝗼𝗺𝗲 to more than 9.000 addresses.

Here we talk about:

🔹𝗧𝗵𝗲 𝗜𝗺𝗽𝗼𝘀𝘁𝗼𝗿 𝗦𝘆𝗻𝗱𝗿𝗼𝗺𝗲

🔹𝗧𝗵𝗲 𝗼𝗽𝗽𝗼𝘀𝗶𝘁𝗲: 𝗧𝗵𝗲 𝗗𝘂𝗻𝗻𝗶𝗻𝗴-𝗞𝗿𝘂𝗴𝗲𝗿 𝗘𝗳𝗳𝗲𝗰𝘁

🔹𝗧𝗵𝗲 𝗠𝗼𝗿𝗲 𝗬𝗼𝘂 𝗞𝗻𝗼𝘄, 𝗧𝗵𝗲 𝗠𝗼𝗿𝗲 𝗬𝗼𝘂 𝗥𝗲𝗮𝗹𝗶𝘇𝗲 𝗬𝗼𝘂 𝗗𝗼𝗻’𝘁 𝗞𝗻𝗼𝘄

🔹𝗛𝗼𝘄 𝘁𝗼 𝗗𝗲𝗮𝗹 𝗪𝗶𝘁𝗵 𝗧𝗵𝗲 𝗜𝗺𝗽𝗼𝘀𝘁𝗼𝗿 𝗦𝘆𝗻𝗱𝗿𝗼𝗺𝗲 𝗮𝗻𝗱 𝗧𝗵𝗲 𝗗𝘂𝗻𝗻𝗶𝗻𝗴-𝗞𝗿𝘂𝗴𝗲𝗿 𝗘𝗳𝗳𝗲𝗰𝘁

Check it out from the following link: https://lnkd.in/ds5HdfWn.

#technology #softwareengineering #career #techworldwithmilan #learning

Friday Developers Fun 🤣

Someone mentioned AI?

#developers #softwareengineering #meme #fridayhumor

𝗦𝘁𝗮𝗴𝗲𝘀 𝗧𝗵𝗮𝘁 𝗧𝗲𝗮𝗺𝘀 𝗚𝗼 𝗧𝗵𝗿𝗼𝘂𝗴𝗵 𝗙𝗿𝗼𝗺 𝗙𝗼𝗿𝗺𝗮𝘁𝗶𝗼𝗻 𝗧𝗼 𝗚𝗿𝗲𝗮𝘁 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲

According to Bruce Tuckman's concept, published in 1965, a team must go through four phases to develop and grow. Tuckman's five stages of team development is a widely recognized model in organizational psychology. The model describes the typical stages that a team goes through as it develops and matures over time. The stages are:

𝟭. 𝗙𝗼𝗿𝗺𝗶𝗻𝗴 - 𝗖𝗼𝗺𝗶𝗻𝗴 𝗧𝗼𝗴𝗲𝘁𝗵𝗲𝗿: This is the initial stage where team members come together and get to know each other. Next, they may need clarification about their roles, the objectives of the team, and the norms of behavior. In this stage, the team leader is critical in providing direction, clarifying goals, and establishing standards.

𝟮. 𝗦𝘁𝗼𝗿𝗺𝗶𝗻𝗴 - 𝗘𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗶𝗻𝗴 𝗖𝗼𝗻𝗳𝗹𝗶𝗰𝘁: In this stage, team members may experience conflicts as they have different ideas, opinions, and approaches to the work. These conflicts can be constructive if managed well by the team leader, leading to better outcomes. Effective dispute resolution, mutual respect, and open communication are essential to overcome these obstacles and promote a positive work atmosphere.

𝟯. 𝗡𝗼𝗿𝗺𝗶𝗻𝗴 - 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴 𝗵𝗼𝘄 𝘁𝗼 𝗺𝗮𝗸𝗲 𝗶𝘁 𝘄𝗼𝗿𝗸: In this stage, the team begins to resolve conflicts and establish explicit norms of behavior, roles, and responsibilities. This leads to greater cohesion, trust, and cooperation among team members. The leader should be asking questions rather than directing.

𝟰. 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗶𝗻𝗴 - 𝗪𝗼𝗿𝗸𝗶𝗻𝗴 𝗘𝗳𝗳𝗲𝗰𝘁𝗶𝘃𝗲𝗹𝘆: In this stage, the team has achieved high productivity and effectiveness. Team members work together smoothly and efficiently to achieve the team's objectives. A good leader will now delegate, train team members, and keep a proactive role because the high-performing team is essentially autonomous.

And optionally, 𝟱. 𝗔𝗱𝗷𝗼𝘂𝗿𝗻𝗶𝗻𝗴 - 𝗗𝗶𝘀𝗯𝗮𝗻𝗱𝗶𝗻𝗴 𝘁𝗵𝗲 𝘁𝗲𝗮𝗺: This is the final stage where the team has completed its task, and members are preparing to move on to other projects or assignments. The team leader should acknowledge the team's accomplishments, celebrate successes, and provide closure.

An important thing to mention is that teams could roll back in cycles, depending on their internal state. Therefore, leaders must understand the process and proactively guide their teams.

_______
If you like my posts, please follow me, Dr. Milan Milanović, and hit the 🔔 on my profile to get a notification for all my new posts.

Grow with me 🚀!

#technology #softwareengineering #techworldwithmilan #management #careers 

𝗜𝘀 𝗬𝗼𝘂𝗿 𝗖𝗼𝗱𝗲 𝗥𝗲𝗮𝗱𝗮𝗯𝗹𝗲 𝗕𝘆 𝗛𝘂𝗺𝗮𝗻𝘀?

A codebase's code is only sometimes consistent. Some of the application's code may be so basic as to be trivial. On the other hand, a different section of the codebase can contain more complicated code. In a similar vein, the importance of code varies. Your application's critical business domain is of utmost importance. You might have less crucial components to the extent that they can be separated into other packages.

𝗖𝗼𝗴𝗻𝗶𝘁𝗶𝘃𝗲 𝗰𝗼𝗺𝗽𝗹𝗲𝘅𝗶𝘁𝘆 in software development is a measure of how hard it is to understand a given piece of code—e.g., a function, a class, etc. It has important implications regarding the quality of a software project because it creates a more complex code, which is more susceptible to bugs and causes more rework. Also, it makes it harder to onboard new team members.

Here is the approach to how we can 𝗰𝗮𝗹𝗰𝘂𝗹𝗮𝘁𝗲 𝗰𝗼𝗴𝗻𝗶𝘁𝗶𝘃𝗲 𝗰𝗼𝗺𝗽𝗹𝗲𝘅𝗶𝘁𝘆:

1. Start with a complexity score of 0.

2. For each control structure (such as if, for, while, switch, etc.), increment the complexity score by 1.

3. For each nesting level, increment the complexity score by the nesting level. For example, if you have an if statement inside a for loop, the nesting level is 2.

4. Consider code organization and readability. Look for factors like: length of functions and methods, consistent naming conventions, proper code formatting, etc. If these factors are not met, adjust the complexity score accordingly.

5. Combine the complexity scores from all functions and methods to get the total cognitive complexity for the entire codebase.

There are 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁 𝗿𝗲𝗮𝘀𝗼𝗻𝘀 𝘁𝗵𝗮𝘁 𝗰𝗮𝘂𝘀𝗲 𝗰𝗼𝗴𝗻𝗶𝘁𝗶𝘃𝗲 𝗰𝗼𝗺𝗽𝗹𝗲𝘅𝗶𝘁𝘆, such as:

🔹 𝗖𝘆𝗰𝗹𝗼𝗺𝗮𝘁𝗶𝗰 𝗰𝗼𝗺𝗽𝗹𝗲𝘅𝗶𝘁𝘆 (number of linearly-independent paths through a program module)
🔹 𝗣𝗼𝗼𝗿 𝗻𝗮𝗺𝗶𝗻𝗴
🔹 𝗣𝗼𝗼𝗿 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗮𝗹 𝗱𝗲𝗰𝗶𝘀𝗶𝗼𝗻𝘀
🔹 Large functions
🔹 𝗟𝗮𝗰𝗸 𝗼𝗳 𝗳𝗮𝗺𝗶𝗹𝗶𝗮𝗿𝗶𝘁𝘆 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝗱𝗼𝗺𝗮𝗶𝗻 𝗼𝗿 𝘁𝗲𝗰𝗵 𝘀𝘁𝗮𝗰𝗸
🔹 And more

Read more in the document by SonarSource.

_______
If you like my posts, please follow me, Dr. Milan Milanović, and hit the 🔔 on my profile to get a notification for all my new posts.

Grow with me 🚀!

#technology #softwareengineering #programming #techworldwithmilan #complexity

𝗪𝗼𝗿𝗸𝗶𝗻𝗴 𝗘𝗳𝗳𝗲𝗰𝘁𝗶𝘃𝗲𝗹𝘆 𝗪𝗶𝘁𝗵 𝗟𝗲𝗴𝗮𝗰𝘆 𝗖𝗼𝗱𝗲

In his book "Working Effectively With Legacy Code," Michael Feathers wrote about dealing with legacy software. Even though it's a bit outdated (from 2004.), there are some excellent points inside that still hold their value. This book offers us confidence that we can employ focused, incremental unit testing and refactoring to improve legacy software's testability, comprehension, and extensibility while implementing and delivering new functionality.

The author defines legacy code as "𝘤𝘰𝘥𝘦 𝘸𝘪𝘵𝘩𝘰𝘶𝘵 𝘵𝘦𝘴𝘵𝘴." This implies that if the code doesn't have tests, it's challenging to ensure that changes to the code will only introduce unintended side effects or break existing functionality.

He lists four reasons to change software:

🔹 𝗔𝗱𝗱𝗶𝗻𝗴 𝗮 𝗳𝗲𝗮𝘁𝘂𝗿𝗲
🔹 𝗙𝗶𝘅𝗶𝗻𝗴 𝗮 𝗯𝘂𝗴
🔹 𝗜𝗺𝗽𝗿𝗼𝘃𝗶𝗻𝗴 𝘁𝗵𝗲 𝗱𝗲𝘀𝗶𝗴𝗻 (𝗶.𝗲., 𝗿𝗲𝗳𝗮𝗰𝘁𝗼𝗿𝗶𝗻𝗴)
🔹 𝗢𝗽𝘁𝗶𝗺𝗶𝘇𝗶𝗻𝗴 𝗿𝗲𝘀𝗼𝘂𝗿𝗰𝗲 𝘂𝘀𝗮𝗴𝗲

He says that regardless of how the code is altered, we must always uphold other behaviors we do not plan to change. 

The main contribution of this book is the Legacy Code Change Algorithm:

𝟭. 𝗜𝗱𝗲𝗻𝘁𝗶𝗳𝘆 𝘁𝗵𝗲 𝘁𝗮𝗿𝗴𝗲𝘁𝗲𝗱 𝗹𝗲𝗴𝗮𝗰𝘆 𝗰𝗼𝗱𝗲: Identify change points (Seams) for the target change or new code addition and Find test points where the code's behavior can be sensed.

𝟮. 𝗚𝗲𝘁 𝘁𝗮𝗿𝗴𝗲𝘁𝗲𝗱 𝗹𝗲𝗴𝗮𝗰𝘆 𝗰𝗼𝗱𝗲 𝗶𝗻𝘁𝗼 𝗮 𝘁𝗲𝘀𝘁 𝗵𝗮𝗿𝗻𝗲𝘀𝘀 𝗮𝗻𝗱 𝗰𝗼𝘃𝗲𝗿 𝘄𝗶𝘁𝗵 𝘁𝗲𝘀𝘁𝘀: Break dependencies (very carefully and often without sufficient tests) and get the targeted legacy code into a test harness and cover targeted legacy code with (characterization) unit tests.

𝟯. 𝗔𝗱𝗱 𝗻𝗲𝘄 𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹𝗶𝘁𝘆 𝘄𝗶𝘁𝗵 𝗻𝗲𝘄 𝘁𝗲𝘀𝘁𝘀 (by using the Test Driven Development (TDD) process).

𝟰. 𝗥𝗲𝗳𝗮𝗰𝘁𝗼𝗿 𝘁𝗲𝘀𝘁𝗲𝗱 𝗰𝗼𝗱𝗲 to remove duplication, clean up, etc.

He also suggests some techniques:

🔸 𝗜𝗱𝗲𝗻𝘁𝗶𝗳𝘆𝗶𝗻𝗴 𝘀𝗲𝗮𝗺𝘀: Find places in the code where you can change the behavior without modifying the code itself. Seams can be at the class, method, or function level and help you isolate parts of the code for testing and refactoring.

🔸 𝗦𝗽𝗿𝗼𝘂𝘁 𝗺𝗲𝘁𝗵𝗼𝗱 𝗮𝗻𝗱 𝗦𝗽𝗿𝗼𝘂𝘁 𝗰𝗹𝗮𝘀𝘀: When adding new functionality, create a new method (Sprout method) or a new class (Sprout class) instead of modifying existing code. Unit tests it and identifies where to call that code from the existing code (the insertion point). Then, call your code from the Legacy code.

🔸 𝗪𝗿𝗮𝗽 𝗺𝗲𝘁𝗵𝗼𝗱 𝗮𝗻𝗱 𝗪𝗿𝗮𝗽 𝗰𝗹𝗮𝘀𝘀: When you need to modify the behavior of a method or class, create a new method or class that wraps the original one with the same signature. Rename the old method you want to wrap. Then, call the old method from the new method and put the new logic before/after the other method call.

#technology #softwareengineering #programming #techworldwithmilan #coding

I was called to give a 𝗹𝗲𝗰𝘁𝘂𝗿𝗲 𝘁𝗼 𝘁𝘄𝗼 𝗵𝗶𝗴𝗵 𝘀𝗰𝗵𝗼𝗼𝗹𝘀 𝗶𝗻 𝗺𝘆 𝗻𝗲𝗶𝗴𝗵𝗯𝗼𝗿𝗵𝗼𝗼𝗱 to students.

I discussed some topics they are still unaware of, which are not taught in the school and mentioned in families, but are essential to their success in the future. 

Here are the 𝗺𝗮𝗶𝗻 𝗺𝗲𝘀𝘀𝗮𝗴𝗲𝘀 from the lecture:

𝟭. 𝗧𝗵𝗲𝗿𝗲 𝗶𝘀 𝗻𝗼 𝘀𝘂𝗰𝗰𝗲𝘀𝘀; 𝘁𝗵𝗲𝗿𝗲 𝗶𝘀 𝗼𝗻𝗹𝘆 𝗮 𝗿𝗲𝘀𝘂𝗹𝘁. Success is what we define for us

𝟮. 𝗧𝗵𝗲 𝗺𝗼𝘀𝘁 𝗲𝘀𝘀𝗲𝗻𝘁𝗶𝗮𝗹 𝘁𝗵𝗶𝗻𝗴 𝗶𝘀 𝘁𝗼 𝗯𝗲 𝗯𝗲𝘁𝘁𝗲𝗿 𝘁𝗵𝗮𝗻 𝘆𝗼𝘂𝗿𝘀𝗲𝗹𝗳 𝘆𝗲𝘀𝘁𝗲𝗿𝗱𝗮𝘆 𝗮𝘁 𝟭% (the power of tiny gains). Do not compare yourself to others

𝟯. 𝗧𝗵𝗲 𝗯𝗲𝘀𝘁 𝘄𝗮𝘆 𝘁𝗼 𝘀𝗲𝗹𝗲𝗰𝘁 𝘆𝗼𝘂𝗿 𝗰𝗮𝗿𝗲𝗲𝗿 𝗶𝘀 𝘁𝗼 𝗰𝗵𝗼𝗼𝘀𝗲 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝘁𝗵𝗮𝘁 𝘁𝗵𝗲 𝘄𝗼𝗿𝗹𝗱 𝗻𝗲𝗲𝗱𝘀 𝗮𝗻𝗱 𝘁𝗵𝗮𝘁 𝘆𝗼𝘂'𝗿𝗲 𝗴𝗼𝗼𝗱 𝗮𝘁. But, of course, both things must be checked

𝟰. 𝗜𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝘁𝗵𝗶𝗻𝗴 𝗶𝘀 𝘄𝗵𝗼 𝘆𝗼𝘂 𝗮𝗿𝗲 𝘀𝘂𝗿𝗿𝗼𝘂𝗻𝗱𝗲𝗱 𝘄𝗶𝘁𝗵. You're an average of 5 people who are in your life

𝟱. 𝗬𝗼𝘂 𝘄𝗶𝗹𝗹 𝗻𝗲𝗲𝗱 𝗴𝗼𝗮𝗹𝘀 𝘁𝗼 𝗴𝗲𝘁 𝘀𝗼𝗺𝗲𝘄𝗵𝗲𝗿𝗲. It would help if you had goals for life (vision), year, month, week, and day. Goals should be SMART

𝟲. 𝗧𝗵𝗲𝗿𝗲 𝗶𝘀 𝗮𝗻 𝗲𝘃𝗲𝗻 𝗯𝗲𝘁𝘁𝗲𝗿 𝘁𝗵𝗶𝗻𝗴 𝘁𝗵𝗮𝗻 𝗴𝗼𝗮𝗹𝘀, 𝗮𝗻𝗱 𝘁𝗵𝗼𝘀𝗲 𝗮𝗿𝗲 𝘀𝘆𝘀𝘁𝗲𝗺𝘀. We want to build habits that will get us the desired results. People don't choose their destinies, they select their practices, and their habits determine their futures

𝟳. 𝗧𝗼 𝗮𝗰𝗵𝗶𝗲𝘃𝗲 𝗺𝗼𝗿𝗲, 𝘄𝗲 𝗺𝘂𝘀𝘁 𝘂𝘀𝗲 𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝘃𝗶𝘁𝘆 𝘁𝗲𝗰𝗵𝗻𝗶𝗾𝘂𝗲𝘀, such as GTD, Eisenhower matrix, Ivy Lee method, Pomodoro, etc

𝟴. 𝗙𝗮𝗶𝗹𝘂𝗿𝗲𝘀 𝗮𝗿𝗲 𝗲𝘅𝗽𝗲𝗰𝘁𝗲𝗱 𝗮𝗻𝗱 𝗻𝗼𝗿𝗺𝗮𝗹. Without failures, success is not possible. But don't be disappointed after a loss; mark it as a result and continue

𝟵. 𝗜𝘁 𝗶𝘀 𝗲𝘀𝘀𝗲𝗻𝘁𝗶𝗮𝗹 𝘁𝗼 𝗵𝗮𝘃𝗲 𝗮 𝗴𝗿𝗼𝘄𝘁𝗵 𝗺𝗶𝗻𝗱𝘀𝗲𝘁. We may not be good at something, but we are not good at something YET. We will learn and become better

𝟭𝟬. 𝗜𝗳 𝘆𝗼𝘂 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗸𝗻𝗼𝘄 𝘁𝗵𝗲 𝗽𝗮𝘁𝗵, 𝗰𝗵𝗼𝗼𝘀𝗲 𝘆𝗼𝘂𝗿 𝗺𝗲𝗻𝘁𝗼𝗿. Try to find someone you admire and try to deconstruct what (s)he did. Also, ask people to be your mentors directly. Some of them will say YES

𝟭𝟭. 𝗗𝗼𝗻'𝘁 𝗮𝗰𝗰𝗲𝗽𝘁 𝘁𝗵𝗲 𝗽𝗵𝗿𝗮𝘀𝗲: "𝗪𝗲'𝘃𝗲 𝗮𝗹𝘄𝗮𝘆𝘀 𝗱𝗼𝗻𝗲 𝗶𝘁 𝘁𝗵𝗶𝘀 𝘄𝗮𝘆.". Challenge everything. Break things to first principles and build them again from fundamentals

𝟭𝟮. 𝗕𝗲 𝗽𝗲𝗿𝘀𝗶𝘀𝘁𝗲𝗻𝘁 𝗮𝗻𝗱 𝗯𝗲𝗹𝗶𝗲𝘃𝗲 𝗶𝗻 𝘆𝗼𝘂𝗿𝘀𝗲𝗹𝗳. Then, when you fail, stand up and continue with your goals!

𝟭𝟯. 𝗦𝗰𝗵𝗼𝗼𝗹 𝗿𝗲𝘄𝗮𝗿𝗱𝘀 𝘁𝗵𝗲 𝗯𝗲𝘀𝘁 𝘀𝘁𝘂𝗱𝗲𝗻𝘁𝘀, 𝗹𝗶𝗳𝗲 𝗿𝗲𝘄𝗮𝗿𝗱𝘀 𝘁𝗵𝗼𝘀𝗲 𝘄𝗵𝗼 𝗮𝗿𝗲 𝗰𝗼𝗻𝘀𝘁𝗮𝗻𝘁𝗹𝘆 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴

#career #personaldevelopment #success #productivity #education

𝗛𝗼𝘄 𝗧𝗼 𝗘𝗻𝗮𝗯𝗹𝗲 𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻 𝘄𝗶𝘁𝗵 𝗣𝘂𝗹𝗹 𝗥𝗲𝗾𝘂𝗲𝘀𝘁𝘀?

With Pull Requests, we lost the ability to have a proper Continuous integration process, in a way that we delayed integration due to code reviews. So here comes a “Ship/Show/Ask” branching strategy. The thing is that not all pull requests need code reviews.

So, whenever we make a change, we have three options:

🔹 𝗦𝗵𝗶𝗽 - Small changes that don’t need people’s review can be pushed directly to the main branch. We have some build pipelines running on the main brunch, which run tests and other checks, so it is a safety net for our changes. Some examples are: fixing a typo, increasing the minor dependency version, updated documentation.

🔹 𝗦𝗵𝗼𝘄 - Here, we want to show what has been done. When you have a branch, you open a Pull Request and merge it without a review. Yet, you still want people to be notified of the change (to review it later), but don’t expect essential discussions. Some examples are: local refactoring, fixing a bug, added a test case.

🔹 𝗔𝘀𝗸 - Here, we make changes and open a Pull Request while waiting for feedback. We do this because we want a proper review in case we need clarification on our approach. This is a classical way of making Pull Requests. Some examples are: Adding a new feature, major refactoring, and proof of concept.

Back to you, have you already tried this strategy?

_______
If you like my posts, please follow me, Dr. Milan Milanović, and hit the 🔔 on my profile to get a notification for all my new posts.

Grow with me 🚀!

#technology #softwareengineering #programming #techworldwithmilan #coding

Taplio

Dr. Milan Milanović's Linkedin Analytics

Dr. Milan Milanović

What is Dr. Milan talking about?

Who is engaging with Dr. Milan

Dr. Milan Milanović's Best Posts (last 30 days)

Want to drive more opportunities from LinkedIn?

Taplio

.css-1jgreyo{background-image:linear-gradient(284deg, rgba(39,43,72,1) 0%, rgba(33,47,183,1) 100%);color:transparent;-webkit-background-clip:text;background-clip:text;}Dr. Milan Milanović's Linkedin Analytics

Dr. Milan Milanović

What is Dr. Milan talking about?

Who is engaging with Dr. Milan

Dr. Milan Milanović's Best Posts .css-qqfgvy{font-size:var(--chakra-fontSizes-md);}(last 30 days)

Want to drive more opportunities from LinkedIn?

Dr. Milan Milanović's Linkedin Analytics

Dr. Milan Milanović's Best Posts (last 30 days)