HN user

gfody

1,678 karma
Posts4
Comments779
View on HN

This has been happening for a while now, basically anywhere there’s room for a potential compatibility issue there will be one. As if any time some observable behavior is an implementation choice the Chrome team policy is “not what Firefox does”. The result is that if you develop on Chrome and don’t test on Firefox your stuff is very likely broken on Firefox.

The AirPods Effect 1 month ago

incarceration is going too far, all you need is a few enforcers with shock wands like in Demolition Man

Claude Fable 5 1 month ago

K2.6 on Cerebras is basically a preview of the future. We'll eventually get similar performance locally with Tenstorrent hardware.

we'll just use /etc/hosts no DNS required!

this is classic "easy vs. simple" folly, witness how someone too lazy to [learn how to] setup proper DNS for their infrastructure will do 10x the work hacking something "easy"

"quality" isn't succinctly definable. Zen and the art of system maintenance quality code is written by an old and wise programmer and any attempt to rigidly codify what it is they did and why is doomed to fail.

Sure but the OP suggests that these were minor gains

When antirez says 'I ventured to a level of complexity that I would have otherwise skipped,' I don't think you can call that a minor gain. The alternative is likely something 'good enough' that leaves the community dissatisfied for months, and then after initial design mistakes become load-bearing the ideal implementation can never be realized.

I haven't used azure devops but I used TFS in its heyday and still haven't ever seen a better integrated ticket workflow with fully customizable states and transitions - it's like a mutant hybrid of jira and github but all built into VS. There's definitely something to be said about keeping the primary admin UI in the dev tools.

it's actually neither. normal forms provide semantic guarantees through structure. the structure proposed here does not constrain the data in any way and therefor cannot be said to be a normalization - tfa is dead wrong basically.

this timing matches my experience, enterprise plan, but using opus from vscode - finished a heavy refactor of a large C# codebase mid march, tried to do basically the same thing early april and couldn't

Layoff Thinking 3 months ago

vibe layoffs are bad practice due to fundamental attribution error (line managers don't necessarily have any idea who their low performers are even if they think they do) and ultimately expose the company to discrimination lawsuits if hr doesn't enforce a fair and consistent selection criteria

regardless of who is on the hook for what, ones contributions are their own. a manager makes contributions by performing actions just like anybody else. this label for implying that a managers contributions includes that of their reports is bogus - if a manager does absolutely nothing at all we should consider the contributions of their reports? actual technical jargon adds precision to language "IC" takes it away, it's nothing more than corporate newspeak ala 1984