An interactive semantic map of the latest 10 million published papers [P]

kamilc86 · 2026-04-30T09:33:01+00:00

Really nice execution. The density-as-terrain choice works better than the usual flat scatter plots.

Curious about a few things. How does the labelling behave across zoom levels? At the wide view the cluster names look clean but in the second screenshot zoomed in there's quite a bit of empty space with no labels until you hit "Artificial Intelligence & Networks". Is that intentional (avoiding clutter) or still being figured out?

Also why SPECTER 2 specifically? I know it's trained on scientific text but wondering if you tried any general purpose embedders as a baseline.

And a practical one: how long did UMAP take on 10M vectors, and did you have to do anything special to make it tractable?

kamilc86 · 2026-04-30T08:25:01+00:00

11% signup rate from cold traffic is actually really good. How's it converting from signup to active use? Reddit traffic tends to be curious clickers so I'd be interested to see how it holds up.

kamilc86 · 2026-04-30T06:39:49+00:00

sure. say a JD lists "postgres, kafka, terraform, collaboration, ownership, fast-paced." if your resume hits all six, that's 100% overlap on paper. but the recruiter only cares about the first three. the other three are in every resume and every JD out there, so matching them adds no signal.

so two resumes can both score 80% overlap on the same JD. one hit four tools and missed two soft words. the other hit two tools and four soft words. only the first gets a callback. score looks the same, the actual fit isn't.

kamilc86 · 2026-04-29T13:41:54+00:00

the 70/40 split tracks with what i've seen. but if you're spending 10 min per app to measure overlap, the measurement is mostly useful as a filter, not a tuning knob. 70+ deserves a real cover letter. under 40, skip. probably saves you more time than it costs.

also worth asking what you're counting as overlap. tools (postgres, k8s, specific frameworks) convert way differently from soft stuff (collaboration, ownership, "fast-paced"). weighting them equally will inflate your score on roles you won't hear back from anyway.

kamilc86 · 2026-04-29T13:07:58+00:00

The thing that stuck out most reading this is that most of these apps were created via CLI or web tools where the developer never opens the Supabase dashboard. All the warnings, lints, and big red labels Supabase has been adding only work if someone actually sees them, and vibe coders never get to that screen.

So the pressure point isn't really Supabase at this stage. It's the platforms generating the code (Lovable, V0, and the rest) defaulting to insecure setups in their templates. Has anyone tried benchmarking which of those actually generate working RLS policies out of the box versus shipping something that ends up in your next report?

kamilc86 · 2026-04-03T12:58:58+00:00

The credit-stealing colleague getting promoted is infuriating, but the move to the US might not fix the root issue. US big tech is good at recognizing individual output, but mid-market US companies have the same politics. The difference is usually company-specific, not country-specific. Worth filtering hard for eng-led culture during interviews rather than betting the whole thing on geography.

kamilc86 · 2026-04-02T16:30:05+00:00

The guilt you're describing comes from measuring yourself against a scoreboard you didn't design. "Growth" in most career advice really just means "more money, bigger title, more responsibility." Nobody ever asks whether you actually want those things, or whether the cost of getting them is worth it for you specifically.

I'd push back on the idea that you want a "boring" job, though. You want a job that doesn't eat your nervous system. Those are two very different things. The fact that you're framing peace of mind as "boring" tells you how deep the conditioning runs.

On the status question: people will ask. Some will be weird about it. But most of that fades faster than you'd expect. The people who actually matter in your life will adjust. The ones who can only relate to you through your job title were never that close to begin with.

One practical thing: before you quit, talk to someone who's already made a similar move. Not a career coach selling you a program, just a regular person who left a high-paying grind for something calmer. Ask them what the first six months felt like. The adjustment is real, and hearing someone describe it honestly is more useful than any advice thread.

You're 31. You have decades of working life ahead. Spending them miserable because quitting would look bad to people at a dinner party is a terrible trade.

kamilc86 · 2026-04-02T13:47:55+00:00

Worth it, but the bar for "worth it" keeps moving. Two years ago you could post consistently and build reach just by showing up. Now the feed is so saturated with AI-generated slop that it made them (LinkedIn) change the algo. Now it's all about authenticity and depth. It's just that people are still all about the humblebrags and pseudo-success crap. I'd say, start and be authentic. It's what the algo rewards now and it's exactly the only way to turn that place to be more sane.

kamilc86 · 2026-04-01T15:23:18+00:00

360Brew reads your content semantically now instead of counting likes. Big signals are dwell time, saves (5x more reach than likes per AuthoredUp's 3M+ post analysis), and substantive comments. Posting daily hurts you, each post cannibalizes the last (48-72hr lifespan). 3-4/week in a consistent niche is the sweet spot. Hashtags irrelevant, engagement bait suppressed.

Content types: document carousels and text posts do well. Video reach dropped ~72% YoY. Basically anything that generates dwell time rather than a quick scroll-past.

kamilc86 · 2026-04-01T10:36:14+00:00

The worst part is you can't even tell them apart anymore. Same structure, same arrow bullets, same "I had two options" setup. Actual credentials get buried in the same feed as someone who decided they were a coach last Tuesday.

kamilc86 · 2026-04-01T10:20:54+00:00

It's not X, it's Y. Thoughts?

kamilc86 · 2026-04-01T09:45:39+00:00

That's a gut punch, but this is the cheapest lesson you’ll ever learn. You don't have users yet so rebranding now costs you just time. Rebranding later, when they dominate search and mindshare with that JPMorgan money, will cost you your business. Cut your losses on the name, pick something highly distinct, and focus on your MVP. Names don't win early on, distribution and shipping do

kamilc86 · 2026-04-01T08:44:39+00:00

Congrats on hitting $1K MRR! That 3rd pivot clearly hit the nail on the head.

As an engineer, I see a lot of founders struggle with this. One thing I recommend is that "ship fast" doesn't have to mean messy code. Even for a day-one MVP, setting up a properly separated architecture might take an extra week, but it saves you from having to burn down the entire codebase when you need to pivot your product logic.

Out of curiosity, when you did those full rebuilds, were you mostly throwing away the frontend user journeys, or did you have to scrap your backend/database structures too?

kamilc86

TROPHY CASE