Technical depth over breadth
We'd rather publish one article that fully explains a topic — including its failure modes and edge cases — than ten that skim the surface. If something is hand-waved in industry literature, we say so.
About Elektro Krishna
Where electrical engineering meets rigorous, readable writing.
We publish long-form, technically-vetted articles on power systems, embedded firmware, signal processing, and the software that ties them together — written for working engineers and curious students alike.
Our story
Started at a workbench, sharpened by deadlines.
Elektro Krishna began in 2021 as a personal notebook — a place to write down the things Krishna Iyer wished someone had explained clearly when he was a junior power-systems engineer: why a particular ground-fault calculation kept producing nonsense, how to choose between an RC and a digital filter for a noisy sensor line, why a certain STM32 timer refused to generate the PWM everyone else seemed to get for free.
What started as margin-scribbles grew into a small editorial team of practicing engineers, researchers, and technical writers. Today, every article on elektrokrishna.com goes through a working professional with skin in the relevant field — somebody who has debugged the circuit, written the firmware, or modeled the system being described. We do not publish AI-generated drafts, and we do not run sponsored "what is" articles that masquerade as engineering content.
Mission & values
Three principles that shape every article.
We treat engineering writing as a craft, not content marketing. These are the standards we hold ourselves to — and the ones our readers should expect from us.
Vetted by practitioners
Every piece is reviewed by at least one working engineer with hands-on experience in the subject. Code samples are compiled. Calculations are checked. Datasheet claims are verified against the actual document.
Honest about limits
We clearly mark assumptions, cite sources, and tell you when a problem is out of scope for the article. No vague "consult a professional" closers — we name the standard, the formula, or the next thing to read.
By the numbers
A small team, a long shelf-life library.
We measure success in years, not clicks. Our most-read article from 2022 is still being cited in university course materials today.
240+
Published articles
18
Contributing engineers
9
Engineering domains covered
0
Sponsored or AI-only articles
Editorial standards
What "well-written" means at Elektro Krishna.
Before an article reaches you, it passes through five checkpoints. This is the workflow that keeps our content accurate two, five, and ten years after publication.
01
Draft by a domain author
Written by someone who has personally worked on the system being described — not outsourced to a generalist.
02
Peer technical review
A second engineer checks derivations, equations, circuit choices, and code for correctness and safety implications.
03
Reproduction & simulation
Code is compiled and run. SPICE models are simulated. Measured results are compared against the theoretical predictions in the article.
04
Editorial pass for clarity
Plain-language editing for sentence rhythm, terminology consistency, and figure quality — without dumbing down the content.
05
Annual review cycle
Every article is revisited at least once a year to update for new standards, errata, or superseded parts.
The editorial team
Engineers writing for engineers.
A handful of practitioners across power, embedded, RF, and software — plus the editors who keep the prose honest. We publish under our real names.
Krishna Iyer
Founder & Editor-in-chiefPower systems engineer by training. Spent eight years on grid-tied inverter design before turning to full-time technical writing.
Anika Menon
Lead Embedded EditorFirmware architect for industrial IoT. Reviews our MCU, RTOS, and low-level driver articles with a debugger in one hand.
Daniel Voss
Signal & Systems EditorControl systems PhD. Owns the signal processing, controls, and DSP corner of the library. Sketches Bode plots on request.
Riya Patel
Software & Tools EditorBackend engineer with a soft spot for tooling. Oversees our Python, simulation, and CAD workflow tutorials.
What you can expect
A reading experience built for working engineers.
When you open an Elektro Krishna article, here's what you'll find — and what you won't.
Real derivations, not hand-waving
When a formula matters, we show where it comes from. When an approximation is used, we say so and quantify the error.
Runnable code & schematics
Snippets compile, scripts run, and circuit diagrams are drawn from real designs — not stock templates or toy examples.
Proper citations & links
Datasheets, IEEE papers, application notes, and standards documents are linked inline — not buried in a footer block.
No fluff, no clickbait
No "you won't believe" headlines, no SEO-stuffed intros, no mid-article ad interstitials pulling you out of the problem.
Open to corrections
Found a mistake? Email us. We publish errata with timestamps at the top of the article — quietly, professionally, no defensiveness.
A long shelf life
We design articles to stay useful. Background concepts are explained once and referenced later, so old pieces remain relevant as the field evolves.
Dive into the library.
Browse over 240 articles covering power electronics, embedded systems, signal processing, and the software that ties it all together — all free, all peer-reviewed.