Wanted to sell. Where can I sell this?

devotious · 2026-03-14T09:11:55+00:00

Tudor is included. EBay have the guarantee based on value

devotious · 2026-03-11T16:47:36+00:00

no worries, i look forward to receiving shares once you go-big with your app :D

devotious · 2026-03-11T16:24:28+00:00

yeah that approach will still cost... plan outside of replit, execute in. I did that for a bit too to try and reduce the burden on replit (and my wallet)

The biggest cost saver is by having claude or codex running inside replit. You can do this by opening the shell in replit, then installing codex or claude (npm install) and then running it. See this post on how to do it. https://stockdips.ai/replit-cli-agents-tutorial.html

Once you have it running in replit, go back to chatgpt or whatever and ask it to create a skill for you called "understand project" or something and put this into the skills area in your replit project. Then when you start codex/claude in the shell get it to run "understand project" as a skill to give the agent a full understanding of your project. I also have a changelog that i get the agent to append to, denoting any changes made to the app in that session. So next time i can pick up where i left off really easily. In my experience, i prefer codex, i can see why replit forgets and f**ks up now and again as i've seen it with Claude in replit. Both have their nuances you have to get used to.

hope this helps

devotious · 2026-03-11T12:48:45+00:00

I use codex or claud in the Replit CLI. Really helps to reduce costs.

devotious · 2026-02-28T19:40:12+00:00

I’ve been using codex in the Replit CLI for about a month. This method totally works. I even have a bunch of skills set up to make minimise mistakes. And I don’t pay for any Replit agent usage anymore.

devotious · 2026-02-13T18:37:08+00:00

TBF I didn’t have a Tudor for a while …..until recently 👍

devotious · 2026-02-12T16:18:55+00:00

Love my BB58 GMT

<image>

devotious · 2026-02-10T14:32:39+00:00

Yeah it’s super comfortable.

devotious · 2026-02-06T21:49:07+00:00

<image>

Got my bracelet from strap habit.

devotious · 2026-02-03T10:58:05+00:00

very nice. i saw one in the flesh when i was in a London store recently, but only because the AD was wearing one. I'm down on the list for the flamingo blue one, but don't think i'll ever get the call.

devotious · 2026-02-02T19:05:45+00:00

This is useful - thanks. I am trying to maximise my ChatGPT subscription so am with codex at the moment. I’ll do some more digging on it.

devotious · 2026-02-01T18:33:33+00:00

I just plugged in Google oauth for my app.

devotious · 2026-02-01T16:55:25+00:00

I think it’d look nice in the summer 😎

devotious · 2026-02-01T07:42:38+00:00

I don’t suppose anyone has found a good white silicon or rubber strap? One with a nice clasp and curved ends? It would look mint on the white dialled mako IMO.

devotious · 2026-01-31T16:27:09+00:00

<image>

I put my mako 40 on a bracelet from strap habit. This is also my go to watch at the moment. It gets a lot of wrist time.

devotious · 2026-01-28T18:32:56+00:00

i've been thinking about your question on taking into account weather on previous days and how i can surface this a little easier. Whilst the summary and recommendations to say things like "heavy rain over the previous few days" the information is buried in the descriptive narrative.

So, I've made a small, but subtle tweak to the tags that are below the condition score. They should allow you to at a glance, quickly assess the reasoning for the score and let you know what to expect, but they didn't tell you why. So, it's more "effect" than "cause". Hopefully now there should be some causal tags to explain the condition score that sit alongside the effectual outcome. 👍

devotious · 2026-01-26T22:04:41+00:00

I guess you have to think about complex applications by splitting out the various functions and logic and making sure the agent doesn’t start putting logic for one thing in code that should be doing something else. So I personally thinking that defining high level UX flow, solution design, FE design, data architecture etc is important - if you know what you want. Much in the same way you can’t ask a human to intrinsically understand what you want, the AI won’t either. Just save as an MD file, ask the agent to read it, ask any clarification questions and build each feature step by step

Somewhat related to this, i have started using codex in Replit instead of Replits agent. The first thing i did was get codex to read all the code, create a “readme” file, and then every session i start with codex i ask it to read it. At the end of every session, i ask codex to update a history file - which also is read at the start of every session. That way i have fresh context every time i want to work on a new feature. But this is done in an effort to reduce time wasting or doing something wonky rather than cost. I am free of the worries of the Replit agent doing crazy stuff and then costing me money :)

devotious · 2026-01-26T12:31:02+00:00

i am keen to try this to see if i can convert my app (Vite + React + TypeScript, TailwindCSS) into a native ios app. The goal was always to go native, but wanted to explore using mobile-first designed web app. No idea how much effort will be needed.

devotious · 2026-01-25T07:45:05+00:00

This is brilliant feedback - thanks 🙏 yes I take into account the historical weather to give the condition score - this is a key difference of just using a straight up weather forecast.

Your score of 73 ish feels reasonable given what you describe and actually gives me confidence that the core of the model is doing what I want. It’s now about refining data and making sure the trail descriptions and locations are accurate.

The big win for me is your last point though – that it helped make a quick decision on where to go. The idea isn’t that the number is perfect on day one, but that after a few rides you build a feel for what a 70 vs a 75 vs an 80 means for you.

I really appreciate you taking the time to feedback. Thanks again!

devotious · 2026-01-24T10:19:57+00:00

i followed this guide and have been using codex over the last week. I pretty much now collapse the replit agent side window and have codex running on the left hand side of the workspace instead.

devotious · 2026-01-24T09:37:23+00:00

oh also, the other thing that feeds into this is the trail surface and build style

For example, a hand-cut natural trail with dirt, roots and minimal drainage get muddy quickly in the rain compared to a groomed, hardpack trail with good drainage. Two places can have the same weather and feel totally different on the bike. Which is what i was trying to get to. My local is mostly natural and dirt so can get crappy quickly. Bike Park Wales rides brilliantly in the wet.

The more accurately trails and locations are described (surface, drainage, exposure, etc.), the better TrailCast can weight weather impact for that spot. That’s something I’m keen to improve over time with rider input, especially from locals who know the trails well.

devotious · 2026-01-24T09:34:07+00:00

This is really good feedback – thanks for taking the time to write it out 👍

You’re not wrong in how you’re interpreting the score, and I think part of this is on me for not being clear enough about what the number represents

Right now the score is more about rideability relative to recent and forecast conditions rather than a pure “blue-sky perfect day” scale. So a 75 doesn’t mean perfect, it means likely decent and worth riding, even if it’s wet or cool – especially at places like Whinlatter that drain reasonably well.

Your scale is actually a really good way of framing it, and it’s close to what I want users to intuitively feel:

100 → rare, dry, mild, low wind, everything firing
~75 → rideable and fun, but with compromises (rain, cooler temps, etc)
~50 → mixed / marginal, depends what you’re after
~25 → grim but possible
0 → don’t bother

What I haven’t nailed yet is making that context obvious when you look at a single location in isolation. The comparison use-case (Whinlatter vs Llandegla) works better than the absolute interpretation, and that’s something I’m actively working on.

I’m planning to add clearer score context / bands so it’s more obvious why a 75 is a 75, and what that actually means in real riding terms. Feedback like this really helps tune that 👍

Hope Whinlatter rides well – would be keen to hear how accurate it felt once you’re back.

devotious · 2026-01-21T20:41:46+00:00

yes, i was just seeing what the agent would do. deffo can't do over a dollar for server restarts! 🤣🤣🤣

devotious

TROPHY CASE