frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Micro-Front Ends in 2026: Architecture Win or Enterprise Tax?

https://iocombats.com/blogs/micro-frontends-in-2026
1•ghazikhan205•1m ago•0 comments

Japanese rice is the most expensive in the world

https://www.cnn.com/2026/02/07/travel/this-is-the-worlds-most-expensive-rice-but-what-does-it-tas...
1•mooreds•1m ago•0 comments

These White-Collar Workers Actually Made the Switch to a Trade

https://www.wsj.com/lifestyle/careers/white-collar-mid-career-trades-caca4b5f
1•impish9208•1m ago•1 comments

The Wonder Drug That's Plaguing Sports

https://www.nytimes.com/2026/02/02/us/ostarine-olympics-doping.html
1•mooreds•1m ago•0 comments

Show HN: Which chef knife steels are good? Data from 540 Reddit tread

https://new.knife.day/blog/reddit-steel-sentiment-analysis
1•p-s-v•2m ago•0 comments

Federated Credential Management (FedCM)

https://ciamweekly.substack.com/p/federated-credential-management-fedcm
1•mooreds•2m ago•0 comments

Token-to-Credit Conversion: Avoiding Floating-Point Errors in AI Billing Systems

https://app.writtte.com/read/kZ8Kj6R
1•lasgawe•2m ago•1 comments

The Story of Heroku (2022)

https://leerob.com/heroku
1•tosh•2m ago•0 comments

Obey the Testing Goat

https://www.obeythetestinggoat.com/
1•mkl95•3m ago•0 comments

Claude Opus 4.6 extends LLM pareto frontier

https://michaelshi.me/pareto/
1•mikeshi42•4m ago•0 comments

Brute Force Colors (2022)

https://arnaud-carre.github.io/2022-12-30-amiga-ham/
1•erickhill•7m ago•0 comments

Google Translate apparently vulnerable to prompt injection

https://www.lesswrong.com/posts/tAh2keDNEEHMXvLvz/prompt-injection-in-google-translate-reveals-ba...
1•julkali•7m ago•0 comments

(Bsky thread) "This turns the maintainer into an unwitting vibe coder"

https://bsky.app/profile/fullmoon.id/post/3meadfaulhk2s
1•todsacerdoti•8m ago•0 comments

Software development is undergoing a Renaissance in front of our eyes

https://twitter.com/gdb/status/2019566641491963946
1•tosh•8m ago•0 comments

Can you beat ensloppification? I made a quiz for Wikipedia's Signs of AI Writing

https://tryward.app/aiquiz
1•bennydog224•9m ago•1 comments

Spec-Driven Design with Kiro: Lessons from Seddle

https://medium.com/@dustin_44710/spec-driven-design-with-kiro-lessons-from-seddle-9320ef18a61f
1•nslog•9m ago•0 comments

Agents need good developer experience too

https://modal.com/blog/agents-devex
1•birdculture•11m ago•0 comments

The Dark Factory

https://twitter.com/i/status/2020161285376082326
1•Ozzie_osman•11m ago•0 comments

Free data transfer out to internet when moving out of AWS (2024)

https://aws.amazon.com/blogs/aws/free-data-transfer-out-to-internet-when-moving-out-of-aws/
1•tosh•12m ago•0 comments

Interop 2025: A Year of Convergence

https://webkit.org/blog/17808/interop-2025-review/
1•alwillis•13m ago•0 comments

Prejudice Against Leprosy

https://text.npr.org/g-s1-108321
1•hi41•14m ago•0 comments

Slint: Cross Platform UI Library

https://slint.dev/
1•Palmik•18m ago•0 comments

AI and Education: Generative AI and the Future of Critical Thinking

https://www.youtube.com/watch?v=k7PvscqGD24
1•nyc111•18m ago•0 comments

Maple Mono: Smooth your coding flow

https://font.subf.dev/en/
1•signa11•19m ago•0 comments

Moltbook isn't real but it can still hurt you

https://12gramsofcarbon.com/p/tech-things-moltbook-isnt-real-but
1•theahura•23m ago•0 comments

Take Back the Em Dash–and Your Voice

https://spin.atomicobject.com/take-back-em-dash/
1•ingve•23m ago•0 comments

Show HN: 289x speedup over MLP using Spectral Graphs

https://zenodo.org/login/?next=%2Fme%2Fuploads%3Fq%3D%26f%3Dshared_with_me%25253Afalse%26l%3Dlist...
1•andrespi•24m ago•0 comments

Teaching Mathematics

https://www.karlin.mff.cuni.cz/~spurny/doc/articles/arnold.htm
2•samuel246•27m ago•0 comments

3D Printed Microfluidic Multiplexing [video]

https://www.youtube.com/watch?v=VZ2ZcOzLnGg
2•downboots•27m ago•0 comments

Abstractions Are in the Eye of the Beholder

https://software.rajivprab.com/2019/08/29/abstractions-are-in-the-eye-of-the-beholder/
2•whack•27m ago•0 comments
Open in hackernews

Ask HN: What's it like working at early-stage YC startups?

4•jennalk•4w ago
Considering an offer from a YC startup that's raised seed, 6 months post-pivot, and actively looking for PMF before Series A. What should I know about this stage? What's different from pre-seed or post-Series A companies? Any questions I should definitely ask them?

Comments

codingdave•4w ago
Pre-PMF running off a seed round? There is a very real timer counting down. They need PMF and customers before the money runs out in order to convince the next round of investors. Assume it will be a 3-6 month gig, with a mild chance of actually turning into a real job if everyone gets lucky.

You should ask them how long their runway actually is, what goals need to be hit in order to get to the next round and extend the runway, and how this role is going to contribute to those goals. Be wary of anyone who won't answer those questions or who doesn't know the answer to those questions.

jennalk•4w ago
Thanks for the insight. Since they're post-pivot and hunting for PMF, I’m trying to gauge the panic vs focus ratio.

Does this stage inevitably turn engineering into a feature factory just to close deals? I'm worried the roadmap will become 'whatever the client screams for' rather than building a scalable core. Any specific questions I can ask the founders to sniff that out?

codingdave•4w ago
You'd need to dig into who is running their product decisions, and try to determine how they are making decisions. But to be honest, that line of questioning would probably make most interviewers defensive to the point that you'll be ending your chances of getting the job.

It might be better to dance around such questions. Don't directly challenge their product strategy. Instead, be a little sycophantic, encourage them to talk more, tell you more. Get excited by the features they tell you about, ask questions about how they landed on that feature set, etc. But then pay attention to what they don't say. Pay attention to if they say "we had an idea" vs. "our customers helped us refine" vs. "our founder has a vision". Listen for gaps in their stories, hesitations, anywhere that they get a little nervous. Pauses and rephrasings as they tell their story will also tell you their problem areas.

Basically, just keep them talking. Read between the lines. Teams at this stage tend to be really bad at hiding the warts in their organization, if you just give them enough space to let it all out.

dustingetz•4w ago
join after the A if you care about money. Join before the A if you are uniquely mission aligned or technology aligned, e.g. it’s 2016 and you want to work in VR, and aren’t optimizing for money right now. Early stage is fun and you’ll learn a lot and that’s about it.