DevKoury

An Obsessive engineer with a mischievous streak · building fluxcrawl
24 Y/O
· heavily caffeinated ☕
Trying to overcome shiny object syndrome

[DevKoury @Devkoury]

I have a bad case of shiny object syndrome.
So I’m publicly removing the option.

For the next 6 months I’m building one product. No jumping to the next exciting idea, no rewriting the thesis every week.

Goal: get a real paying customer. If I can’t do that in 6 months, I switch.

This is post #1. Consider it a contract with myself.

[ShowUpAnyWay @ColdMorningGrit]

Hackyard #3 starts today.
@HackyardSocial

Theme: One Screen. Everything your build does has to fit on a single view.

Building Dream Team — pick 5 X builders, get a fighting-game character card for each one with role, stats, and team power level.

One screen. No nav. Just your roster.

[DevKoury @Devkoury]

Cool use case. Have you looked into Jev for the tailoring/decision layer?

You could potentially use it to decide which experiences, skills, and keywords from the master CV are actually relevant to a specific job before handing that context to the LLM to rewrite.

I’ve been experimenting with it for decision points in agent workflows, and this feels like an interesting fit.

[DevKoury @Devkoury]

It’s everyone’s dream now and all the gurus and “I built this to $10K MRR in 30 days” content makes it feel way more normal and easy than it actually is.

AI made building cheaper and faster, but that just moved more of the work into distribution, conversations, and actually finding people who care.

The thing that keeps me going is pretty simple though: you can keep trying and maybe get there, or stop and guarantee you won’t.

[DevKoury @Devkoury]

@crisgrossmann Thanks for sharing, will take a look!

[DevKoury @Devkoury]

@crisgrossmann Also, have you come across Jev for agent routing and decision-making? I’ve been experimenting with it in my own setup, using it at decision points to choose what an agent should do next. Curious if you’ve looked at it for your agent handoffs.

[DevKoury @Devkoury]

That’s really cool. The linked agents are especially interesting to me. How are you handling the handoffs between them? Does one agent explicitly decide which agent gets the task next and pass structured context/output to it, or are the workflows predefined?

Also adding Pushover to my list 👀

[DevKoury @Devkoury]

I feel this, Stripe isn’t available to me directly in Egypt, so I looked into setting up a US LLC just to use it. Then I went down the rabbit hole of physical address requirements, compliance, and the possibility of still getting rejected.

Ended up going with Paddle instead. They take around 5%, which hurts, but sometimes you just do what you have to do to get V1 out the door.

Shipping > spending weeks fighting payment infrastructure.

[DevKoury @Devkoury]

@The_CozyDev I think you nailed what I’ve been noticing with the “AI look”, it’s not necessarily that anything looks bad, it’s that everything starts reaching for the same safe patterns again.

Will try to keep the smaller, more deliberate design system in mind. Thanks for sharing this!

[DevKoury @Devkoury]

@buildwtim HI Tim,
24, husband, 9-5 AI lead, building on the side and chasing that $10K MRR goal.

Hopefully adding “dad” to that list one day too

Sounds like we’re on a pretty similar path, just at different chapters. Glad to connect!

[DevKoury @Devkoury]

@buildwcrispim @DmitryBBLV @explee Urgency first for me. In my opinion, if the pain is real enough, they’ll make time, share what they’re using today, and actually push the product until something breaks. That feedback is worth way more to me right now than someone who just thinks the idea sounds cool.

[DevKoury @Devkoury]

Started testing Fluxcrawl before even having a landing page.

Sent a few cold emails through @explee, got a few high-intent leads. Enough early validation to keep building.

So I shipped the first version of the landing page.

Live social data through one stable API.

Now working on the backend and aiming to get the first usable version out next week.

Still early, but we're building 👇

https://t.co/epZZbw5Is3

[DevKoury @Devkoury]

Building in public also means building my X account from scratch.

I’ll probably grow much slower than the playbooks recommend.

I could automate replies, write AI slop, pump out posts, and try to optimize every interaction for engagement.

But I’d rather actually get to know the people behind the accounts.

Already had some great conversations with @AfterimageDev, @romg_dev, @ColdMorningGrit, and @buildwcrispim . I’ve learned what they’re building, why they’re building it, and even found my way into @HackyardSocial.

That’s the part of building in public I’m enjoying most.

So, who are you? What are you building, and why?

Drop it below. I genuinely want to check it out and get to know more builders here.

[DevKoury @Devkoury]

@ColdMorningGrit Really appreciate the shoutout, man! Still early days with Fluxcrawl, but building and pushing every day. Thanks for putting me on the radar 🫡

[DevKoury @Devkoury]

@buildwcrispim @DmitryBBLV @explee I ran the campaign for a little over a week and got 6 interested replies, I will reiterate and build, then try to run a small pilot.

[DevKoury @Devkoury]

@ColdMorningGrit Awesome, I am in!

[DevKoury @Devkoury]

@ColdMorningGrit Ahh that makes sense! Which hackathon did you participate in?

[DevKoury @Devkoury]

@buildwcrispim @DmitryBBLV @explee The concierge pilot sounds cool though, have you gotten any high-intent leads yet? What stage are you at with it now?

[DevKoury @Devkoury]

For me it was mainly describing the pain and sharing what they’re using today. I got a better picture of their current setup, pricing, what’s missing, and where the friction is. That was enough validation for me to dig deeper into the market and figure out where Fluxcrawl can have a strong differentiator.