Trying to write code while chat pings pop up every ten minutes is basically impossible. I tried turning off notifications on my phone but my laptop screen would still light up with every little update. The only thing that actually saved my focus was setting specific blocks of time for communication and treating the rest of the day as offline. If notification settings aren't enough for you
what physical or software tricks do you use to keep yourself from checking chats constantly?
I ve been a user of cloud based password managers for years. But after the LastPass breach, and seeing more leaks every quarter, I started feeling uncomfortable. My passwords, my bank accounts, my private keys all sitting on someone else s server. Even if zero knowledge sounds great, I can t verify it.
So I went the offline route. I tried pass (the standard Unix password manager) but GPG is a nightmare for non tech folks. I also looked at Keepass, but the UI feels like it s from 2005, and syncing between devices is clumsy.
I m preparing for a Product Hunt launch, but I haven t shared the product publicly yet. I m considering keeping it private until launch day, while using the next two weeks to talk with makers and learn from other launches.
For people who have launched before, did staying quiet help, or did it make the launch harder? What did you share beforehand without revealing the full product?
I ve been curious to try an AI notetaking tool that doesn t loudly announce itself when joining a call and only shares the notes afterwards with me.
I guess this is starting to become more commonplace but it still feels (to me) like an intruder in the call, and like I should ask permission (just as when someone records the call - I m honestly not sure there is really any difference).
We have more ways than ever to monitor business performance. Analytics dashboards update continuously, AI can summarize data in seconds, and reporting tools can automate much of the preparation.
Yet many teams still make decisions through weekly reporting cycles.
Here's the distinction I've been thinking about: having real-time data isn't necessarily the same as recognizing a meaningful change in time to respond.
A KPI could cross an important threshold on Tuesday, but the implications might not be discussed until Friday's review.
Curious what the community is running for authentication/authorization in their apps (e.g. Auth0, Supabase Auth, Clerk, Firebase Auth, Cognito, etc.)
A few things I'd love to hear your take on:
What provider are you using and what's your primary stack? (e.g. Next.js + Clerk, Go + Auth0, etc.)
What's the one thing that surprised you , good or bad ?
Would you make the same call today? Especially curious if you've hit scaling pain.
For context: I'm building a B2C application with my own database layer, and currently in the process of evaluating which authentication provider best fits the architecture. Trying to understand how others are handling the auth <> database relationship and what influenced your final decision.
When you ask an AI to write tests for a complex module it always defaults to the cleanest, most basic inputs. It never thinks about null values, weird timeouts or race conditions unless you hold its hand through every single scenario.
By the time I write out all the strict edge cases myself it almost feels faster than letting the agent do it.
When an agent actually nails a complex feature request across 8 different files, reviewing the PR feels harder than writing it from scratch. You have to hunt for subtle logic bugs hidden inside 500 lines of generated code. For daily agent builders, what s your sanity check review process?
