skysight-inc/HackerNews huggingface dataset:
This reveals one weakness of the Windows development model: if something isn’t a feature that is driven with a PM behind it, it won’t happen. On the other hand, if some obscure internal thing isn’t optimal yet, you can bet some obsessed hacker is going to tackle it one day. How many schedulers has Linux had already?
Corona Killing Me
> churning out features without thinking critically about why, your work might not even change the company

Isn't this just speculation? Why would anyone build features without any thoughts about their benefit?

In practice you never know how a feature is going to work out and benefit or harm the company, you just have to try it. Not trying is a sure way to lose to bolder competition.
Two of these companies are British, and the other two are complete jokes. It is like talking about the 'Ukrainian software industry'. Sure, some of them have computers, but that does not a tech industry make.
What makes you think it's abandoned? The author is active on Twitter, the last update for dark mode was in May 2019 and I don't see any show stopper bugs or crashes on Catalina. Small utilities like this don't need an update every month. I bought it a while ago because

1) It's very cheap and a great show case for a small niche Mac app that's both beautiful and works well

2) The two times per year I use it, it's already worth it and fun to play around with.

https://blog.helftone.com
I agree with all of your arguments except the last one.

1) you should be able to be housing secure from your job

2) $200k+ is an absurd amount of salary

The solution isn't paying MORE salary to further inflate real estate costs and price out ever more service workers that you depend on as a city. The solution is opening offices in one of the many LCOL tech hubs and/or having a remote-first culture.

Open an office in Kansas City (for network infra secret advantages) or Baltimore (for ed/med/gov/NYC access at low cost) or, if you're hiring new grads anyway, any random "big university" town, and see what kind of crazy talent you can attract and retain with 100k.

Real estate prices should not be driving costs for a software company. It's insane.
What about array programming, in your view, would differentiate it from the imperative and related paradigms?
Canada: Wet’suwet’en rail blockades ‘serious threat’ to economy, AB Premier says
The point is to demonstrate capability, not "penchant". I mean, look, subtle code happens. Maybe it shouldn't. But it does, and it has to be fixed. There was a story here just a few days ago about some Project Zero work to find a bug in Chrome that involved a state machine with something like 50+ states! And realistically finding people who can do that requires that they be able to also do things like traversing a binary tree, right?

So I'm going to ask the question one more time: if you won't traverse a tree in an interview, how else do you propose to select for people able to reason about that kind of problem in practical code?
Why is displaying your public IP (prefix?) is an issue?

If this bothers you, shouldn't you use a VPN ?

What do you mean by "normally" ? Torrent is the normal way to host large files in a distributed manner!
BSD would be what Linux is today, but with less drama and more freedom for users.
> How do you know that what you're delivering is any good?

How do you know it isn't? You need to implement it and see whether it's good or not.
Hmm, I got a little thrown off by the words "bundler and minifier", which are both Webpack tasks. Scrolling further down I do see "JSX transformation" thrown in, which is definitely normally a Babel thing.

If this project is trying to replace everything in a single pass then yeah, it's probably doomed to failure. Not only from the ambition of the task, but from the lack of the modular structure that allows community support to thrive: anybody can write a Webpack loader or a Babel plugin without getting their hands dirty in those codebases. That doesn't seem to be the case here.
Show HN: Quicker Way to discover and watch great videos
Feature addiction is exacerbated by VC. Without real consequences to a poorly planned product roadmap due to the years of runway afforded by massive funding rounds, entire orgs fall into the “one more feature” cycle and never focus enough on measuring success in terms of real dollars. No one knows what went wrong when all the money is gone and devs/designers/PMs rinse and repeat at a new well-funded startup.
Interesting thanks. I thought the course of events was: get cancer. Use quackery for a while to no effect. Get real treatment. Discover its a treatable form of cancer. Live half a decade more. Succumb to cancer.
> Even if not intended, someone else may assume your "documentation" function was meant to be generally accessible (i.e. an API), and call it that way.

And then, suddenly, instead of a single use function that serves mainly for documentation and code organization, it js a locally resuable and locally reused piece of functionality. Which is a problem, ...why, exactly?

The only difference between a well-designed single-user function and a well-designed locally reused function is that the single, clear, and unit tested purpose of the single-use function isn't needed in more than one place when it is written. If that changes, why shouldn't it be reused?
As long as it can be streamed or batched you can get pretty much the same throughput with IPC. Only latency suffers slightly (microseconds, still within a frame budget even for realtime use), but you only pay that latency overhead once per batched action.
The "NextGen" they refer to is an animated film that was made in Blender.
I have a wide-ranging self-taught skill set as well that I've developed over the last 14 years of running my own businesses. I'll share what I'm doing from a high level as it might not be the most common path.

I've been acquiring small but promising businesses that don't have the right team in place to move them forward. I bootstrap them on my own and replace my roles as the business can afford staff. Once enough roles are replaced, I'm able to start looking for the next business. I'm on my fourth business now. Sold the first two, the third is a productized service netting seven figures, and I just acquired the fourth, which is a SaaS business that I believe has great potential.

Currently, I'm formalizing this method and will build a team that can execute it much more quickly than me alone. I'll be shooting for a new business every 12-18 months to build a portfolio. We'll have a group of partners and a small staff that will be focused on getting these acquisitions straightened out and growing, then we'll install a team to run them full-time and we'll go on to the next one.

So just taking what I've been doing for years and everything I've learned from it and scaling it up to reduce the timeframe from acquisition to growth and then operation of the business.

If OP or anyone else who identifies themself in a similar manner wants to chat, email is in my profile. I'm actively looking for people like us to work with.
Wow, this looks like huge news for NetBSD. Not too in tune with the BSD ecosystem, but this sounds great for ARM servers.
Sigh... At some point, most healthy adults who are not living in terrible circumstances come to the mature realization and compromise that their job is largely to produce value for someone else, not to be the primary source of personal fulfillment, and they come to understand that there is dignity in being productive, if not creative. Be creative on your own time. Lead a civic group. Be a good parent. Volunteer at a charity. If your main gripe at work is that you're on the value-adding side of a company, which is what feature dev is in software, you have it pretty good in this world. Change jobs if you must, but the realities of companies, especially as they gain traction, rarely means the grass is ever greener. If this is unsatisfactory still, start your own company. I just don't understand the problem here.
Feel free to be horrified: a data scientist who doesn't understand where and why to use unix command line tools for data preparation and ETL is about as useful to me as one who doesn't understand the conditions where a t-test breaks down or what a ROC curve is.

Generally speaking, people like this have never actually dealt with large data sets, never dealt with issues involved with installing "unapproved software" on a machine (ridiculously common in The Real World), has probably never cleaned a dirty data set (what do you do when your giant csv is formatted in a way that Wes McKinney didn't think of?), and will in a senior role be a long term liability for a data science team that works on serious problems. Sure at one point I didn't know about them either: I wasn't a senior data scientist then. I submit that if you don't know about them and haven't actually used them, you aren't either.
This new version of Blender comes with a new fluid solver called MantaFlow. There should be tutorials popping up on YouTube as I type. I use the FLIP fluid add on which comes with good documentation.
I don't necessarily consider that a weakness
I am a Linux user. What would be a good reason for me to try out NetBSD? Honest question.
In practice you could join an autonomous driving or robotics start-up/R&D group.
Me and my kids have been using it routinely since 2.80 (thanks to the shift to saner mouse button defaults and other UX tweaks), and there are loads of great YouTube tutorials out there these days, so I’d say it’s really helped 3D rendering become mainstream.
Ah yes, the chart that lists Oz and Alice ? under every box
I imagine indentured servitude path should be dramatically more expensive by the end of it than paying straight up -- it's like taking money from a loan shark; it's not actually a good deal -- but you don't have the resources to get anything better.

I imagine the actual cost of buying a ticket would probably be like 50÷ the cost of indentured servitude
I have noticed tribalist hatred on this front as well. My friends, who are mostly left, love to make fun of the “conservative” diets and their adherents. I wasn’t even aware that such a division existed until I heard their comments.
Oh cool, missed that being added. That covers a good chunk of the issue.
Our infrastructure lasted for 100 years. That was how I opened. How is that invisible?

Now it's being neglected. Sure I didn't say anything about that, because to me that is obvious.

The world is more than 1st-world advanced countries. I see a bunch of first-worlders going on about who's dick is bigger. Not a reasonable discussion about infrastructure; a venting about how our world-class technology is not keeping up with expanding demand. Essentially a complaint about our plenty, not being enough.

And this bit about 'going after people' is really ripe irony. I've been gentle and respectful. Never addressed other commenters directly, but just the topic. Got to consider that comment trolling at best.

But enough of that. Let the pedantry thrive, I've not got any ego in this game.
True. But imagine if you are also a shareholder in such a company - would you not want them to fix it?
I'm not sure what the debate is. I'm all for changing strategies. My claim is that they don't have data on success from engineering. As evidenced by every pivot they have done being driven as much from marketing as technical.

Chrome, as an example, had a ton of marketing push behind it. Still some solid engineering, but not really any better than Firefox. Wasn't really any better than edge, but ms decided to drop the push for their own tech.

So, my question is what engineering successes do they have to back up their data on what will succeed?

I think you could pull in some of the ml work they are doing. Not sure how much data they actually have there, though.
Do you know what the deal is with the constantly present "Listening for events" notification with RiotX?

Is this to work around the Android background task auto-killing?
Not on topic, but can you point me to some information about the spending habits of someone making that much in a city which I understand is fairly expensive?
I find this diagram less easy to navigate than the simpler categorization of declarative vs imperative with four subcategories:

I.e. Imperative: Procedural, Object-oriented

Declarative: Functional, Logic (or better term for Prolog-esque languages - constraint-based perhaps)

Four simple categories with two meta categories.
Yup, Germany is surprisingly more generous than NL. But here the Liberals have been working hard to prevent a “Scandinavian socialist hellhole”... ;)
Pascal is hardly unique in that; many languages have nested functions, and every language that has first class functions and local variables/constants has the equivalent of nested functions (potentially with even narrower scope than a whole function) even if it doesn't have a specialty nested function declaration syntax.
How is it coming up?
Most of the indications for immunotherapy are cancers with solid tumors. This source [0] is a bit dated (2017) but it contains a chart showing which cancers had an indication for immunotherapy at the time, and they're almost all solid tumors. The initial approvals for the big immunotherapy drugs were for melanoma and non-small cell lung cancer.

[0] https://www.statnews.com/2017/03/08/immunotherapy-cancer-bre...
Look into the security field. Your broad base of knowledge from bottom to top would be helpful.

Find a great security team and hope that they will bring you on and mentor you.

Security is a great specialty for you in that it is very broad and always changing.
Parsing gigabytes of JSON per second in Go using simdjson-go
You should check infrastructure costs for band or other big enterprises... Those companies move to the cloud because it's cheaper...
> Comments can add "section headers", while keeping the code flow linear, so I can skim it just like I skim an article.

Yes, and decomposition provides an outline, which is faster to skim than an article. There's a reason tables of contents are a thing; they let you find wheat you care about much faster than linear text with section headers.

With code, they also have the advantage of allowing you to make use of step-over/step-into debugging.
I've heard about great successes with animal based ketogenic diets, and fasting. There's a clinic in Hungary that treats and (tries to, despite apparent censorship), publish research: https://www.researchgate.net/publication/331812176_PALEOLITH...

Hope you'll find something that works, even if only augmenting your current treatment
I'm surprised by so many negative comments here (actually, I'm not). This great piece summed up a lot of awful aspects about commercial software development that I've also observed over the past 20 years, but have been unable to organize together and articulate as single problem.

People are asking why this is bad. One way to think about why the Feature Factory is bad is that it's mostly open loop: You "launch" feature after feature at the customer, but there's no real feedback coming in to understand whether what you're doing is worthwhile, to understand what to improve or fix, or to drive future decisions. The only feedback that gets measured are things like revenue and sales, and the only thing leadership sees as driving revenue is the constant spew of features--because that's all you're doing. The insights that you get from revenue are very generic: "Money is coming in--keep doing what you're doing" or "We're losing money. Do something different!". The insights you get from salespeople are even worse: "We'll land this sweet-ass deal (and I'll get my bonus) if only you churn out otherwise un-needed features X, Y, and Z!"

I guess this is fine if you're an agency or consulting shop that just does one-off projects and then moves on to the next client. On the other hand, if you're writing software for actual people to use, trying to be the best in class at one thing, or building a platform to last decades instead of months, then your product will suffer if all you do is bolt half-baked features onto it over and over.
Bank transfers in Estonia did get slower when SEPA first arrived, but not horrendously so. I think the transfers used to be every 15 minutes and during most of the day. With SEPA it got downgraded to every hour and only during normal working hours. However nowadays we've already moved on to SEPA Instant Payments which take about 10 seconds and are EU-wide, provided the other EU bank isn't dragging its feet with implementing it.
Most new housing in the Bay will go to higher than average income earners, not poorer people, unfortunately. The Bay is a very dynamic city there vastly more people who would like to live there than actually do, given the right conditions. The Bay may have to contend with paying 'regular people' simply a lot more and contemplate actually sharing more of that wealth being created.
Health insurance may not be so bad for a $300K+ SV software engineer, but it's terrible for just about everyone else. My wife's a teacher and for a while we had to use her health insurance, which meant getting the "family plan" option through her school district.

The cost of that? Half her take-home pay. And it's not even a very good plan (i.e. we were still exposed to a lot of risk, we had a couple medical things come up in the same span of time and were out several thousand more dollars for those).

Now, sure, I make way more money than her so we were fine, but her single-parenting colleagues? The couples in which both are teachers? They're not so lucky. And more jobs pay way closer to a teacher's salary, and may have even worse health benefits, than pay anything like SV software developer money.

Half may be an exaggeration, but for normal people losing 15-30% of their post-tax income to healthcare is probably about right. And of course we're already paying Medicare & Medicaid taxes on top of that.
I suggest re-reading this article in the negative: Assume that your team implemented every single one of these bullet points perfectly, for every feature in every sprint. Now imagine that each of those bullet points is a recurring meeting invite on your calendar. Now imagine how happy you'd be spending all of that time in meetings or reading process-related e-mails so your company could satisfy the criteria of not being a feature factory. Does a feature factory sound so bad now?

I thought this article was great when it first came out, but I've since changed my mind. I've seen too many engineers, especially junior engineers, become overly cynical about their jobs after reading too much into this one article.

1) With 12 different "signs" of a feature factory, it begins to read like a horoscope: Almost everyone reading it can find something to identify with. Multiply this across every different project or initiative at a company, and everyone can think of multiple times their job has resembled the descriptions in this article. Does anyone actually read this article and walk away thinking their company has never once resembled the vague signs in the article?

2) It begins with an implied assumption that working in a feature factory is a bad thing. Combine that with the horoscope-like 12 possible indicators of a feature factory, and the reader will always conclude that their workplace is the bad thing.

3) It sets unrealistically high standards. The alternative to a "feature factory" is defined in the negative in this article. Can you think of any company that would score a perfect 12/12 on every bullet point in this article across every team in every department? The process overhead would be significant, and it would very easily translate to a lot of meetings, e-mails, and overhead.

The kernel of truth within the article is still very valid. Teams should absolutely take the points into consideration and apply them judiciously, where it matters. However, it's a mistake to use this article as a checklist by which to judge your company's process. Real work is always a bit messy, communication is never perfect, and just because you don't see these things with your own two eyes doesn't mean they aren't happening somewhere in the company.

As a product manager, suggestions are always welcome and I'm happy to discuss reasoning for decision making, but I also don't burden the entire team with every detail of every step of the way.
Author here. I think the Rust vs. Go question is interesting. I actually originally wrote esbuild in Rust and Go, and Go was the clear winner.

The parser written in Go was both faster to compile and faster to execute than the parser in Rust. The Go version compiled something like 100x faster than Rust and ran at something around 10% faster (I forget the exact numbers, sorry). Based on a profile, it looked like the Go version was faster because GC happened on another thread while Rust had to run destructors on the same thread.

The Rust version also had other problems. Many places in my code had switch statements that branched over all AST nodes and in Rust that compiles to code which uses stack space proportional to the total stack space used by all branches instead of just the maximum stack space used by any one branch: https://github.com/rust-lang/rust/issues/34283. I believe the issue still isn't fixed. That meant that the Rust version quickly overflowed the stack if you had many nested JavaScript syntax constructs, which was easy to hit in large JavaScript files. There were also random other issues such as Rust's floating-point number parser not actually working in all cases: https://github.com/rust-lang/rust/issues/31407. I also had to spend a lot of time getting multi-threading to work in Rust with all of the lifetime stuff. Go had none of these issues.

The Rust version probably could be made to work at an equivalent speed with enough effort. But at a high-level, Go was much more enjoyable to work with. This is a side project and it has to be fun for me to work on it. The Rust version was actively un-fun for me, both because of all of the workarounds that got in the way and because of the extremely slow compile times. Obviously you can tell from the nature of this project that I value fast build times :)
The toolchain does not have to run on the supercomputer itself. Most supercomputer architectures have self-hosting toolchains there are also supercomputers that do not. Also compiling or even debugging programs directly on the machine is in most cases plain waste of (expensive) computing resources and it is not that one would ever have only the supercomputer and not any other computers (in fact, many traditional supercomputers cannot boot on their own and have to be booted by some kind of frontend computer).
lol and how can you not enjoy the surprise ending!
Go to that candidate's website. Read books about them. Check their voting record.
At a certain company size, there simply is not the level of control (ODA loops) to know what product to make or features to add - it is a fairly good survival strategy to have multiple teams duplicating huge amounts of work simply because a few will deliver the right thing.

The internal politics of most organisations has a similar feel - lots of duplication looks like competing camps and frequently is, but the duplications is partly survival strategy (what if those others don't deliver) and partly evolution (one team will deliver something that actually fits the market.)

Boy there are better ways to arrange it, but this seems to be a local maxima that's easy to reach.
https://youtu.be/uf3ALGKgpGU

https://youtu.be/iZn3kCsw5D8
No, it doesn’t work that way for HTTPS. Public Key Cryptography is a relatively expensive operation. So the public/private keys are used to create and exchange a temporary symmetric encryption key. That symmetric encryption key is used to encrypt and decrypt the HTTPS requests and responses later by the client and the server.

What you describe is used that way when you want to send, say encrypted emails to someone else when you have their public key.
You could potentially not need node installed in order to do "modern" frontend development.