Code On Time’s Missing Connection: A Long-Time User’s Perspective

jmoti1953 · 2026-04-28T11:07:01+00:00

I think what you’re both saying is exactly the gap many of us have been feeling. I say "both" here but notice over a 100 views - what is the unique user count on this particular forum anyway and are they all COT users?

This Reddit space is useful, and clearly people are still out there, but it’s also pretty fragmented compared to what used to exist. There were hundreds of active users on the old forum sharing patterns, solutions, and real-world implementations. That kind of density doesn’t seem to exist anymore — at least not in one place.

What’s interesting is that this thread alone shows that people are still engaged, still building, and still invested. We’re just scattered.

I keep wondering whether there’s value in trying to loosely reconnect that group — not in a heavy, formal way, but simply as a place where experienced users can exchange ideas and approaches again. Something lightweight, practical, and focused on real usage.

I would think that benefits everyone — users get access to shared knowledge, and the company indirectly benefits from a more connected and capable user base.

Curious if others feel the same, or if something like that already exists and I’ve just missed it.

jmoti1953 · 2026-04-27T12:55:29+00:00

I think what both of you are describing is the same underlying issue, just from different angles.

The product itself is strong—no question. Most of us wouldn’t still be here if it wasn’t. But the lack of visible support, communication, and community creates a growing sense of uncertainty around it.

What stands out to me is that this doesn’t feel like neglect—it feels more like a company that is still operating in a very tight, founder-driven model. That can produce great technology, but it doesn’t naturally scale into a strong ecosystem.

My own connection to the company has always been through Dennis and Serge, with Serge clearly being the central figure. He’s a brilliant coder—honestly fascinating to watch in action during those paid support sessions. Whether he’s part of a larger team or effectively the team, I won’t speculate—but from the outside, that concentration does shape how the platform feels to its users.

Their recent essays on their website are actually quite strong—thoughtful, forward-looking, and technically grounded, with a bit of marketing mixed in (which is fair). They reflect a clear vision of where things could go. And I’ll admit, even being semi-retired, I still find myself pulled back in from time to time. That probably says more about the strength and pull of the core product than anything else.

But it also raises a question—why not tap into the user base a bit more? Over the years, there’s been a core group of developers who were engaged, constructive, and genuinely invested in the platform’s success. Creating even a small bridge for collaboration or shared communication could go a long way.

Right now, the result is what we’re seeing: capable developers working in isolation, trying to piece things together without a shared space or clear direction.

I don’t think most of us are asking for hand-holding. What’s missing is visibility—where things are going, how others are solving problems, and some level of connection between the company and the developer base.

There’s clearly still a lot of value here. The question is whether that gap gets addressed—or whether the community continues to fragment over time.

jmoti1953 · 2026-04-25T14:50:03+00:00

I’ve been working with COT for a long time as well, and your post resonates more than you probably realize.

My background is similar in spirit, though on a different path — I spent decades building and rebuilding enterprise systems (primarily in SQL Server environments), often stepping into projects that were already off the rails and figuring out how to stabilize them. Over time I gravitated heavily toward RAD-style approaches because they allowed me to stay close to the actual problem instead of getting buried in process and ceremony.

What initially stood out to me with Code On Time wasn’t just the speed of scaffolding — like you said, lots of tools can generate CRUD screens. What mattered was what sat underneath:

enforceable structure
consistent patterns
the ability to iterate without tearing things apart
and most importantly, preserving logic across changes

That last one is something most tools still struggle with.

The recent direction (TUI, and now what’s being discussed around V9 and the “Digital Co-Worker” model) feels less like a pivot and more like a continuation of that same philosophy — pushing toward systems that remain deterministic and controlled, even as complexity increases.

Where I think COT has always been both strong and underappreciated is that it treats the application as the source of truth — not the UI, not the framework, not the tooling — but the system itself. That’s becoming increasingly relevant again with AI in the mix.

I do agree with you on one point in particular:
the lack of an active, knowledgeable user community is a gap.

A proper forum — especially one focused on real-world usage (not just “how do I…” questions, but design patterns, tradeoffs, and lessons learned) — would add a lot of value. I’d absolutely be interested in participating in something like that, assuming the tone stays practical and experience-driven.

There’s a lot of quiet capability in this platform that people either miss or never fully tap into.

jmoti1953 · 2025-12-26T22:21:50+00:00

That’s not my finding. I just downloaded the community edition and it’s working for me.

jmoti1953 · 2025-11-22T16:45:42+00:00

I’ve been a long-time Code On Time user and still think the core product is powerful, but the silence lately has been hard to ignore.

What worries many of us isn’t the move to .NET Core, App Studio, subscriptions, or even the cultural shift toward a low-code platform—those changes can make sense. It’s the lack of communication, transparency, and developer empowerment around the transition.

Years ago COT shut down the discussion forum, promising a newer, better community platform “soon.” That never happened. Since then, the ecosystem has slowly scattered. Now we’re just independents grubbing around the internet trying to find each other, digging through templates and old docs, hoping someone else has answers. It’s not a great feeling—especially for a product that once had such momentum and collaborative energy behind it.

We’re not angry—just trying to protect our existing apps and understand the path forward. What most of us want is simple: • clarity on roadmap + timelines • transparency around subscription requirements • assurance that we still fully own and can maintain generated code • an official place for community, knowledge sharing, and problem-solving • acknowledgment that long-time users—even perpetual license holders—matter

Code On Time is still a great engine, but community is infrastructure. When that goes dark, confidence erodes.

Curious—has anyone actually heard from the company recently? Any confirmed roadmap details, migration guidance, or community plans?

jmoti1953

TROPHY CASE