Hey @X
I’m looking to connect with:
- Founders
- Builders
- AI enthusiasts
- Saas founder
- Software engineer
- Vibe coder
If you’re one of the above, say hi and let’s connect 👋
Devs, I’m curious about something:
When you get a new idea, how do you turn it into an actual product?
What happens before you write the first line of code?
Do you validate the idea first?
Do you define the logic?
Run tests?
Build an MVP?
Talk to users?
What’s your strategy from idea → product?
Yesterday was a 12+ hour coding marathon building, debugging, testing, and refining every detail.
And now, the result is live.
The new feature is officially available on https://t.co/jKFlo5NfNp.
Another feature shipped. Another step forward.
Back to building
I just shipped a feature I wish existed before visiting Kosovo.
You tell E-Visiton:
📍 where you’re going
📅 how long you’re staying
🎯 what you’re into
And boom your Kosovo itinerary is generated in seconds.
No more “what should I do here?” 😅
Plan My Trip is now live on https://t.co/o57haOr6bA 🇽🇰
Most developers don’t need another AI tool.eeee
They need to get better at thinking.
AI can write the code.
It can explain the error.
It can even architect the solution.
But if you don’t understand why something works, you’re not becoming a better engineer.
You’re becoming better at prompting.
And there’s a big difference.
Hey devs, I have a question:
Would you rather work on a project with:
10 developers + perfect documentation
or
3 developers + complete ownership?
I’m curious what people would choose — and why.
I truly believe you should build in silence until you reach a certain stage.
In the early phases, you’re still figuring things out. You don’t know every feature, direction, or even what the product will eventually become.
Sharing too early can make it easier for others to replicate the idea before you’ve had the chance to validate and shape it.
Build first. Share when there’s something real to show.