Erroroverflow Blogs
About Erroroverflow
Who writes this, what gets covered, and how it is tested

Erroroverflow is a personal engineering blog about embedded systems and React Native. Every post starts from a real problem — flashing firmware without the vendor IDE, comparing native module frameworks, building an RTOS from scratch — and follows the trail it left behind: setup, code, measurements, dead ends, and the primary documentation that explains what is actually happening.

What you will find here

  • Microcontroller programming and flashing: AVR, SPI, programmers, and toolchains.
  • RTOS and scheduler internals, written while implementing them from scratch.
  • React Native internals: the New Architecture, JSI, TurboModules, and Nitro Modules.
  • Debugging notes on tools that behave differently than the documentation claims.

How examples are tested

Commands and code samples are run locally before they are published. Sketches are compiled and flashed to real hardware where possible, benchmark numbers are linked to the source that produced them, and code excerpts are taken from the actual files rather than rewritten from memory. When something could not be verified on hardware, the post says so.

Sources and corrections

Claims about chips, SDKs, and tools link to datasheets, official documentation, or source repositories. When a number comes from someone else's work, it is credited and linked. If you spot a mistake, open an issue on GitHub — posts show an “Updated” date when they are revised, and corrections are folded into the text instead of left in an errata list.

Get in touch

Erroroverflow is written by the developer behind github.com/Manith-2001 . GitHub is the fastest way to reach me, whether it is a correction, a question about a post, or a topic suggestion.