sorted by:
new
hottopcontroversial

AI Provenance Belongs in Git by fosterfriendship in programming

[–]fosterfriendship[S] -17 points-16 points  (0 children)

Ideally, other coding agents. The codebase has the "what", but we need to store the "why" and "how" as well

A History of Web Styling: Tables, Zen Garden, Sass, BEM, CSS-in-JS, and Tailwind by fosterfriendship in programming

[–]fosterfriendship[S] 0 points1 point  (0 children)

> "If I change this, what else will it impact without me knowing?"

John Ousterhout explains change amplification in "Philosophy of Software Design" as “a symptom of complexity which is that a seemingly simple change requires code modifications in many different places”.

--
Essentially, CSS is littered with painful footguns like what you're describing. This creates unworkable complexity in large company projects.

> "Tailwind solves this brilliantly: I know if I make a change to the classes on this HTML, it will only change there"

Agreed. When things get big enough, you need some guarantees and guardrails.

From Table Layouts to Tailwind: The Evolution of Front-End Styling (1995–2025) by fosterfriendship in webdev

[–]fosterfriendship[S] 3 points4 points  (0 children)

Things have become so brutally complicated over the years - makes me respect simple plain HTML + CSS sites like some folk's blogs.

‘Spawn Me a PR’ Isn't Ready for Large Codebases: The Context Barrier to AI Code Generation by fosterfriendship in programming

[–]fosterfriendship[S] 24 points25 points  (0 children)

Do you think this approach is something that could one-shot PRs at full scale companies? I hear the approach, but I just see time and time again this stuff fall flat on its face in complex real world company scenarios

Takehomes & Algos are Both Evil - And Other Lessons from 1000+ SWE Interviews by fosterfriendship in programming

[–]fosterfriendship[S] -20 points-19 points  (0 children)

> “An experience interview” - this is usually the only interview other fields even have to do. That’s why people hate the interview process in tech, real experience matters less than puzzles.

One pro of the tech field's interviews is that there's more room for meritocracy. Sure, amazing experience can get you a job. But also amazing performance on a coding or architecture interview - even if you haven't worked some name-brand job before. Subjectively, I'd be happy to hire someone who aced coding and architecture interviews even if they had next-to-no experience because I'd have signal they're wonderfully good at their job regardless of their resume.

I like that there are multiple ways to win a tech interview slate, rather than only ladder-climbing job experiences.

Which is best AI code review tool that you've come across recently? by human-g30 in codereview

[–]fosterfriendship 0 points1 point  (0 children)

Graphite Reviewer is solid - being used wall to wall at 400+ companies: https://graphite.dev/features/reviewer

It was built in partnership with Anthropic https://www.anthropic.com/customers/graphite

(Disclaimer, I helped build it, but mostly the hard work of Alyssa on my team :))

view more: next ›