zan
Joined 16 years ago
Joined 16 years ago
I used to work in devrel, and traveled a lot for events, and I always struggled skipping things like workouts, looking at the time on the last day of a conference trying to check whether it's time to leave yet - so this gives me the opportunity to build a tool I would have loved to use.
Currently I'm working on a LLM-powered booking email parser, that ingests forwarded booking confirmations and adds flights, hotels, etc. to your itinerary.
It's a travel tool for business travelers that figures out your suggested departure times for your entire itinerary based on predicted traffic patterns. Think Flighty but for all the non-flight parts of your trip.
You first build a travel itinerary with your legs - flights, activities, hotels (and hotel returns) and it tells you things like "leave your hotel at 7:40am" before your 8:30 meeting - in a single itinerary, no need to do the google maps acrobatics for every two items in your itinerary. While it's aimed at frequent business travellers I personally use it for all family leisure travel and daily itineraries around town as well - "do I have time for lunch at home after my son's class or should we bring packed lunch". I built it as during my time working in developer relations I traveled a lot, and always built unnecessary buffers and kept nervously glancing at my watch or phone to see if my planned time to leave still holds.
Tech-wise, currently it's Remix web app with a NodeJS/Fastify backend and Supabase for storage, and relying on google maps for route duration calculations. I want to expand it to native mobile clients in the future as well.
I am using it as playground on product thinking, ruthless prioritisation based on user benefit, figuring out unit pricing and economics, sensible architectural design, and exploring how including AI-enhanced features here and there can help make the product better, not just include them for their own sake.
We can offer a $50 Amazon gift card as a thank you.
Happy to also answer any questions.
I recently created this one to help with my particular GitHub workflow - instantly diff any commit with the current master branch: https://gist.github.com/zmarkan/503789d31acf385e44f13b0b3c3c...
I just have one remark - how on earth does a 737 fly from SFO to LHR without stopping as in the example?
This is gold
> Rule Number One: You may not use a single word an LLM suggests to you.
Over the last week-ish I turned around 2 product announcement blogposts within ~24hrs. Both written manually by someone who doesn't do product marketing for a living. It actually felt incredibly satisfying to focus and smash something out that was 100% human (despite praising the benefits of agentic systems, oh the irony).
My flow has been: Go for a walk, record all of the thoughts on the topic with speech to text, and have LLM organise my thoughts into what I call "facts" - simple sentences of fact, and point out open questions and inconsistencies ("you are a product marketing expert helping me organise the content for an upcoming feature announcement" ...).
After some back and forth of inconsistency bashing I have a large pile of short sentences in the vein of "Feature X is for Y because Z", that I use to manually build a narrative with headings, and then write the actual copy covering a subset of them.
I also agree that light style LLM edits are fine, and that I don't let LLM do anything other than ordering and filler words removal and provide structural comments.