Image 1 — How we turned a fun idea into a physical anti-doomscrolling key in 2 months
Image 2 — How we turned a fun idea into a physical anti-doomscrolling key in 2 months
Image 3 — How we turned a fun idea into a physical anti-doomscrolling key in 2 months
Image 4 — How we turned a fun idea into a physical anti-doomscrolling key in 2 months
Image 5 — How we turned a fun idea into a physical anti-doomscrolling key in 2 months

How we turned a fun idea into a physical anti-doomscrolling key in 2 months

About 2 months ago we had a funny idea: what if we "vibe" some small devices and try to ship them in just one week per product. The brief was simple, which was to build something fun and useful, apply the vibe coding philosophy, keep the hardware simple, and ship something.

We started with a pain point everyone on the team had felt, which was doomscrolling. Not just the productivity drag, but the slow theft of quality time. The hour with your kid became 45 minutes. The dinner you scrolled through. The Sunday afternoon that disappeared into a feed. So we built a small physical key that locks apps on your phone, and two months later we have a finished product. Here's what we learned between version 1 and the final product.

Version 1: The first prototype, 3 days from blank screen

We had a working prototype three days in. A small object, 3D printed in an afternoon, with an NFC tag inside. A companion app vibe-coded in a couple of sittings. Tap your phone to the Key to lock chosen apps, tap again to unlock them. The mechanism worked. Physical key, digital lock. Clean. It also failed almost immediately, and the problem was symmetry. 

Locking and unlocking both required the Key, which meant we had to carry it everywhere, which meant it was always within reach, which meant unlocking was trivial. If the Key is in your pocket while you're trying not to scroll, the lock is performative, because you'll tap it the moment willpower fails. We'd built friction in name only.

Version 2: Asymmetric mechanics

We rewrote the app. Locking became one tap in the app with no Key required, and the Key was only needed to unlock. This changed everything, because now you could leave the Key at home and walk out the door with your phone locked, and you couldn't unlock the apps you'd chosen to lock until you came back. The distance from the Key was the friction, and suddenly the placement of the Key was the design parameter. 

  • On your desk: trivial unlock. 
  • In a drawer in another room: moderate friction. 
  • At home while you're at the office: genuine friction.

 

This is when the product clicked.

The session problem

Asymmetric mechanics fixed the unlock friction, but created a new problem. Once you unlocked, the apps stayed unlocked indefinitely until you decided to lock them again. Which meant the moment you tapped the Key, all the discipline disappeared. You'd unlock for "just a quick check," look up two hours later, and the Key was still sitting where you left it.

So we made the unlock time-bounded. Tap the Key, get a session (30 minutes, or whatever you set). Session ends, apps lock again automatically. Want more time? Tap the Key again.

This was the version we'd been looking for. Every use becomes a deliberate choice, not just the first unlock, but every extension. The friction doesn't fade after the first tap. It refreshes.

Picking which apps to lock was also tedious at first. You'd open Settings, hunt through your app list, toggle each one, and by the time you finished, the urge to scroll had passed and you'd lost the moment. So we grouped apps automatically into categories like Social, Games, Shopping, News, and one tap locks an entire category. The lock decision became as fast as the unlock should be slow.

Where AI fits

At this point the device worked. Locks were easy, unlocks were hard, sessions were time-bounded, and we had a finished product on the bench. We all loved it.

Then we asked the obvious question, which was how this fits with the rest of the Autonomous ecosystem. We already make AI companions for thinking work, so could the Key participate? We integrated the Key feature into the Autonomous Thinking Devices app, alongside our other AI companions, and the AI in the app (called Autonomous Intelligence) observes the lock and unlock patterns and offers small commentary.

There's an important constraint here: iOS Family Controls returns anonymous tokens, so the AI doesn't know which app you locked, doesn't know how many times you tried to open something. It only sees session timestamps, durations, and streaks. That constraint shaped the voice, because the AI isn't a coach and doesn't tell you what to do. It notices small things, in a warm baseline with dry humor and no exclamation marks. 

Things like "3:12am? I noticed." Or "Seven days, each session under 20 minutes. Something's working." Or "Tapped at 9, tapped again at 9:32, tapped again at 9:48. We've all been there." Or "Last session lasted 4 minutes. That's a record." The same things a good friend says when they've been paying attention.

The product, two months later

The final product is a small physical key called Autonomous Key, which is symbolic and easy to understand. There's a feature in the Autonomous Thinking Devices app where you pick the apps to lock and the session duration you want for each unlock. The selected apps stay locked by default. Unlocking requires the Key paired with your phone, and unlocks last for the session duration you chose. When the session ends, apps lock again. Tap the Key again for another session.

Autonomous Intelligence lives in the same app, noticing your patterns and saying small honest things when they happen. The whole product is built around one principle, which is to make locking as easy as possible and make unlocking as hard as you choose. The goal isn't to win against your phone, it's to give you the gap of time that lets you decide.

Questions for the community
We are officially launching the production version of the Autonomous Key this week. I would love to get your feedback on this feature set:

  • For those who cannot commit to a full dumbphone due to critical work apps, does this "always locked except for timed hardware sessions" feature solve your main frustration?
  • Does forcing yourself to physically get up and touch an object to extend screen time sound more practical than standard digital app blockers?

I work on the product, but I am genuinely here to learn from your daily setups. I have 5 extra units at the workshop right now. I would love to ship them for free to anyone in the comments who shares the most detailed insight about their current routines and struggles.

u/deebuildsthings — 12 hours ago

How we designed our WorkPods without pouring a concrete slab

I keep getting asked how we engineered the Autonomous WorkPod to handle the core challenges of a backyard ADU: wall acoustics, structural loading, and the perpetual headache of ground settlement and frost heaves.

An ADU wall has to do four things at once: hold the structure up, keep sound out, keep heat in (or out), and survive every season. Here is the full engineering breakdown of how we solved these constraints, one layer and one footing at a time.

1. The Wall Assembly: 6 Layers of Acoustic Impedance

Instead of using exotic materials, our acoustic strategy relies on shifting mechanical impedances. Sound loses energy every time it crosses a transition between different material layers. Every WorkPod wall uses a specific 6-layer stack (from outside to inside):

  1. Metal siding (exterior cladding, weather and impact)
  2. Breathable membrane / housewrap (weather barrier)
  3. Multi-layer plywood (exterior sheathing)
  4. Honeycomb board (insulation core)
  5. Structural frame (solid timber or steel depending on the model)
  6. Multi-layer plywood (interior sheathing)

Why Honeycomb instead of Foam or Fiberglass?

You are really insulating with air. The material just holds it still. Honeycomb is an efficient scaffold per unit weight. Same cell structure damps sound between the plywood layers. Light, dimensionally stable, recyclable. Three jobs, one layer.

2. Structural Framing & Load Distribution

The structural frame inside every WorkPod wall depends entirely on the model you choose:

  • Solid Structural Timber Variant: Engineered wood members, dimensionally stable, factory-cut to tolerance.
  • Steel Frame Variant: Welded structural steel, featuring a slimmer profile and higher load rating for taller spans.

Both variants ship as flat-packed wall panels and bolt together on-site. Panels lock with M6 bolts at every joint. Class 8.8 structural grade. Torqued to 9 N·m, each joint achieves ~7.5 kN clamping force, well inside the bolt's tensile limit.

Two people, one Allen wrench. No specialty tools.

The wall consists of 10 prefab modules. Each module is bonded as one rigid block: 5 vertical 2×4 Southern Pine studs, 2 horizontal 2×4 plates (top + bottom), and 2 multi-layer plywood faces. The WorkPod weighs 2.9 tons total, but the structural walls only carry the overhead roof load, about 600 kg (1,300 lbs). Divide that across 10 modules: ~130 lbs per module. Less than 1% utilization of the framing's structural capacity. The structure isn't fighting the load. It's barely noticing it.

Windows are where sound reduction fails fastest. We over-engineered ours: 5/16" tempered glass (4-5× stronger than standard glass), aluminum frame for thermal break.

3. Electrical & Airflow Management

An ADU electrical system shouldn't force you to rewire your main house. The WorkPod operates on a single cable principle: one outdoor cable runs from your house to the pod, utilizing two connectors at each end. This allows you to stay entirely inside your existing house panel capacity, meaning no second utility meter, no upgraded panel, and no city permits.

Inside the pod, the pre-wired circuit powers a highly optimized workspace load:

  • 3 outlets
  • 1 ceiling light
  • 1 ventilator

A typical workday load, laptop + monitor + LED lighting + ventilator, etc… The pod is rated for up to 2,750W (25A), enough headroom to add a portable AC or space heater on the same circuit. The cable is intentionally oversized for the transient spikes those units pull on startup.

The HVAC and Ventilation Strategy:

Because the walls are tightly sealed for maximum soundproofing, airflow cannot be an afterthought. Every WorkPod features an integrated, active exhaust ventilation fan that runs silently to continuously exhaust stale air and pull fresh oxygen in, preventing the slow buildup of CO2 that causes 3 PM fatigue.

We intentionally don't ship a built-in HVAC because climate varies by zip code (a built-in AC sized for Texas overbuilds for Oregon). Instead, every pod provides dedicated clearance space for a portable climate unit and comes with a 5.9" exhaust port pre-cut directly through the wall. This allows users to buy a standard $300–600 portable AC/heater that fits their local weather, routing the exhaust perfectly without drilling into the structural panels.

4. Foundation Engineering: Ditching the Concrete Slab

A concrete slab requires permits in most cities, takes weeks to cure, tears up your yard, and permanently welds the pod to one spot. We don't do that.

Instead, we designed an adjustable point foundation system to handle sloped lots (up to ~5 degrees) and natural ground movement. Backyard soil doesn't stay put. It settles and heaves over time due to drainage and frost.

Our solution relies on 6 reinforced concrete pedestals (one under each foot):

  • Geometry: Each pedestal is a truncated pyramid (wide square base, narrower square top, four sloped sides). The wide base increases ground contact area, lowering pressure so the subgrade barely loads up under the 2.9-ton total mass.
  • The Load Path: An M27 hex bolt is welded into a steel frame cast directly into the concrete pedestal. Aligned vertically with the gravity load axis. A long nut spreads load over more threads, ensuring it doesn't back off under freeze-thaw cycles.
  • Leveling: Happens at each foot via a tapered roller bearing welded to the bolt. It never rotates in service. The taper is there to spread load down the cone instead of pinning it to a single point.

The pedestals come 29.5" to 48.5" tall so you can match your backyard's grade. Fine-tuning is done by turning the bolt with a wrench to adjust the thread height of each corner independently. If frost heaves the ground in winter, you wind it back down in spring. If a corner settles, you wind it back up. No heavy lifting, no digging, entirely reversible.

—-

Every backyard presents a different combination of soil, slope, and climate. By taking these baseline structural constraints seriously, we’ve built an ADU that acts like a highly observable, adaptable machine.

We’ve already been shipping these units integrated with solar panels. Right now, our engineering team is tackling the integration of pre-wired, pre-plumbed restroom and kitchen modules. The ultimate goal? To ship a fully code-compliant, functional house that can be ordered online, delivered flat-packed, and fully assembled to live in within a single day.

Happy to answer any questions about the structural loads, fastening specs, or foundation physics in the comments!

u/deebuildsthings — 6 days ago

Built a workstation for local AI. Flagging the mistake i almost made

PSA from someone who almost made an expensive mistake. I wanted to run 2 GPUs for local AI inference. Initial plan was to slot them into a Z790 board because I already had one. Started reading PCIe lane docs and realized the second slot would drop to x8 or x4 depending on the board, which kills tensor parallel performance.

Went to a workstation board instead. ASUS Pro WS W790-ACE, LGA 4677 socket, full Gen5 x16 to both slots. CPU is Xeon W5-3425, picked entirely for lanes and memory channels, not cores. 12 cores is plenty for inference workloads.

Things I didn't expect that I'd warn anyone about.

The Xeon doesn't ship with a cooler. The LGA 4677 socket is physically different from AM5 and LGA 1700, so none of your spare coolers fit. Had to buy a tower specific to the socket.

DDR5 ECC is more expensive than regular DDR5 but the W790 platform expects it. Don't try to save money here, you'll fight stability instead.

Riser cables. Get good Gen5 ones. A cheap riser will give you intermittent crashes that look like a GPU problem but are actually a signal integrity problem. Took me a day and a half to figure that out.

The 12V-2x6 GPU power connector needs to be fully seated. Push until it clicks, then tug to verify. Every melted connector horror story I've read came down to a seating issue.

Cooling matters more than on a single GPU build. Two cards stacked means the inner card cooks unless you've got proper airflow. 4 fans minimum, 2 intake at the front, 2 exhaust at the back, all PWM.

This is a niche use case but if anyone's thinking about dual GPU for any reason, AI or otherwise, the workstation platform decision is the one that matters most. Everything else can be tuned. Lane count cannot.

u/deebuildsthings — 29 days ago
▲ 73 r/homelab

Put 7 sensors in the room I work from. Three months of data and a couple readings I still can't explain

I work out of a prefab unit in my backyard. Small standalone room, HVAC, power, that's it. Been in there about a year. Got tired of guessing why some days I'm locked in and other days I'm useless by 2pm. So in January I decided to just instrument the room and log everything. Ended up with CO2, air quality (mostly PM2.5), an mmWave presence sensor, smoke and gas combo, lux, a calibrated dB mic and a seismic vibration sensor (overkill, I know, had one in a drawer from another project). All piped into ESPHome, Influx, Grafana.

3 months in, some of it lines up with what I expected and some really doesn't:

  • The 3pm crash I always blamed on lunch is CO2. Sits around 600 in the morning, climbs past 1,300 by mid afternoon if I keep the door shut. Crack the door for 10 min and it drops to around 800. I can feel the difference inside 20 minutes. Didn't believe it until I'd reproduced it 5 or 6 times
  • Bad focus days correlate almost 1 to 1 with the noise floor. Not loud noise, the baseline. Rough days run 6 to 8 dB above good days and most of the time I can't even tell what's driving it. Neighbor's pool pump? Wind direction? No clue
  • Light is the one I'm least sure about. Lux drops hard in the afternoon as the sun angle shifts in April but I can't tell yet if that's actually doing anything to me or if I'm reading causation into a correlation. Putting a desk lamp on a smart plug to A/B it next month
  • Weird unresolved one. HVAC short cycles way more on Tuesdays. Same setpoint, similar outdoor temps. Every other day of the week is fine. Driving me a little crazy
  • The other unresolved one. Noise floor reads 4 to 6 dB higher when my upstairs neighbor's heat pump kicks on, even though I can't hear it from inside. And I focus worse during those windows. 11 weeks of data and the correlation holds, but I have no working theory on the mechanism. Acoustic coupling? Vibration through the slab? Open to ideas

What surprised me most is how much the room itself was running the show. I've had a Whoop for a couple years and it's useful but kind of just tells me what I already feel. The room data has been more like "here's why you felt that way, dummy". What's the one environmental thing you're convinced is wrecking your focus but have no way to prove?

u/deebuildsthings — 30 days ago