Writing

LoRaWAN is not just a radio protocol. It is a full network architecture with device classes, join procedures, and tradeoffs that only become visible when you deploy it in the real world.

In 2016, during a turbulent time in Turkey, I joined a startup building a smart city from the ground up. No proven network server existed. So I wrote one.

Most protocol documentation is written by engineers for engineers. Here is the order of questions to answer before you go anywhere near the physical layer.

Building a hardware product without an electronics background is not the problem. Here is what good technical leadership actually looks like.

Getting a prototype to work on your desk is the easy part. Here is what actually separates a prototype from a product that survives in the field.

It is not bad engineering that kills hardware startups. It is starting to build before you know what you are building.

Most people treat wireless communication like a casual conversation. But distance costs energy, bandwidth is shared, and structure is what makes any of it reliable.