Rachit Tyagi | Engineering & AI

Over the years, the way I approach software engineering has changed. Earlier in my career, a large part of the work was translating requirements into code, choosing the right framework, and figuring out how to implement a feature. Those skills still matter. But as systems become more interconnected and AI coding tools make implementation faster, I find that the most important engineering work increasingly happens before and after the code is written . Before implementation, I need to understand the problem, define the constraints, and make architectural decisions. After implementation, I need to establish that the system behaves correctly—not just in the happy path, but under retries, invalid inputs, partial failures, and changing requirements. This is the workflow I try to follow. 1. Define the Problem Before Writing Code I start by asking a few questions: What problem are we actually solving? What does success look like? What constraints already exist? Which...

For the first 15 years of my engineering career, I had a single metric to gauge my productivity: How many lines did I write today? This is how I gauge it in 2026: Did I make enough good decisions — and validate them well enough? I didn’t realize it, but that transformation has quietly altered the way I am going to approach designing systems, debugging production problems and even writing documentation. From ASP.net web forms to react / Angular, MSSQL to Postgresql, C# to NodeJS, I’ve come to a simple realization: AI doesn’t replace experienced engineers.  It magnifies that engineer who groks what systems are. This isn’t hype. Here’s how I actually use AI in production-grade settings to help me think better, design faster, and make less avoidable mistakes. No fluff. Just what works. 1️⃣ From Idea → Structured Architecture (Faster, Not Lazier) Early in my career, this is what it would look like to design a system:- Whiteboarding Confluence docs Iterating diagrams Discovering...

In C/C++ a semicolon is used to terminate the statement.But if,while,switch(conditional constructs) do not require a semicolon to terminate.So if we use the printf statement inside these conditional constructs,then we do not require any semicolon to terminate the statement.

Java code snippet to count number of words in a sentence