RewoHub Part 1 - Third time's the charm!

To fail, to adapt, and to trying one more time.

After two failed startup attempts and a long break from the scene, the itch to work on something calling my own started to resurface. You likely know exactly what I’m talking about if you dwell on indiehackers.com. Working on something alone, perhaps as a small, passionate team. The product, something that can be useful to many and your ticket to being your own boss . Yeah, that itch is bothering me the last few weeks. I spent a couple of days figuring out what I should invest in my 1-2 hours of spare time a day. As the username suggests, I’m a software developer. My last two projects were perhaps a bit ambitious, beginners mistake I suppose. This time I want to keep it small, so naturally, I planned to create a WebApp helping teams of software people improve their team’s/organization’s performance by providing an AI-powered agile coach. The idea was to learn the current way the team/organization works. Comparing it against a pre-trained model. Point out bottlenecks of the current mode of work. Not a really small project, especially considering the 1-2 hours/day time constraint. So I’m shelving it for now. An ML model representation of Kent Beck’s and Uncle Bob’s teachings will have to wait.

The idea for the WebApp came from my organization failing to implement a proper agile workflow. Neither completely adopting it, nor throwing it out of the windows, losing a lot of talents in the process. I like to work on things, fixing my own issues. I’m my own’s most loyal customer after all. If nobody would use my product at least I would solve my own issue.

During a retrospective half of my brain was trying to figure out an idea for a small side project which I could launch rather fast. The other one was fighting a certain kanban board we were using to collect things either holding us back or empowering us. If only this damn board would cooperate. Don’t get me wrong, the board was not fundamentally bad. A lot of small, infuriating UX issues rather than big, crippling ones. When I want to edit my answer I would have to resize the TextArea to read my wall of text, since it would resize to display only 2 lines of my text. Typical HTML TextArea behavior but not so nice to use. Also, why the heck would I need to click a button first in order to change my text? We are using this board for quite some time now and those problems persisted in driving me mad and that was an issue. An issue which I would like to fix. Looks like I found myself a sweet little side-project that can be of use to somebody. Perhaps proposing to my team to try it out and provide feedback. I like it. A chance to put my money where my mouths at. Let’s start with a bit more planning and a bit of initial coding..