Mastodawn

Senior devs: you’re not behind, you’ve just gotten very good at one lane.

I spent 15 years shipping features, then realised I’d never even touched
Corepack or Yarn. The real bug? The ecosystem blind spot.

Read how I zoomed out and built habits for staying aware.

#Career #Softwaredevelopment

https://g.omid.dev/HGHr81r

The Zoom-Out: When 15 Years of Code Meets the "Ecosystem Blind Spot"

It happened to me this morning. After 15 years in the trenches—building frontend architectures, dipping into the backend, leading teams, and surviving countless framework wars—I hit a wall. Not a technical wall, but a conceptual one. I realized I didn’t know what Corepack was. I’ve never actually used Yarn. I’ve heard of test-managers, but I’ve never managed to actually run one in a production pipeline. At first, the feeling was a sharp mix of guilt and sadness. How can I be a “Senior” or a “Lead” and miss things that seem so trivial to others? But then I zoomed out. I stopped looking at my specific lane—the features, the bugs, the immediate sprint—and looked at the entire ecosystem.

Omid Farhang Jan 25

NetBlocks Jan 25

RE: https://mastodon.social/@netblocks/115954808295822658

🗓️ 17 days after #Iran introduced an internet blackout to mask a deadly crackdown:

- minimal whitelisted service available to some users
- circumvention allows messages to get through
- brief connectivity spikes give false impression of wider restoration

The shutdown continues.

Omid Farhang Jan 6

How years of standard medication led to a 14.2 HbA1c and silent nutrient deficiencies. 🧪

A personal and scientific exploration of "nutrient robbers", specifically how B12, Magnesium, Chromium, and Iron levels impact metabolic recovery and mitochondrial function.

The Hidden Depletion: My Journey from 14.2 A1c to Metabolic Recovery

How years of standard medications for blood pressure and diabetes led to silent nutrient deficiencies, and how I reclaimed my health through research and supplementation.

Show thread

Omid Farhang Jan 2

Covering:

✅ The Psychological Shift: Outcomes over Output.
✅ Phase 0: Legal foundations (IP, Vesting, Incorporation).
✅ Ruthless Validation: Finding the "Pain Threshold."
✅ The MVP Cut-Line: Why your senior skills are a liability in Week 3.
✅ Scaling Leadership: Treating communication like an API.

This post also serves as a roadmap through my technical catalog from 2024 and 2025, from API design to the ethics of legacy code.

Omid Farhang Jan 2

For the builders in the room: I’ve put together a "Technical Founder Execution Playbook." 🛠️

As senior engineers, we often over-engineer the solution and under-validate the problem. This guide is about closing that gap. It covers the gritty details: legal hurdles, ruthless scoping, and maintaining engineering hygiene without slowing down.

Check it out: https://g.omid.dev/3jHLgA6

#SelfHosted #Jupyter #SoftwareArchitecture #Startup #DevLife

The Engineer’s Dilemma: Building a Startup When You Only Want to Code

The definitive execution playbook for senior developers transitioning to technical founders. Master validation, legal foundations, ruthless MVP scoping, and scaling leadership.

Omid Farhang Jan 1

The Circadian Code: Why Your Code Quality Depends on Your Light Exposure.

Your brain is the most critical piece of infrastructure in your stack. I wrote about how to optimize your biological clock for better engineering performance. From morning light protocols to managing the 3 PM slump.

The Circadian Code: Why Your Code Quality Depends on Your Light Exposure

As developers, we often treat our bodies like hardware that just needs caffeine to keep running. We pull late-night sessions, work in dimly lit rooms, and stare at blue-light-emitting screens for 12 hours a day. We optimize our CI/CD pipelines, our database queries, and our bundle sizes, but we often ignore the most critical piece of infrastructure in our stack: our own biology. Our brains aren’t just processors; they are biological organs governed by a 24-hour internal clock known as the circadian rhythm. This rhythm dictates everything from our core body temperature to our hormone production, and most importantly for us, our cognitive performance.

Omid Farhang Jan 1

Hunting ghosts in vintage circuits. 🛠️

Intermittent faults are the hardest to find because they do not show up on static tests. I explored the systematic methodology for finding them, from thermal cycling to mechanical tap tests.

I also look at how these hardware techniques parallel modern software practices like load testing and distributed tracing.

Read the full guide: https://g.omid.dev/RYmfYJD

#Electronics #VintageTech #Engineering #Troubleshooting #Repair

The Ghost in the Machine: Troubleshooting Intermittent Faults in Vintage Circuits

There is nothing more frustrating than a device that works perfectly until you try to show someone else. In the world of vintage electronics, these “intermittent faults” are the ultimate test of an engineer’s patience and methodology. Unlike a blown fuse or a charred resistor, an intermittent fault is a ghost. It might be a cold solder joint that only fails when the chassis expands from heat, or a silver-mica capacitor that only leaks under specific humidity levels. These are the problems that don’t show up on a static multimeter test. They require a dynamic, almost adversarial approach to troubleshooting.

Omid Farhang Jan 1

Migrating from React to Angular: A "Ship of Theseus" case study.

We replaced a core FinTech application piece by piece while it was still in production. By moving to an opinionated platform, we improved governance and delivery speed. Read about our strategy and the Strangler Fig pattern: https://g.omid.dev/RiTgV8T

#Angular #React #WebDev #Architecture #FinTech

The 'Ship of Theseus' Migration: Why We Swapped React for Angular in Production

In the software world, the “Ship of Theseus” paradox is a daily reality. We replace parts of a system until, eventually, none of the original code remains. But usually, the industry moves toward the “shiny new thing.” At work, we did something that might sound like heresy to some: we migrated our core legacy React applications to Angular. This wasn’t a decision made out of fanboyism. It was a strategic move driven by the need for governance, stability, and long-term maintainability in a high-stakes FinTech environment. In this post, I’ll break down the architectural “why” and the pragmatic “how” of moving against the grain.

Omid Farhang Jan 1

Building a Personal Knowledge Engine with Jupyter and Local LLMs.

Move beyond simple prompt engineering. By running models locally and using Jupyter as a workbench, you get executable reasoning and total privacy. No more copy-pasting into cloud interfaces.

Full guide here: https://g.omid.dev/anqnyVS

#AI #Jupyter #LLM #SelfHosted #Productivity

Beyond Prompt Engineering: Building a Personal Knowledge Engine with Jupyter and Local LLMs

We’ve all used ChatGPT to write a function or debug a regex. But that’s just the tip of the iceberg. The real power of Large Language Models (LLMs) isn’t in the “chat”—it’s in the integration. As I explored in my 2025 series on Jupyter and AI, the real value of these tools comes when they are part of a structured thinking process. By combining the interactive execution of Jupyter Notebooks with the reasoning power of Local LLMs, we can build something much more powerful: a Personal Knowledge Engine.

Omid Farhang Jan 1

Why rewriting from scratch is often a mistake.

I wrote about the ethics of legacy code and the concept of Chesterton's Fence in software. We should respect the bedrock of the systems that actually work instead of dismissing them as trash.

Read the full post: https://g.omid.dev/deeZf3I

#LegacyCode #Refactoring #SoftwareEngineering #Programming

The Ethics of Legacy Code: Why 'Rewriting from Scratch' is Often a Failure of Empathy

Every developer has been there: you inherit a codebase that looks like a bowl of spaghetti, and your first instinct is to say, “We need to rewrite this.” You see the outdated libraries, the inconsistent naming conventions, and the lack of unit tests, and you think, “I could do this so much better from scratch.” But a rewrite is rarely just a technical decision. It’s a social and ethical one. Legacy code is code that is working. It’s code that is paying the bills, processing the transactions, and serving the users. When we dismiss it as “trash,” we are dismissing the context, the constraints, and the hard work of the engineers who came before us.

Website	https://omid.dev
GitHub	https://github.com/omidfarhang
LinkedIn	https://linkedin.com/in/omidfarhang
Bluesky	https://bsky.app/profile/omid.dev