They ask people how they are doing after stress has already built up, after someone has already withdrawn, or after a manager already feels that something is wrong but cannot clearly see what is happening.
As my launch date gets closer, I've been reflecting on how much of building a product has nothing to do with code.
A few lessons have surprised me:
Building is usually easier than deciding what to build.
Users don't always use a product the way you expect.
Small improvements repeated consistently beat big bursts of effort.
Progress often feels invisible until you look back months later.
The biggest surprise for me has been how often assumptions turn out to be wrong. Features I thought people would love weren't always the most valuable, while simple things ended up mattering far more than expected.
You can spend only 2 hours on your phone and still destroy your focus.
So I built OXIS.
Instead of counting time, it tries to measure attention fragmentation in real time: Mind Score (0 100) App switching behavior Recovery after distraction Daily cognitive patterns
One thing surprised me:
People with lower screen time were sometimes more fragmented than heavy users.
Curious:
If your phone measured attention instead of time what would you want to see?
(Feedback appreciated still improving the model.)
There's a debate I keep having with enterprise AI teams.
Side A says: 'Ship something working in 4 weeks, prove value, then refactor. Enterprises want results, not perfect code.'
Side B says: 'One bad architecture decision in enterprise AI costs you 6 months of rework. Get it right before you scale. The cost of fixing later is 10x.'
I fed an AI some of the longest and most confusing documents I could find. Terms of Service.
Contracts.
Prediction market rules.
Even secretive organization documents. Most people have no idea what they re actually agreeing to. So I built MarketRules AI upload any document and get a plain-English breakdown in seconds. https://curly-market-logic-lab.b... I d love your feedback.
Hello everyone. Welcome back to my siterows.com series. Quick reminder of what this app does: Allows you to scrape web content with SQL, like you would query a DB. Creating a FREE account unlocks automation features and higher usage limits. Today's question: "On the site, what is the whole deal with this Objects box?" The purpose of the objects box is to give it a SQL-like look and feel, and here is how it's structured: When you expand "DOM" and further expand any element like @a or @div, you get two items: "Scraper Fields" and "Attributes". Under "Attributes", you'll find all the standard HTML attributes for that element Under "Scraper Fields", you'll find a couple of extra synthetic attributes I thought would be useful like Index, Parent, Children, etc... Scrolling back to the top, you'll see a couple of "Composite" elements I also thought would be useful. For example, the @headings element represent @h1, @h2, @h3, @h4, @h5, @h6 elements combined. Think of any element like @a, @div, or @headings as your "tables", and their attributes like href, id, class as your "fields".
Thanks, everyone. Please don't hesitate to reach out with any questions or feedback.
Also I am a technical CEO - (Ask me anything about AI, LLM's SLM's, Server's architecture, Encryptions, Quantum Computers) Currently building the first AI doctor Avatar that can diagnose you from a video call.
App is finished ( pending review from playstores)..
Will launch it here at Product Hunt, where probably it will be seen only from Me, Myself and I
I ve been building Atlasly to make global data easier to understand and compare. It s a web app that turns open datasets into clear country profiles, rankings, and trend charts helping anyone explore how nations evolve in numbers.
Atlasly is built with simplicity and curiosity in mind. Instead of overwhelming users with raw data, it focuses on clean visuals and meaningful comparisons.
I've been comparing the free tiers of social media schedulers and the word "free" is doing a lot of heavy lifting.
Most free plans fall into one of two traps. Either they cap your scheduling volume so low it's unusable past week one (10 posts, 20 posts/month), or they let you schedule but lock the thing you actually need behind a paywall: analytics, more than one or two channels, or AI features that run out after a few credits.
