Harjobandeep Singh

We are entering the last quarter of this year, when we can accomplish some improvements for this year.

On Dec 31st, we will check whether the quarter has been successful and whether the whole year was productive in general.

I've been the sole developer at a startup for close to two years now. No code reviews, no one to ask when something breaks at midnight, no second opinion on architecture decisions.

The hardest part wasn't the coding itself. It was making decisions with no feedback loop. You ship something, it either works or it doesn't, and there's nobody to tell you if you did it the right way or just the way that happened to not break.

I've started keeping notes on every major technical decision I make what I chose, what I considered, and why. It's the closest thing to a code review I've found when you're solo.

Curious how other solo devs or tiny-team builders handle this. Do you just get used to it, or did you find something that actually helps?

switched our basic support templates to AI-generated drafts that our team edits before sending.

first replies got faster, but now users reply back way more often because the messages sound so personal and
conversational. instead of a quick issue resolution, it turns into a whole back-and-forth discussion.

Anyone else notice their team getting busier after introducing AI drafts instead of standard templates?