This came during a fireside chat with Meta’s Mark Zuckerberg at the LlamaCon conference on Tuesday. For those of us watching, it was a new phase of software development, where humans and machines work side by side, not in theory, but in the process of producing code.

This is beyond speeding things up. It’s about what’s being built, who’s building it, and how much control engineers still have. 

Nadella pointed out that Python has been more responsive to machine-written code, while C++ — a language notorious for its strictness — is trailing. That tells us something important: the technology isn’t universal, and the shift isn’t clean.

Interestingly, when Nadella turned the same question back to Zuckerberg — how much of Meta’s code is machine-generated — Zuck didn’t offer numbers. “I don’t know,” he admitted, though he did confirm that Meta is investing heavily in automated development and expects machines to handle “half of our coding work” before long. The silence on current figures wasn’t lost on anyone.

Meanwhile, Google’s CEO Sundar Pichai, on an earnings call last week, claimed more than 30% of Google’s code is now machine-generated. But here’s the catch: no one seems quite sure what counts as “generated.” Are we talking about boilerplate scripts suggested by autocomplete tools or fully functional modules? Pichai didn’t say, and Nadella didn’t clarify either. That makes it hard to compare — and easy to overhype.

Microsoft’s Chief Technology Officer Kevin Scott added another layer of boldness to the mix. “I expect 95% of all code to be machine-generated by 2030,” he said recently. It’s a huge number. But these projections gloss over a real tension developers feel: where does assistance end and overreliance begin?

The tools themselves — those AI-driven co-pilots, reviewers, and debuggers — are becoming essential. At Microsoft, Nadella says they’re now baked into the workflow, not just for writing code, but for catching bugs and managing quality. It’s not about coding faster. It’s about trusting what the system builds — and knowing what to do when it breaks.

But even with all this automation, we’re not seeing uniform results. Some languages benefit more than others. Some teams resist the change entirely. And while executives trade stats and predictions, there’s still little clarity on what “AI-generated” actually means in practice.

The bottom line? We’re not in a world where machines are just helping. They’re now co-authors of the digital infrastructure that powers everything — and not everyone is ready for that level of partnership.

Coming from the generation that wrote procedural codes and then transitioning into Object Oriented Programming (OOP) when I started working with organised teams. 

It was a different ballgame requiring discipline and adhering to programming standards. 

This article is a compilation of my experiences, lessons, and knowledge I gathered about;

• the importance of coding standards
• class organisation
• frameworks and
• the seamless migration of legacy codebases.

Note that the examples I will give in this article are typically PHP-based, but the same principles apply to other OOP-focused programming languages like JavaScript, TypeScript, Java, Python, etc.

Procedural Programming  Phase (Spaghetti Coding)

Procedural programming was the beginning of my journey into software development. This paradigm is usually simple when developing very little pieces of code snippets.

However, in more complex requirements, those snippets are grouped into separate files and included in the runtime when required or preferably into separate functions. 

This method indisputably helped me accomplish tasks, but over time I realised the limitations of this method when it comes to developing more complicated applications. 

These limitations include;

• Having different files that accomplish similar requirements,
• complexity in managing codebase and unorganised workflows—which increases as the application grows.

The above code snippet will work for a simple user registration page but will become more complex when adding extra features such as email verifications, etc.

Transition into Object-Oriented Programming

I couldn’t wave off the idea of data and action encapsulation within objects as it seemed to be the solution to my ever-increasing project complexity. 

This idea prompted my first transition into object-oriented programming (OOP). 

My early attempts at object-oriented programming were filled with setbacks resulting from my ignorance of fundamental coding concepts. 

The classes I took, though rigid, turned out incompetent as they excluded several fundamental principles of effective design. 

My Discovery: The Need for Coding Standard

My understanding of the significance of coding standards was fine-tuned when I began collaborating with well-structured teams. 

Guidelines like SOLID (Single Responsibility, Open-Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion) were followed by these groups. 

These principles are more than theoretical exercises; they provide actual instructions for more resilient, scalable, and easy-to-maintain codes. 

There are numerous things to understand about programming principles but I will explain some important ones.

1. Single Responsibility Principles (SRP)

This is one of the first principles I embraced.

Depending on your preferred programming language, the main requirement for this principle is knowledge of Object Oriented Programming, how it works, and how to organise your codes into classes and methods.

The Single Responsibility Principle (SRP) states that a class should have only one reason to change. 

I started implementing SRP by breaking down my monolithic classes into smaller and precise ones. This made my codebase easier to understand and maintain. 

This saved me the cost of breaking my functionalities into separate files and including them when needed.

Now let’s apply what we’ve learned so far. We will convert the previous functionalities into classes. 

If we are applying the SRP;

1. We will have a class called Database, which will be in charge of making connections to the database.

2. We will also define another class called AuthController which will house all the “Methods” that control the Authorization such as register, login, verifyEmail, etc.

2. SOLID Principle: Other Components of SOLID Principles.

My coding techniques were further refined as I continued to adhere to the remaining SOLID principles. 

My understanding of the importance of making sure that subclasses and their base classes are compatible came from—the Liskov Substitution Principle (LSP). 

I was inspired to build more detailed and precise interfaces by the—Interface Segregation Principle (ISP), and finally was able to separate high-level modules from low-level implementations by the–Dependency Inversion Principle (DIP).

Programming Frameworks

I started leveraging programming frameworks as I was learning coding standards. Here is why; 

By providing a standardised basis for application development, frameworks guarantee consistency and best practices. 

I was able to reduce the amount of boilerplate code I needed to write because they also offered various built-in functionalities.

Other Benefits of Using Frameworks

I was also able to drastically improve my coding skills after adopting frameworks like React(which relies on JavaScript) for front-end development and Laravel(which relies on PHP) for back-end development. 

By enforcing coding standards and architectural principles, these frameworks strengthened and simplified the maintenance of my apps. 

During my learning phase, the community support and detailed documentation were also beneficial.

Migrating Legacy Codebases

This migration was another leap in my programming journey. 

From the knowledge I gathered to this point, I knew it was time to transform some of my legacy codebases. 

Transitioning from an OOP codebase that was procedural and ill-structured to one that followed conventional coding techniques was one of the most satisfying tasks I ever encountered. A slow, iterative strategy was crucial for a smooth migration.

Firstly before I started reworking, I examined my legacy codebases and ensured I followed coding standards for the most important parts of the code.

I was able to thoroughly test each modification before going on to the next by refactoring it in small steps. 

Using the Single Responsibility Principle, I divided huge classes into more manageable ones. Subsequently, I made sure my classes could be extended without any changes by applying the Open-Closed Principle.

As I refactored my code, I noticed significant performance improvements and my applications became more efficient because I organised my classes better and reduced dependencies.

The use of design patterns also contributed to these optimizations, providing tried-and-tested solutions to common problems.

Conclusion

My transition from procedural to a standard codebase has been a life-changing experience for me. 

My adoption of coding standards like the SOLID principles and the use of frameworks transformed me into a more disciplined and efficient developer. 

The process of transferring historical codebases has been incredibly gratifying, despite its challenges, as it has influenced the creation of maintainable and streamlined applications.

Generally, this series of experiences revealed the trend in the software development industry. It is always changing. 

So, it’s important to adapt to change, learn best practices, and follow coding standards to keep up with the trend. Beyond this, we can also build long-lasting apps that are scalable, stable, and easy to maintain if we learn and adopt these standards. 

The NCS TIDP Programme received impressive response, with applications from 47 teams showcasing their ideas and solutions to address societal challenges.

During the first day of the boot camp, Tuesday, held in Lagos, industry leaders and mentors from the ICT sector gathered to interact with the four selected teams.

The mentors and various committees are committed to working closely with the teams to ensure the transformation of their ideas into tangible products.

Speaking with TechEconomy, Professor Adesina Sodiya, President of NCS, emphasized the importance of building a strong foundation for innovators and guiding them towards creating finished products. 

To facilitate their progress, each team member will receive brand-new laptops, and financial support will be provided to keep them motivated and focused.

The TIDP program, initiated approximately 3 years ago, aims to foster innovation and development in Nigeria. It seeks to provide resources and expertise to young individuals with brilliant ideas but limited means to translate them into world-class solutions. 

By bridging this gap, Professor Adesina said the program aims to build a community of young innovators who can become successful entrepreneurs or find employment.

“The upcoming second boot camp for the technology team is already in the planning phase, following the success of the first phase last year. The products developed by the first batch of participants will be showcased in July after a dedicated period of three to four months for project completion.”

The selection process for the program, according to him, involved assessing five major criteria, including the commercial viability of the product and its potential impact on society. The aim is to develop implementable solutions within a specified timeframe, while also ensuring uniqueness and market appeal,”

Sodiya said.

Further, he commended Leo Stan Ekeh, Chairman, Zinox Technologies for his tremendous support for the program since inception. While responding to if there are plans to approach stakeholders in the public sector, the President confirmed that there have been ongoing conversations geared towards getting more support. 

Asked Dr. Mohammad Sirajo Aliyu, Deputy President of NCS, what his advice would be for the participants, he urged the teams to seize the opportunity offered by the program, highlighting the chance to learn and explore various aspects of their projects. 

Experts from different fields will provide guidance and mentorship, covering both technical aspects and the business side of innovation. Participants will gain valuable skills in product packaging, marketing, patenting, and more.

The TIDP represents a significant step by the NCS to nurture young talent and promote innovation in Nigeria. By providing immediate resources and support to selected individuals, the program aims to transform ideas into impactful innovations that benefit both society and the innovators themselves.

The evaluation and launch of products developed by the participating teams are expected to further demonstrate the value of their contributions to society.

With the TIDP, the NCS is positioning Nigeria as a hub of innovation, empowering its young population to make significant contributions and shape the future of technology in the country.

Responding to questions on sponsorship and the support for the selected teams, Dr. Mohammad said NCS’s sponsorship approach involves a thorough assessment of the needs and requirements of the participants. 

Firstly, we provide them with laptops to support their work. Additionally, we allocate resources based on the specific development stage of their product. At the end of each month, when they present their progress, we collect a comprehensive report and provide them with a token for their upkeep. 

“Our approach focuses on addressing their individual needs rather than simply providing pocket money. Moreover, during the product launch, we explore various options such as partnering with external entities, selling the product, or offering a share of the product to interested parties,” he said.

While addressing the young innovators, Lanre Ogunya, CEO at VTpass.com who will also serve as one of the mentors for the program, urged them that acquiring business skills and not just focusing on writing codes will be a game changer.

It is not just about the hard skill of coding, you must learn how to run a business by leveraging all the online resources and mentorship.”

Ogunya said.

According to Lanre, identifying market gaps and opportunities, developing a business model, knowing how to manage financial and human resources, marketing and customer acquisition, and leadership are germane for any entrepreneur who wants to successfully launch a product in the market.