An Independence Day message to young engineers, learners and builders. Most of us are the third generation born into a free India, so freedom is a condition we inherited rather than a memory we carry. Earlier generations built the institutions and then the services industry. The unfinished work handed to this one is originating technology instead of only executing it well, and that takes capability and character, neither of which access to tools supplies.
A very happy Independence Day to everyone reading this: to the students, the engineers, the teachers, and to every Indian doing good work wherever in the world they are doing it. Today is the eightieth Independence Day, and it is worth stopping for. A country that began in 1947 with almost no industrial base now designs semiconductors, has landed a craft near the Moon’s south pole and put an observatory in orbit around the Sun, runs the largest real-time payments system in the world, and sends engineers into every serious technology company on the planet. Whatever remains unfinished, that is a remarkable inheritance, and the people who built it have earned today’s celebration completely.
Celebration is the right response, and tribute and memory belong with it. The eightieth Independence Day can also carry one harder question without spoiling the mood: what are we doing with the freedom we inherited?
It is worth being accurate about the distance, because it is easy to speak as though the freedom struggle were our parents’ doing. It was not. If you are in your twenties, the people who won independence were your great-grandparents’ generation: they were young adults in 1947. Your grandparents were the first generation born into a free India, your parents the second, and you are the third. If you are in your forties, move each of those back by one. Either way, nobody in your office remembers 1947. Freedom is not a memory we carry. It is a condition we were born into, and that is a very different thing to be responsible for.
The distance matters, because every generation since has been handed a different piece of unfinished work. The first built institutions out of very little: the IITs from 1951 onward, CSIR and TIFR, ISRO in 1969. The next worked within the limits of a closed economy, and then through the opening of 1991. The one after that built the software services industry that made Indian engineers credible around the world. None of them inherited a finished country either. Each was handed a problem and judged by what they did with it.
Our responsibility is different, but it is no smaller. We have education, technology, global markets, powerful tools and more information than any generation before us. The question is no longer whether opportunity exists. The question is whether we will develop the capability and character to use it well.
What this Independence Day asks of young engineers
For young people entering technology today, freedom should not mean the freedom to drift, to copy, to consume, or to wait for someone else to create direction. It should mean the freedom to learn difficult things, build useful systems, solve real problems, and become reliable when the work becomes uncertain.
The generation that won independence secured the right to choose India’s future. Ours has to become capable enough to build it.
Access is not capability
This generation has access that would have seemed impossible fifty years ago. Courses, documentation, open-source repositories and communities. Assistants that explain, summarise, write code and propose solutions. Hardware, cloud services, development boards and global learning resources. Career opportunities beyond the limits of geography.
But access is not capability.
A learner can work through hundreds of tutorials and still stop, unable to proceed, in front of an unfamiliar failure. A developer can produce code in seconds and still be unable to explain why it fails in production. A professional can collect certificates and still struggle to take ownership when a system breaks. We wrote about this at length in Information Is Free. Skill Is Not., and the gap has only widened since.
India will not become stronger because more people can reach answers. It will become stronger when more people can take responsibility for problems.
This is not an argument against modern tools. The argument is narrower and, I think, harder to dismiss: no tool supplies sound judgment, technical depth, ethical responsibility, patience with difficult work, the ability to tell a symptom from a cause, or the willingness to say “I do not know yet, but I will find out.”
Where India actually stands in technology
Independence Day is a reasonable moment to look at the numbers rather than the slogans. It helps to be specific here rather than patriotic, because the honest picture is the more useful one.
The industry the previous generation built is genuinely large. India’s technology sector is expected to cross roughly 300 billion dollars in revenue in FY26 and employs about 5.8 million people, on NASSCOM’s figures. Alongside it now sit more than two thousand global capability centres, employing close to 1.9 million professionals doing engineering and research work in India for companies headquartered elsewhere. India also builds and runs digital systems at a scale very few countries attempt: UPI processed 241.62 billion transactions in FY26, worth about 314 lakh crore rupees.
Hardware is moving too, though more slowly than the announcements suggest, and the distinction is worth holding on to. Assembly and test plants are now operating. Micron’s packaging facility at Sanand was inaugurated in February 2026 and Kaynes Semicon’s plant at the same site in March 2026, and the CG Power venture with Renesas began commercial production in July. Those are assembly, test and packaging plants. They are not wafer fabrication. India’s first commercial fab, Tata Electronics with PSMC at Dholera, is targeting first silicon late in 2026 and has not produced it yet. The second phase of the semiconductor programme, cleared in July 2026, is aimed precisely at what is still missing: equipment, materials, design intellectual property and research centres.
The gaps are real and they are measurable. India’s gross expenditure on research and development sits at about 0.64 percent of GDP, according to the Economic Survey 2025-26, against roughly 2.4 percent for China and close to 5 percent for South Korea. More revealing than the total is who funds it: business accounts for only about 41 percent of Indian R&D, against roughly 77 percent in China and 79 percent in South Korea. Electronics exports reached about 48 billion dollars in FY26, but of the 29 billion in smartphone exports, around 22 billion was one foreign company’s product assembled here. Estimates of how much value is genuinely added inside India vary widely depending on what is being counted, and that disagreement is itself a signal of how young the component base still is.
Read plainly, that says something specific about the work ahead. India has proved it can operate at scale, execute reliably, and run other people’s engineering well. What remains thin is the part where the intellectual property, the components, the tools and the research originate here. That is not a complaint about the country. It is a description of the unfinished work this generation has been handed, and almost all of it is engineering work.
The generations before us proved that India can execute. Ours has to prove that India can originate.
Freedom needs discipline
Freedom without discipline becomes distraction.
Every young person now chooses what to learn, where to work, what to build and how to spend time. That freedom becomes meaningful only when it is paired with self-direction. For an aspiring technologist, self-direction is specific and unglamorous:
- Learning fundamentals before chasing trends.
- Finishing projects instead of endlessly starting new ones.
- Reading documentation instead of depending only on summaries.
- Debugging failures instead of replacing the work with a copied answer.
- Building evidence of skill instead of announcing ambition.
- Treating time, commitments and other people’s trust seriously.
The country does not need more people waiting to be motivated each morning. It needs people who can create momentum from within: who prepare before the opportunity arrives, who persist when learning becomes uncomfortable, and who take responsibility before it is assigned to them.
Talent may open a door. Discipline decides whether you can be trusted after you enter.
Your move → Pick the one thing you have been avoiding because it is genuinely hard, not the one you have been postponing because it is dull. Give it an hour a day for a month. The difficulty is the point; that is where capability is actually built.
Honesty, integrity, sincerity and accountability
These words can sound like they belong in a school assembly rather than an engineering discussion. They do not. In technical work each of them has a precise meaning, and a team notices their absence quickly.
Honesty is what makes your output usable by anyone else. It is reporting the test that failed and not only the ones that passed. Saying a task is half finished when it is half finished, rather than reporting eighty percent for three weeks. Admitting that the fault came from your own change. Saying “I do not know yet” instead of offering a confident guess that sends a colleague in the wrong direction for two days. A misleading status report is not merely a social failing. It is bad data, and someone else will plan against it.
Integrity is what you do when nobody will check. Nobody will know you skipped the test on the path that rarely executes. Nobody may notice a licence obligation left unmet, or sources never published for the GPL code inside a shipped image, or a third-party component used outside its terms. Integrity is doing the work properly regardless, and refusing to ship something you know to be unsafe even when refusing is expensive.
Sincerity is meaning what you say. It is the difference between a review comment written to improve the code and one written to look thorough. Between asking a question because you want to understand and asking it to appear engaged. Between teaching someone to think and performing expertise in front of them. People detect the difference sooner than we expect, and they adjust how much they trust us accordingly.
Accountability is owning the outcome, not only the task you were handed. It is following a fault past the boundary of your own module instead of stopping at “that is not my code”. It is doing what you said you would do on the day you said it, without anyone following up. It is staying with a problem you caused until it is genuinely closed, rather than until attention has moved elsewhere.
And accountability is the one of these that no workplace can install in you. Organisations try. They build review cycles, checklists, tracking boards, escalation paths and sign-offs. Every one of those mechanisms can detect a missed commitment after the fact. Not one of them can produce a person who did not want to miss it. Accountability enforced from outside lasts exactly as long as the enforcement. The engineer who is careful only because the process catches them will behave differently the moment the process cannot see them, and in real engineering there is always a place the process cannot see.
It has to be formed at the core, long before a salary is involved: in how you treat a deadline at college, a promise to a friend, a commitment to a study group, a lab exercise nobody will grade. By the time a workplace meets you, it is not teaching you accountability. It is discovering whether you already have it.
These qualities also decide whether credit moves correctly. Naming the colleague whose idea you used, and crediting the person who found a fault rather than only the person who fixed it, costs nothing and predicts reliably how someone will behave when the stakes are higher.
A technical mistake can be corrected in an afternoon. A reputation for shading the truth takes years to correct, and it changes how every number you report is read.
A country is not strengthened by capable people who cannot be relied upon. Capability without character is only a larger capacity to do damage. Independence Day language tends to honour courage and sacrifice, and rightly so. In ordinary working life those same virtues usually appear in a smaller form: honesty when it is mildly inconvenient, and care when nobody is watching.
Your move → The next time you report progress, report the actual state rather than the comfortable one, and say plainly what you have not yet verified. It is uncomfortable exactly once. After that, people begin to treat your estimates as information rather than as optimism.
What building means for engineers
Building the nation can sound abstract. For engineers it is usually ordinary work done at a high standard. It is designing a product that works reliably in real conditions. Writing code another engineer can understand and maintain. Debugging an intermittent failure instead of hiding it. Reporting a security issue responsibly. Improving a process that wastes time or introduces risk. Building local technical capability rather than permanent dependency. Teaching a junior engineer how to think, not only which command to run. Solving real Indian problems with execution that would stand up anywhere in the world.
For embedded Linux, edge AI, systems software and hardware-enabled products, this matters more than most fields. India’s technological standing will not be secured by presentations, copied repositories or fashionable claims about artificial intelligence. It will be secured by people who understand a whole system: the hardware, the operating system, the drivers, the reliability behaviour, the security position, the way it fails in the field, and who owns it for the years afterwards.
A serious engineer is not defined by how quickly they can produce an answer. They are defined by whether they can be trusted when the answer is not obvious.
The test the AI era sets
Artificial intelligence makes this responsibility more urgent, not less.
These tools produce explanations, code, test ideas, architecture sketches and summaries. Used well, they make a capable engineer faster. Used carelessly, they let an unprepared learner appear productive while removing the struggle through which understanding is built. The risk is not that engineers will be replaced. The risk is that engineers will let these tools replace the thinking they were supposed to develop.
The weak habit is short: ask for an answer, copy it, move on, and be stranded when conditions change. The strong habit takes longer and compounds: frame the problem, identify the cues, form a hypothesis, use the tool or the documentation to test it, verify the result, reflect on what the failure taught you, and carry that into the next problem.
The engineers who remain valuable will not be those who refuse these tools. They will be those who use them without surrendering their judgment.
What mentors owe their learners
A mentor’s responsibility is changing too.
When information was hard to obtain, teaching could concentrate on transmitting it. Information is now searchable, explainable and generatable, so a mentor has to do more than supply content. The work is to help a learner see what matters inside a complex problem, recognise the technical and behavioural cues that point somewhere useful, build mental models rather than memorise isolated facts, reflect on approaches that failed without losing confidence, find the courage to begin when no solution is visible, and communicate clearly enough to take ownership of the outcome. That is also why we argued that you should pay for mentorship rather than for information.
In my own sessions I do not want people to leave with notes, commands and a finished lab. I want them to leave more capable of facing work they have never seen before. That requires engaging with the problem, reflecting on it, learning to pick the useful cues out of the noise, and having the confidence to keep moving while the path is still unclear.
The real test of learning is not whether you can reproduce a solution. It is whether you can begin when no solution is visible.
Do not wait to feel ready
You may not have the best college, the ideal team, expensive equipment, a clear mentor or a good first opportunity. None of those conditions removes the responsibility to begin. Six commitments, in the order they actually pay off:
- Build depth before visibility. Learn the underlying system before trying to look impressive online.
- Build evidence before expectation. Create projects, debug failures, document decisions, and accumulate work that proves what you can do.
- Build habits before ambition. Consistency, reading, experimentation and reflection compound further than bursts of enthusiasm.
- Build judgment before dependence. Use mentors, tools, documentation and communities, but do not hand your thinking to any of them.
- Build trust before a personal brand. Deliver carefully, communicate honestly, and be the person colleagues can rely on when something goes wrong.
- Build for usefulness, not applause. The work that matters most often attracts no attention at first. It still compounds.
Your move → Take the six commitments above and mark the one you are weakest at, honestly. Most engineers already know which it is. Work on that one for the rest of this year rather than spreading effort evenly across all six.
Do not ask only what India can offer your career. Ask what capability you are building that India can rely on.
Nation-building is ordinary work
Independence Day speeches naturally describe the large version of nation-building: announcements, flagship companies, well-known founders. India’s future will not be built only there. It will also be built in laboratories, factories, classrooms, startups, maintenance teams, product reviews, field deployments, research groups and engineering teams across the country.
It is built when an engineer refuses to ship a design known to be unsafe. When a developer documents a difficult fix for whoever comes next. When a teacher tells a learner the truth instead of selling easy success. When a team repairs the root cause instead of concealing the symptom. When a founder solves a real problem rather than copying a trend. When a young professional chooses craftsmanship over a shortcut.
Nation-building is not always dramatic. Often it is the quiet decision to do ordinary work with extraordinary seriousness.
The right tribute
The eightieth Independence Day is not only a story of freedom won. It is a challenge to everyone who inherited that freedom. We have been given access, opportunity and the ability to take part in shaping a country with a great deal of unfinished work in it.
The right tribute on Independence Day is not only celebration. It is a decision: to become capable, to work honestly, to think independently, to build deeply, to own what we do without being asked to, to stay useful when conditions are difficult, and to create more value than we consume.
Your move → Before this week ends, write down one system you intend to understand well enough to explain to someone else, and one problem you intend to own end to end. Then tell one person, so that it costs you something to abandon it.
Freedom gave us a chance. Building is our responsibility.
Let us become the generation that uses its freedom not merely to seek a better future for itself, but to develop the competence, character and courage required to build a better India.
Frequently asked questions
Why write an Independence Day message about engineering?
Because freedom is exercised through the work people choose to do. The generation that won independence decided India’s direction; this generation decides what is actually built. For engineers, that decision shows up in ordinary work done to a high standard rather than in commemoration.
Is this an argument against using AI tools?
No. The argument is that these tools cannot supply judgment, depth or responsibility. Used well they make a capable engineer faster. The risk is allowing them to replace the thinking you were supposed to develop, which is a habit rather than a technology.
I do not have a good college, mentor or equipment. Where do I start?
Start with depth in one system you can reach, and with evidence rather than announcements. Finish a project, debug something properly, document what you decided and why. None of the conditions you lack removes the ability to begin.
What does “access is not capability” mean in practice?
It means being able to reach an answer is not the same as being able to solve a problem. The test is not whether you can retrieve a solution, but whether you can make progress when no solution is visible.
Can a workplace teach accountability?
It can detect the absence of it, through reviews, checklists and tracking, but it cannot install it. Accountability enforced from outside lasts only as long as the enforcement. It has to be formed earlier, in how a person treats commitments that nobody is checking, and a workplace mostly discovers whether it is already there.
