Be visibly competent. If you have skills but others do not know about them, you will never get the opportunities you deserve. Make your abilities visible, and ensure that what you bring to the table is impossible to ignore.

The 2026 IPO rush explained in one sentence: Investors need liquidity to fund AI companies that need liquidity to build AI that will eventually replace the companies that just IPO'd. It's a circular economy of desperation dressed up as innovation. #AI #IPO #TechMarkets

India spent 39 years and over 2000 crore on the Kaveri engine and still cannot hit the thrust a fighter needs. problem was never funding, GTRE had no access to how Rolls Royce or GE engineers think about single crystal blade metallurgy or combustion instability during flight. That kind of knowledge sits inside people who have iterated on live programs for decades, You cannot download someone else iteration history. You have to be inside the program to absorb what it teaches Every country that builds jet engines went through the same ugly loop, Test, fail, retest, discover something that fits nowhere in a textbook. India had no high altitude test facility for the Kaveri. Had to ship the engine to Russia for every trial run. You cannot absorb the parameters that separate a working hot section from a molten one by reading papers. That knowledge gets created inside the program itself. Miss the program, miss the knowledge. No workaround exists. GE will transfer 80% of F414 manufacturing tech to HAL, The remaining 20% is where the real gap lives. Core metallurgy, turbine cooling geometries, thermal margin tables that took forty years of flight data to build. Safran meanwhile is offering India full hot section know how for the AMCA engine. Two competing offers from two different countries, both telling India the same story. You can buy the right to assemble, You cannot buy the intuition that shaped the design. I love yur thought by the way, I watch few weeks Ago reel where he talked about how hard to make just blade :)

It's going to be pretty sad once Claude Code subsidy goes away... There is no way I will be able to spend thousands of dollars on tokens every month... Until that happens, going to use it to the max...

Every migration you will ever do is a Ship of Theseus problem. The ancient Greeks had a paradox: if you replace every plank of a ship one by one, is it still the same ship? We face this every day, except the ship is in production :) The naive version of a migration is a full cutover: stop the old system, start the new one. It almost never works at scale. What actually happens is a slow, plank-by-plank replacement. Let me give you some examples... Database migrations are the clearest example. Moving from MySQL to PostgreSQL takes time. You run both databases in parallel, write to both (dual-write), and slowly shift small portions of reads to Postgres while monitoring for inconsistencies. Then, you gradually port the entire codebase. Language migrations follow the same pattern. You never rewrite everything from one language to another and flip the switch. It is also done on a piece-by-piece basis. A similar strategy is followed during monolith-to-microservices migrations. So, if you are planning something big, consider breaking it into planks and changing one at a time until your entire ship is new. Pro tip: use this analogy to sound smart in meetings and discussions :) It always works.

Claude just fixed a flaky test by literally mocking the buggy function after spending 15 minutes trying to fix it. Peak AI behavior. To be honest, I would have done the same thing as an intern, out of frustration. Fascinating that AI can be both an intern and a staff engineer at the same time.

When you join a new organization, it is quite natural to feel a strong urge to fix things. Let me ruffle some feathers here... You will notice processes, tools, or practices that feel inefficient, outdated, or even wrong. Maybe the team uses Jira instead of Linear, Java instead of Go, MongoDB instead of MySQL (for a use case), or Tabs instead of Spaces. It will be tempting to point it all out immediately. Resist that urge. Do not get overwhelmed by outrage. Every organization has quirks, and yours is no exception. Complaining loudly in your early days won't make people rally behind you. You may be right, but what you lack is context. What looks foolish from the outside might have made perfect sense at the time. So, start by asking why. Be curious. Ask questions, and listen closely. The more context you gather, the clearer the rationale will become. At first, focus on integrating rather than fixing. Show reliability, do good work, and build relationships. Once you have established credibility, you'll find that people are more open to your perspective. That's when you can choose your battles carefully. Keep this simple framework in mind: - Ask why before suggesting what - Listen more than you speak - Build trust before pushing change - Pick one thing, not everything Prove your ideas with small wins, and show that you understand the context. Over time, you will gain the influence to bring major changes and improvements. You can't fix everything on day one, but you can ruin trust in one. Hope this helps.

The engineers who will thrive in the next 5 years aren't the best coders.They're the ones who understand: → System design at scale → Business context behind the feature → How to ship, not just buildCode is the easy part now. Judgment is the moat. #Career #AI #Leadership

The industry has gone completely nuts. Use tokens to generate AI code and documentation slop. Then use even more tokens to understand and review that slop. Then judge engineers by token usage instead of how empathetic and clear their docs and code actually are, and completely neglect human comprehension. Utter nonsense.

Jira mistakes killing your sprint velocity Treating the sprint backlog as a wish list No WIP limits on the Kanban board Skip retrospectives when things are "going fine" Mix bug tickets and feature work without swimlanes Velocity as a performance metric, not a planning tool

As Indian IT giants lose ground, Anthropic & NVIDIA surge ahead — an inverse equation reshaping global tech power. #IndianIT #Anthropic #NVIDIA #AI #TechShift #MarketDynamics