"This project wouldn’t be possible at this scale without AI and think that is just fine, I do foresee that we might be entering in a golden age of Open Source development, and that every single dev out there with an idea is about to embark into this addictive code frenzy to see it become reality"

Good Development Habits:

* Commit every time a small goal is achieved
* Work incrementally in small iterations
* Build persistent context
* Split long files/functions/components into smaller ones
* Teach the AI modern patterns
* Build it and they will run them (the unit test).

"And the solution to most problems caused by an ADHD dev is just good development habits, the same ones that you should already have but that you forgot to implement because suddenly the AI goes too fast and felt that if you can “skip” coding, you could also skip on everything else."

"I have found that AI really is like a regular ADHD dev that makes mistakes, leans into assumptions, keeps repeating old patterns because that’s how it learned, gets easily sidetracked by refactors, and doesn’t know where to cut a PR so it just keeps adding to it." #AI

As you can imagine this kind of top level re-organization take time, specially when you want to keep data leaks away.

We will invite you to the closed beta as soon as we can be sure your data (even just demo data) will be safe.

Of course you are always welcome to host your own instance of Tomas, teams then make even more sense. As a company could have different teams for each area.

One more thing, and this is important:

We decided to organize the workspaces(a collection of accounts and transactions) around teams so that several users can add transactions, help in the planning and in general cooperate at the same time.

This is also useful for billing in the case of our SaaS.