37. Jeweller in Dubai. Taught myself to code with AI.
My kids (8 & 7) said school was boring. So I built them a tutor.
The twist: it never gives answers.
It asks questions until they figure it out themselves.
Small Codex UI idea: surface the existing weekly usage indicator directly in the composer toolbar, so itβs visible while working without opening the usage menu π
@thsottiaux
@ldo_dev Polling a very bad idea at scale. Cost eat up.
I have not been posting much, got contracted for enterprise software.
Personally I went with SSE. Polling at small scale is okay.
@ldo_dev I used it for sometime. Rounded corners look amazing addition.
I am working an a similar CAD product but in my niche. Would love to know which app or workflow you are using for taking these videos. Donβt want to research.
hey everyone took almost 2 weeks off. now back with a question. really hope to get some guidance.
For one of my projects i need to create a simple AI automation which might bring more clients to my gold business, but i was thinking of creating it separately as a Startup.
The concept is not unique but it has my own unique take on it as a business owner. There are already many competitors at least 7 which i could find but they don't do the one thing which i want to include and should be a there. So doing such a startup would make sense?
@eliana_jordan Claude with opus to brainstorm as it is good to talk to, Codex before shipping things. All inside antigravity just in case need any assets or images. Best of all things I guess
I built a content system inside my code editor.
Every coding session, I run one command: /content-recap
It reads my git commits, finds what I shipped, and drafts 3 posts in my voice:
- 1 build-in-public post
- 1 community post
- 1 hot take
Then it adds them to a content calendar file right in my repo.
Building an AI tutor for kids. 3 users. Shipping every day.
The hardest part of building in public isn't the building. It's the "in public" part.
This system made it automatic.
Send RECAP in reply to get the automation.
#BuildInPublic
My content calendar is a markdown file. Not Notion. Not Buffer. Not Hootsuite.
It lives next to my code. Same repo. Same workflow.
When I ship a feature, the post draft is 30 seconds away.
Building in public shouldn't feel like a second job.