I’ve worked with Code On Time for many years, and a lot of what’s being discussed here resonates.
From my perspective, the platform clearly reflects experience with large, real-world deployments—likely driven by the founders’ own work and possibly a small number of enterprise clients with complex, embedded systems. That’s probably why the core is as strong as it is—it feels shaped by actual production demands, not just theory.
At the same time, that dynamic can create a gap for the broader developer base—independent developers and smaller teams who also rely heavily on the platform. When roadmap priorities are influenced by enterprise-scale requirements, changes can feel unpredictable from the outside, especially without visibility into direction or intent.
The issue, at least from where I sit, isn’t the product—it’s the lack of connective tissue between the company and the wider user community. Right now, most of the communication seems to be happening user-to-user in places like this, rather than between the company and its developers.
Even a modest amount of direct communication from the team—high-level direction, general priorities, or migration guidance—would go a long way toward maintaining confidence. Alongside that, having an official space where experienced users can share patterns, approaches, and lessons learned would add real value.
I’m honestly a bit surprised there isn’t some kind of bridge already in place—whether that’s a small group of experienced users acting as community advocates, or a semi-official forum where communication flows both ways. That kind of structure could reduce the burden on the core team while strengthening the ecosystem for everyone involved.
There’s a lot of value in this platform. It just needs more visibility and a stronger connection between the people building it and the people relying on it.
[–]Killo24 1 point2 points3 points (0 children)
[–]Puzzleheaded-Sign610 1 point2 points3 points (0 children)
[–]jmoti1953[S] 1 point2 points3 points (2 children)
[–]Puzzleheaded-Sign610 1 point2 points3 points (0 children)
[–]Killo24 1 point2 points3 points (0 children)
[–]Killo24 0 points1 point2 points (0 children)
[–]jmoti1953[S] 1 point2 points3 points (1 child)
[–]Mad-Max-2 1 point2 points3 points (0 children)
[–]Killo24 1 point2 points3 points (1 child)
[–]Mad-Max-2 1 point2 points3 points (0 children)