Forge36

I love my e-bike. It sounds like you bought an electric dirt-bike. I'm not going to call you an idiot: the market is confusing and not well regulated, manufacturers are taking advantage of this. There have been some improvements with regulation to promote safety (both for you, as the unaware rider and for others). It's possible where you live it's not legal to take your new e-bike on the road without a motorcycle license OR on bike paths. Be safe, double check your local laws. If it's not legal: return it.

Wi-Fi was never unreliable. The devices that used WiFi were much worse to work with and setup.

Having switched to zigbee devices recently I regret trying to start with WiFi. While I'm not sure how it looks under the hood, adding devices with home assistant was miles easier.

Can you elaborate?

Location and time

That's known as Transmitter Hunting (aka Fox Hunting).

It's a fundamental flaw of most wireless communication. Are you referring to something more specific?

There something amazing about that. Thanks for pointing it out!

On a recent project we joked "developers can't read". Occasionally we'd ask for help and be pointed to the docs "I can't read".

I suspect there's two big parts to this:

1. Users expect batteries included and that everything "just works" the first time.

2. The language you used differs match your audience. E.g they search "gray" and find no results, however you've spelt it "grey"

Bikes typically have a weight rating. Mine has 150lbs of cargo capacity (is a cargo bike).

Context switching like that is exhausting

For me: Will this task take 30 seconds or 3 minutes. With good planning I've been able to step away and come back. Sometimes it decides to prompt me within 5 seconds for permissions. Sometimes it runs for 15 minutes.

The output is still small and I can review it. I can switch tasks, however if it's my primary effort for the day I don't like stepping away for an hour to do something else.

I'm still writing code. I'm doing it to solve a problem, there's more to writing code than than typing. Recently AI massively simplified "getting started", and all of the tips here are applicable to working well on a team.

My recent experience: I'm porting an app to Mac. It's been in my backlog for ~2 years. With Claude I had a functional prototype in under a day getting the major behavior implemented. I spent the next two weeks refactoring the original app to share as much logic as possible. The first two days was lots of fun. The refactoring was also something I wanted to flush out unit tests, still enjoyable.

The worst part was debugging really bugs introduced to my code from 5 years ago. My functions had naming issues describing the behavior wrong, confusing Claude, that I needed to re-understand to add new features.

Parts of coding are frustrating. Using AI is frustrating for different reasons.

The most frustrating part was rebasing with git to create a sensible history (which I've had to do without AI in the past), reviewing the sheer volume of changes (14k lines) and then deciding "do I want my name on this" which involved cleaning up all the linter warnings I'd self imposed on myself.

Menards has done this since at least 2012