I tested #codespeak and I find it is probably a bad example of development from the start.
1. needs a browser to get "authentication". Auth for what? Well, to run a build job locally.
2. Needs a subscription. For what? We don't know. It doesn't say.
3. Don't worry, all "new". Actually it is public.
4. The build process wants to call build.codespeak.dev:50053 . Why? We don't know :) All magic AI.
Summary: The tool failed.
Don't make these mistakes.
a) Release later. Use your brain beforehand.
b) And do not release a specification tool that doesn't have a specification itself.
The fact that you are one of the authors of #Kotlin does not mean you are so exceptional that people don't assess your work. On the contrary. ;)
https://codespeak.dev/blog/greenfield-project-tutorial-20260209
p.s.: I understand that this is just a queue, and no actual local builds remain. Which is another design flaw.




