If you work in IoT, environmental sensing, or data systems, forest soil monitoring is one of the most technically interesting problems you'll encounter. The system you're trying to measure is extraordinarily complex, the variables are deeply interdependent, and the consequences of getting it wrong — or not monitoring at all — are significant. The Problem Space: What You're Actually Measuring Soil
There's about $400 of meat, milk, and miscellaneous condiments in my kitchen fridge at any given time. It runs 24/7, makes a quiet humming noise, and gives no indication when something's wrong until you open the door three days later and recoil. The freezer compartment is worse: a slow failure can defrost everything before you notice the puddle. I already had a TP-Link P110 smart plug on the fridg
Some time ago, I was building a chat application using AWS Websocket API gateway. Things were going smoothly. I created a WebSocket API Gateway, added $connect, $disconnect, and sendMessage/addGroup routes. From the frontend (React) side, everything was fire-and-forget. You send a message, and the onMessageHandler takes care of it 💪🏼 But then a new requirement of uploading files using S3 signed
One of the recurring challenges while building IoT systems is testing device communication, telemetry handling, MQTT flows, and event-driven architectures without constantly relying on physical hardware. To solve this problem, I recently started building a lightweight IoT Simulator CLI focused on helping developers simulate virtual devices directly from the terminal. The project is designed for de
Every device you own has a speaker and a microphone. I decided to use them for something useful. Natural disasters knock out cell towers. WiFi dies at conferences. Underground sensors need to offload data where nothing reaches. Bluetooth pairing is painful and range-limited. LoRa is great but requires hardware you don't have. Sound doesn't care about any of that. Every phone, every laptop, every e