Very excited to announce that tomorrow I'll be making the repo public for everyone to be able to run a very close version of my personal playbook.

All you'll need is a google places API key from google cloud services & Claude CLI.

I've started to notice something about mature products.

The size of a feature rarely determines how much work it takes.

Instead, the effort depends on how many past decisions that feature touches.

A simple "Add Google Login" suddenly affects authentication, onboarding, permissions, analytics, documentation, QA, and maybe even your pricing model. What looked like a two-hour task turns into a week of discussions because you're no longer building a feature; you're negotiating with decisions your product has accumulated over months or years.

I've made this tool called Eneya, and unlike most things posted here the name tells you nothing, so: it's written pre-screening for tech recruiters. You build a short questionnaire around the competencies the role actually needs, candidates answer it in text on their own time, and you get back a scored report on each one. No video, no scheduling, no calls that end in the first four minutes.

Anyone who has screened for a role with two hundred applicants knows the specific dread of it: you're going to interview maybe eight of those people, the CV tells you almost nothing about who's worth the slot, and somewhere in that pile is the person you should have hired. With Eneya you get to see how each candidate actually thinks about the work before you spend an hour on them, and the report shows its own arithmetic, so when you tell a hiring manager why someone didn't make the shortlist you have something to point at rather than a number the tool refuses to explain.

Latest TalkPix experiment:

• One still portrait

• One audio clip

• Zero filming

The concept:

A direct portrait that suddenly turns into a Beat It performance.

Hello everyone!

My friend s mother lost around $40K on a fraudulent crypto investment. She believed she had found a golden opportunity and risked all her savings, only to be devastated when the scam unfolded. Witnessing her pain and financial loss, I both a coder and a cybersecurity specialist realized something had to change.

That's why I created StopScam: Scam Detector Pro. I built this app to provide a reliable tool for protecting your hard-earned money. With StopScam, you can manually upload screenshots, images, or take photos of digital content, physical letters, and even PDF files. Our advanced AI, machine vision, and OCR technology analyze them for scam signals.

I first installed StopScam for my family and close friends, ensuring they would never face the same hardship. And this is just the beginning! In the near future, I plan to add even more useful features to further safeguard your loved ones from fraud. StopScam is designed to be your comprehensive shield against scams, keeping you one step ahead of fraudsters.

Every trip planner I tried either dumped a checklist that ignored geography, or handed me a "finished" plan I had no say in. Built Routinex to fix that: neighborhood-anchored days, group voting, live weather/flight data, and a Cruise Port mode for people who stress about all-aboard timing.

routinex.travel

What's the one trip-planning problem you still haven't found a good tool for?

Hi!

I ve been building my website for a few months now, all on my own.

Hey everyone!

If you re building a SaaS or a side-project, setting up payments usually means hours of dealing with webhook routing, customer sync logic, and getting locked into one provider.

I built Paycan to fix this. It s an open-source, self-hosted checkout layer.

• No Vendor Lock-in: Switch between Stripe and PayPal without changing your database or application logic (more local payment providers soon).

• Drop-in Simple: Around 10 lines of code to integrate.

• Self-Hosted & AGPLv3: You run it on your own server, keeping full control over your checkout.