five9s's comments

On: Show HN: Track the AI-generated code in your repo

[five9s]

Could see this becoming really helpful for benchmarking code quality and speed.

On: Show HN: Tududi – a minimal task manager you can self-host

[five9s]

Nice app. Have you thought about using AI to automatically organize and group ideas?

[cvicpp123 → five9s]

Of course, this is the goal, A keep-it-out-of-the-way application.

On: Show HN: 10x the output of your coding agent

[five9s]

Very cool. How do you get your context into the IDE? It is mostly a repo scan that helps the agents?

[jellyotsiro → five9s]

indexing both repos and web!

On: Ask HN: Why are only CEOs building products at record speeds

[five9s]

I think you mean "founders"; it's a bit disingenuous to call yourself a CEO of a company with less then 5 people IMO. Founders are moving faster then ever due to the ability to embrace AI-based development.

On: Velocity Coding

[five9s]

I want to be part of the cosmic assembly line of pure creation.

[benzguo → five9s]

hop on board all are welcome even product managers and designers and 10yr old children

On: Ask HN: Startup shutting down, should we open source?

[five9s]

I think it could be a nice emotional ending to the journey if that's where you are. At least it's 'out there' in the world and you can move on. I'll be a one time effort to get it out there, but then can be community supported.

On: Show HN: Zenta – Mindfulness for Terminal Users

[five9s]

Pretty cool. Have you thought about auto triggering a need for a breath at certain intervals?

[ihiep → five9s]

The best breath is the one you notice, not the one you're told to take.

On: Show HN: An accurate implementation of Pomodoro Technique

[five9s]

Love the pomodoro technique to focus, but why do you think that a simple timer isn't enough?

[ity75303 → five9s]

The timer is one part of it, and indeed, a simple kitchen timer is all you really need. But most of the Technique is about tracking your work through backlogs, estimating it, and (most importantly) analyzing it retrospectively: https://archive.org/details/ThePomodoroTechnique/ThePomodoro... It's like a personal mini-Scrum with planning and retrospectives. Flowkeeper mainly automates that "paperwork" part.

Also, Pomodoro Technique requires discipline, and most of the simple timers don't help you much. For example, if you just cancel a pomodoro (or a short break) -- nothing happens, while in Flowkeeper it is more visible, you get an interruption recorded. There's a bunch of small things like that, which motivate the user to do Pomodoro _right_. When you do it right, it is much more efficient.

Just to be clear -- a kitchen timer and a sheet of paper is enough. I just wanted to do the _exact_ same thing for my desktop.