Comment

Comment by raxxorraxor

Of course, I didn't want to say it is entirely wrong. But not every project will be some foundational core project and you won't have one without the other. Neglecting such contributions because the authors might not do it for a marketable product is likely a sub optimal HR policy which leads to sub optimal business decisions and results.

We compare the usual corporate grind or corporate experience with these contributions. It is not the whole of problems in engineering hiring, but at least something to consider. The requirement of a product is an economic necessity but not something intrinsic to good engineering. And yet I think hiring decisions would strongly benefit to have further understanding of this particular value of problem solving, even if that alone doesn't meet the requirements of a successful business.

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton