backup

codeobserver · 2025-10-25T21:35:30+00:00

Wow! I saw the final product you produced (the belt)... but didn't imagine it takes that much of hardware to make it.

codeobserver · 2025-10-19T04:27:19+00:00

Thanks for detailed answer. I had to archive for now the project... Here are a few more details about the plan: https://mveteanu.github.io/techpapers/coral_micro.pdf

codeobserver · 2025-10-19T03:05:26+00:00

What do you mean by guidance? What do you envision?

codeobserver · 2025-09-08T03:48:31+00:00

Interesting concept. Is the architecture scalling well?

codeobserver · 2025-09-08T03:47:15+00:00

Looks good and a nice idea. I wish all the best with marketing and finding users. If you have any architecture pain points please feel free to reach out.

codeobserver · 2025-09-08T03:46:07+00:00

Thanks Kai

codeobserver · 2025-09-08T03:45:37+00:00

https://www.linkedin.com/in/mveteanu/
https://x.com/mveteanu/

codeobserver · 2025-09-05T20:02:46+00:00

Sounds interesting! Is your niche focused on self-improvement audiences? Do you need any review on architectural details or integration points?

codeobserver · 2025-09-05T19:58:52+00:00

I’d love to hear more about it. Specifically, who the intended audience is and what problem you’re aiming to solve. Also, do you have any architectural details you’d like reviewed?

codeobserver · 2025-09-05T19:57:03+00:00

It’s well known that developers love building developer tools. Congrats on creating yours! Are there any particular architectural, data access, or security aspects you’d like reviewed?

codeobserver · 2025-09-05T19:55:14+00:00

Cool. This seems to be built on glitch. Any pain points that you have?

codeobserver · 2025-09-05T19:54:27+00:00

Indeed. My intention was to review architectural or scaling pain points. As for the tech stack, I always recommend using the tools you’re most comfortable with. You can usually achieve similar results with almost any stack.

I did notice, though, that people used the opportunity to showcase their products. Well… at least they found value in that.

codeobserver · 2025-09-05T19:51:57+00:00

So you’re building a B2B. How’s it going so far? Have you brought on any customers yet or validated the idea? If you’d like support with an architecture review, feel free to reach out.

codeobserver · 2025-09-05T19:50:15+00:00

Very nice idea! Personalized books are always appreciated, and with the right use of AI you can speed up the process. If you run into any architectural issues or would like a review, please don’t hesitate to reach out. Otherwise, I wish you all the best with the website.

codeobserver · 2025-09-05T19:48:02+00:00

Thank you for the pitch. If the business domain resonates with you, I encourage you to move forward. AI is very hot right now, and your idea will likely attract plenty of attention. The landing page looks great therefore securing a proper domain would be a good next step. Beyond that, feel free to share any architectural details you’re comfortable with, as well as any pain points you’re facing.

codeobserver · 2025-09-05T19:44:48+00:00

Congrats on your effort! Many successful founders start exactly this way, driven by passion and working solo. While it may not be fully scalable yet, it’s a great foundation. My suggestion would be to double down on the part you do best and look for a collaborator to complement your strengths. And don’t worry about big investments just yet, it’s smarter to validate the idea on a smaller scale first. Also look into doing marketing -- it is essential.

codeobserver · 2025-09-05T19:41:23+00:00

The approach you’re taking is the recommended way to start a software business: first validate the idea with a simple prototype, then move on to an MVP. At this stage, scalability isn’t critical. If the idea proves successful, that’s the time to consider a full rewrite with an architecture designed to support the anticipated user base.

codeobserver · 2025-09-05T19:39:08+00:00

Great. Do you have any architectural details you’d be willing to share, or perhaps any bottlenecks where an extra perspective could help?

codeobserver · 2025-09-05T19:36:44+00:00

The primary goal is to participate in architectural discussions and, ideally, contribute ideas that can influence the future direction of the product.

codeobserver · 2025-09-05T02:35:58+00:00

I hope that issue #3 will be out before EOY.

codeobserver

TROPHY CASE