seen from United Kingdom
seen from Spain
seen from United States
seen from China
seen from Italy
seen from United States
seen from Ukraine
seen from United Kingdom
seen from China
seen from United Kingdom
seen from Spain
seen from United States
seen from Bangladesh
seen from Malaysia
seen from United States
seen from Germany
seen from Australia
seen from Germany
seen from Germany
seen from Germany
Just had a friend, who always annoyingly referred to me as toxic, finally write herself out of my life. For the one who was being “toxic”, I sure feel a rise in energy, a lift in mood. Now it has me wondering who was really the toxic person in the relationship.
#Repost from @tizio3010 with #sharegram.app. Versione scherzo 😂😂 #ilvolo #italymusic #italy #lunchtime #music #happybirthday #moday #top #tour #american #americantour #2k17
Moving a brand built with Claude Code into Codex
A large part of MODAY was built with Claude Code.
Shopify theme tweaks, Gelato integration, multilingual blog distribution, the chatbot, GA4-based improvement ideas, localized articles. Even when I did not fully understand the technical layer myself, I threw the work at Claude Code, let it build, checked the result, and kept moving.
I have already written about how I use Claude Code. Do not over-organize. Delegate. Follow the momentum. That style fit me, and it worked especially well during the launch phase.
And now, I am trying to move the MODAY working environment to Codex.
Not because Claude Code was bad. Actually, the opposite. Claude Code was good enough that I wanted to test whether I could move away from it.
Read the full story → https://moday.me/blogs/journal/moving-from-claude-code-to-codex
Retracting what I said about "the observation loop"
In an earlier post I wrote that "the observation loop started" — that the moment we opened, the world began talking back.
Four or five days in, here's what I actually figured out: the sample size is too small to observe anything.
I can stare at GA4, follow cart behavior, scrape the chatbot logs — but the volume is so low that none of it produces a hypothesis worth acting on. To even start theorizing, more people have to walk in.
So the right move isn't observation yet. It's getting the traffic up first. I had the order wrong.
Read the full story → https://moday.me/blogs/journal/ai-asked-everything-for-shorts
From the missed opportunity on 5/19 to a live bot in 15 minutes
I wrote about this in another post: on 5/19, the first two customer inquiries came in. I couldn't reply same-day; my response went out the next morning.
I logged that as lost opportunity, and that same day I built a chatbot.
The usual little widget that sits in the bottom-right corner of the store. From "start working" to "deployed and live on Shopify," about 15 minutes. Here's what I know about what's actually inside it.
Read the full story → https://moday.me/blogs/journal/15min-chatbot-render-comeback
A client showed up to a Zoom call wearing a t-shirt that said, in big bold Japanese letters, "I'm so very sorry."
He'd gotten stranded on a trip because of a typhoon. Couldn't get home. Couldn't change clothes. So he wore that shirt — and it apologized for him before he even spoke.
I laughed. And then I thought: a t-shirt can describe your day in one line.
That's how MODAY started — day-of-the-week tees for engineers and geeks who want their Monday brain ("System Booting…") and their Saturday brain ("Off the grid") to look different.
Built solo. Shipped globally on-demand. Documenting the build in public.
Read the founding story → https://moday.me/blogs/journal/why-moday
