HN user

ferdowsi

2,161 karma
Posts12
Comments228
View on HN

More like companies are reducing scope to focus on key profit centers or initiatives, making product managers and designers easy targets for layoffs.

The vast majority of questions around quality that end up surfacing in code reviews can be much more easily settled by commonly shared tooling that enforces organizational style and security practices. Leaving "best practice" up to the code review stage just ends up allowing senior engineers to demand code that they themselves would write, not what's best for an organization.

Agreed. Too many "senior engineers" fail to recognize when they are simply venting their territorialism by nitpicking in code reviews. The role of a good manager is to restrain these tendencies.

The statement doesn't say how much Gatsby was acquired for. Hope that Gatsby equity holders weren't bought out at a steep discount, given the current macro situation.

Htmx in a Nutshell 4 years ago

I'm curious about htmx, but all of the HTML mini-syntax very similar in aesthetic to Angular 1.0, which was pretty quickly supplanted by React. What excites people about htmx? Do people like the mini-syntax but dislike the ceremony of state management?

Recruiters are salespeople. Toxic positivity, undue flattery, etc are all part of their toolbox. It's ultimately on the candidate to perform due diligence on the organization, like with any product.

This list is an aggregation of public layoff lists where people voluntarily signed up, plus people who sign up through us.

You should be actively getting the consent of these people on these lists. They consented to have their info in lists created and shared by colleagues, not as part of your service.

Exciting stuff! Phabricator was one of the better project/dev management systems I've interacted with and I'm glad to see developer energy behind maintaining and improving it!

I would choose Zig because Zig has a much more approachable learning curve and Zig code is eminently legible compared to Rust code and it's overly complex type system.

The credit card companies strongly push merchants to adopt EMV chips by shifting liability for chargebacks onto merchants who are still using magstripes. I don't think I've seen a non-chip capable terminal in the last year.

The sharing of service contracts and their shared dependencies is a difficult problem to solve by itself. There's companies trying to make money off of the problem (buf). Monorepos solve the problem out of the box.