zlwaterfield

I built Radar because GitHub's notifications are noisy and hard to keep up with.

Radar lets you customize notification preferences – so you get a message when you're @mentioned, assigned, etc. It uses AI to match keywords semantically (so "auth" catches "authentication", "login", "OAuth").

It also sends daily digests: PRs waiting for your review, PRs ready to merge, your open PRs – grouped and summarized.

Stack: NestJS, Next.js, Trigger.dev for background jobs, Prisma, Slack API.

Self-hostable with PAYMENT_DISABLED=true for full access. We use it daily at my company.

GitHub: https://github.com/zlwaterfield/radar

Would love feedback on the notification preferences – it's the trickiest part to get right.

This is really cool! I can see the list of your supported Connectors on the site. How could I create custom integrations in Pica that would be accessible via the AI SDK?

Plan is to add local LLM support so goal is fully OSS, agree initial wording could have been better.

Agree, wording could be improved. I'm gonna add local LLM support.

Agree - I want to improve the UX, this was just a quick attempt at it. Thanks for the feedback!

Honestly just an oversight. I want to remove that dependancy anyways with an open source model.

Correct but I'm going to loom into a locally running LLM so it would be free.

Not right now. Looking into a mac app. This was just a quick and dirty first go at it.

Agree, I want to add a local LLM set up. The wording there isn't great.

After years with Grammarly, I wanted a simpler, cheaper way to improve my writing. So I built Scramble, a Chrome extension that uses an LLM for writing enhancements.

Key features: - Uses your OpenAI API key (100% local) - Pre-defined prompts for various improvements - Highlight text and wait for suggestions - Currently fixed to GPT-4-turbo

Future plans: add LLM provider/model choice, custom prompts, bug fixes, and improve default prompts.

It's probably buggy, but I'll keep improving it. Feedback welcome.

GitHub: https://github.com/zlwaterfield/scramble

There’s a bigger picture than just the consumer. If there is not a chance to exit then founders won’t be incentivized to create these companies and employees won’t be incentivized to join or stay at these companies. If M&A markets are limited then the only option is IPO which goes through major cycles and probably can’t support the number of companies needed. Plus many companies can’t get big enough to IPO.

This is sad for the overall M&A market. Companies are going to be scared to enter into these agreements because it’s just a waste of time and money when it inevitably ends up like this.

A straight up G

That really went off the rails.

I lol’d at:“My name is Chris and I am a man of the truth.”

With the advent of AI, a substantial portion of the laborious tasks involved in the 3-tier model will likely be automated, making it less likely for most to move away from this approach. In my opinion, the 3-tier pattern was established for valid reasons, and any attempts to simplify it by removing tiers might inadvertently constrain developers, leading them to eventually revert back to the original model.

Regarding solo projects, I agree that simpler stacks like BaaS or other innovations can be sufficient. However, fast-scaling companies often require the unparalleled flexibility and customizations offered by an in-house 3-tier model. This tailored approach ensures they can effectively meet the evolving demands of their growing operations.

For me it depends on the OS because I don’t mind Apple TV ones but the Samsung OS has subtitles that move around and I can’t stand it.

Agree most are crap. But they are getting better. With the ramp up of embeddings, the data they have access to is more useful and with LLMs they can provide you with plain English answers that are customized for you. Good example: look at what the Supabase docs can do. Not a chat bot but demonstrates the capabilities.

I’ve worked on a few support sites for companies over the years. In all my research I found >40% of customers never look for the answer before contacting support. That’s why you’ll see sites add a bunch of questions with recommendations to answers based on your description before you can contact support. Even AWS support does this.

Bots may be annoying but they can also save the company tons in custer support costs. I’m for it if the UX is good and I can quickly contact an agent if the bot can’t answer my question. This is assuming the bot won’t hallucinate and just tell me random fake facts.

I’m a huge fan of Lunch Money. It’s made by a small team that truly understands the feature-set needed for a full personal finance app. I’ve been on it for 4 years and couldn’t imagine using anything else.

Here’s my referral code if you’re interested: https://lunchmoney.app/?refer=igqb31gn

Damn

I love TransferWise, use it all the time. Honestly, pretty surprised by this rebrand, I don't get why they did it.

WorkOS | Multiple positions | Remote (US timezones) | https://workos.com/

WorkOS is an early-stage technology startup that provides APIs to make cloud apps enterprise-ready. Our first offering allows developers to quickly add Single Sign-On (SSO/SAML) to their app. WorkOS is like Stripe for enterprise features. Here’s our HN launch: https://news.ycombinator.com/item?id=22607402

We are a small, nimble, fully-distributed team based in North and South America. We care deeply about building tools and perfecting the developer experience. We ship code every day. We have ambitious goals and are looking for talented people to join us. Our team values trust, empowerment, empathy, curiosity, speed, and intellectual rigor.

If you love building developer tools and working at the intersection of product, engineering, and design, we'd love to hear from you.

Technologies we use:

* Next.js, NestJS, GraphQL

* TypeScript

* SDKs in 8+ languages (https://github.com/workos-inc)

* Postgres

* Heroku

Positions:

* Software Engineer - https://jobs.lever.co/workos/2333cdf9-5c71-4232-9dc8-4f18f6a...

* Engineering Manager - https://jobs.lever.co/workos/2adf7e5f-3e9b-4847-8e34-c52529c...

* Developer Success Engineer - https://jobs.lever.co/workos/1fe7ef18-57c9-4aa2-b595-de7623a...

* Product Designer - https://jobs.lever.co/workos/dfde45ea-18fe-4aef-9660-0374f13...

* any many more at https://jobs.lever.co/workos

Please apply directly to the postings. Email zach.waterfield@workos.com with any questions you may have.

Happy user here. My favorite part is the seamless local development abilities.

Checkout this YC company from the W19 batch https://www.thejuggernaut.com/newsletter

Congrats on the launch, this looks awesome!

I agree with this, it seems like you don’t have much IP that would be worth selling.