We tell ourselves we're optimizing. What we're really doing is leaving fingerprints on silicon.
You know the lie.
It starts in the most reasonable way possible. You have a problem that is objectively stupid and therefore must be solved.
"The fern is dying."
"The light switch is too far."
"The mailbox doesn't tell me when there's mail."
And you, being a person who knows what an ESP32 is, think: I can automate that.
This is how it begins. Every time. A clean, utilitarian, defensible justification for ordering another dev board you absolutely do not need.
I have a drawer full of these justifications. None of them ended as automation.
Phase 1: The Automation Delusion
The automation phase is pure engineer brain. It's elegant. It's logical. It's a lie.
You open Arduino IDE — or PlatformIO if you've seen the light — and you write the most honest code you'll ever write in the project:
Beautiful. Simple. Utilitarian. You could put this on a resume.
You wire up an ESP32, a capacitive soil sensor, a tiny pump. You flash it. It works. For exactly 47 minutes. Then the sensor corrodes, the pump clogs, the ESP32 decides it no longer likes your Wi-Fi password, and your fern is somehow more dead than before.
This is the first lesson hardware teaches you that software never will: Hardware doesn't care about your intentions. It cares about physics.
Your code can be perfect. Your solder joint can still be cold. Your 3.3V rail can still sag when the pump kicks on and brown-out the whole board. Your "low power deep sleep" is pulling 80mA because you left the power LED on like an amateur.
Software forgives. Hardware remembers.
And yet, we stay. Why?
Because somewhere between the third time you re-solder that header and the first time your janky prototype actually waters the plant by itself, something shifts.
You stop caring about whether the fern lives.
Phase 2: The Creep
This is the phase no one talks about on YouTube tutorials. The scope creep that isn't about features. It's about feel.
You got it to water the plant. Automation: complete. You should be done.
But the bare PCB on the soil looks sad. So you design a little enclosure. Just a simple box in Fusion 360. 30 minutes, tops.
Four hours later you are debating 0.2mm vs 0.16mm layer height, whether matte black PETG says "I am a serious adult who waters plants" and if you should add a tiny embossed fern leaf on the lid because... why not?
Then you think: the LED is too harsh. It should fade in slowly, like a sunrise, when it waters. Not just blink. Breathe.
So you rewrite digitalWrite() into a PWM fade loop with an ease-in-out curve you copied from a frontend animation library. For a plant. A plant does not care about easing functions.
Then you add an OLED. Just to show moisture percentage. Then you add a little animation of a happy fern when moisture is good and a droopy fern when it's not. You spend a whole evening drawing 8x8 pixel art ferns.
You came to automate. You stayed to anthropomorphize.
This is the moment every DIY project crosses the line from engineering into art. You are no longer solving the problem. You are expressing how you feel about the problem.
Automation asks: "Does it work?"
Art asks: "Does it feel like me?"
Phase 3: Why The ESP32 Made Us All Artists
The old Arduino Uno was honest. It had 32KB of flash. It could barely hold your code and a grudge. It kept you humble. You built what you needed because you had to.
The ESP32-S3 is a dangerous thing. It's a $7 supercomputer that pretends to be a microcontroller. Dual core 240MHz, Wi-Fi, Bluetooth, 8MB PSRAM, camera interface, Touch, Hall sensor, stuff you'll never use but love knowing is there.
It has so much headroom that you stop asking "Can I do this?" and start asking "What if I did this beautifully?"
That's why an ESP32 project never ends. There's always one more peripheral. One more sensor. One more ridiculous idea that the chip can absolutely handle, even if you can't.
You start with a mailbox sensor. You end with a mailbox that sends you a Telegram message with a haiku about the mailman, logs the temperature and humidity inside the box, and plays the Metal Gear Solid alert sound when junk mail arrives.
Is that automation? No. Is that necessary? Absolutely not. Is it yours? Completely.
We used to buy objects that were made for us. Now, for the first time in industrial history, normal people can make objects that are like us. Flawed, over-engineered, weirdly sentimental, with inside jokes baked into the firmware.
My house is full of objects that don't make sense to anyone else. A light that turns warm when it rains because I like rainy days. A switch that needs to be double-tapped because single taps are too impatient. A little desktop friend that just sits there and blinks at me when my build fails.
None of these automate anything. All of them make the place feel inhabited.
The Real Circuit
Here's what I actually think after a decade of burning my fingers with a soldering iron that was definitely off:
We tell ourselves we are building smart homes, but we are building haunted homes. Not haunted by ghosts, but haunted by our own attention.
Every time you choose a warm white LED over a cool white one, every time you tune a sensor threshold by hand, every time you add a silly little animation that only you will ever see — you are leaving a fingerprint in the machine.
The big tech companies are trying to make devices that work for everyone. We are making devices that work for one person. That's not a bug. That's the entire point.
Automation is the excuse we give our partners and our wallets. Art is the reason we actually do it at 1 AM on a Tuesday.
So the next time your "simple automatic plant waterer" has a custom PCB, a web dashboard you designed from scratch, and a name — you didn't fail at keeping scope small.
You succeeded at making something human.
You started as an engineer trying to save a fern. You ended as an artist who gave a fern a little robot guardian that breathes.
And honestly? The fern is still going to die. But what a way to go.
If this hit, you'll want what's on my workbench:
I turn these late-night spirals into buildable field kits. No cloud, no subscriptions, just hardware that feels like yours.
1. Hardware Signals Field Pack — ESP32 & Sub-GHz RF Research Lab
The lab I wish I had when I started. ESP32-S3 + CC1101 BOM, portable listening platform, real-world RF capture workflows, and the glue scripts so you stop re-writing the same Python parser for the 100th time. Build a defensive tool you can actually carry.
→ numbpilled.gumroad.com/l/hardwaresignals
2. ESP32 Phantom Networks — Portable Mesh & Offline Infrastructure
For when your art wants to leave the house. How to get ESP32s talking to each other with no router, no cloud, no ISP — wardriving instincts, pocket mesh, offline messaging. The foundation for every "what if it worked off-grid?" project.
→ numbpilled.gumroad.com/l/esp32phantom
Both live on numbpilled.gumroad.com — grab the one that matches the haunting you're building.
Clap 50x if your "quick weekend project" is now 6 months old and has a name. I see you.
Top comments (0)