georgeashworth

Yes, I have used that workflow to fix a tricky data corruption issue earlier this week.

A buggy feature left DB in invalid state, I described the issue to Claude + Postgres MCP to both query the DB to analyze and then generate SQL scripts to fix, and validation and rollback scripts. Easy enough to do without the tooling... but with the tooling, it took probably a quarter or less of the time.

What kind of cash comp are you looking for? I assume $100-200k leadership roles at early startups should be pretty trivial for you to land with your experience, but maybe that's a token salary to you?

> However, I am too embarrassed of how ragtag the device currently is to make more prototypes and sell them (literally held together by tape, string, and a prayer).

I work in software, so take this with the requisite grain of salt, but my first reaction to your post is:

Go ahead and start selling your ragtag device. Slap together a basic website + contact form + checkout page (figuratively held together by tape, string, and a prayer). Start posting about your device wherever interested parties gather on the internet. Be honest and transparent about how early you are in development and ask for feedback.

Even if nothing is sellable, you can at least gather contact info from interested parties.

Even if your device is total unsellable garbage and you sell 0 copies, you will learn so much from this process and the conversations with potential customers, and you can use that to steer your future development direction.

Rather than expressing frustration at the less experienced developers you are working with... as a hiring manager I would prefer to hear something more constructive, like that you are able to understand the common pitfalls a team of less experienced developers are likely to run into and proactively lead/wrangle/herd them towards success.

I use GitHub Copilot IntelliJ plugin every day and would not consider going back to the pre-LLM state of affairs.

I don't use it to generate entire classes or tests, because it doesn't work well for that, and definitely not for big refactors, but it works well as a "super autocomplete" for 1-3 lines of code at a time.

Does this type of occupancy tracking work accurately outdoors? I'm assuming it would be difficult because signals would travel further. (My startup needs occupancy tracking for tennis courts.)

Maybe I could mount a BT device at a corner of the outdoor space and use its signal strength as the threshold value.

Citation needed