News for hackers. Stuff that matters.
Re:Demystifying Radix Trees: How Radix trees made blocking I... by derpherpsson on Wednesday January 16, 2019 @12:58PM (#18923121)
I am appalled that the understanding of basic complexity theory is missing in a company like this, and that people apparently think this is worth reading.

This SHOULD NOT be news.

Maybe you guys should revisit your school books.

No, this comment is not "too harsh" or elitistic.

Re:Demystifying Radix Trees: How Radix trees made blocking I... by fiveoak on Wednesday January 16, 2019 @02:11PM (#18923921)
No one is forcing you to read it... I'm a self taught developer and I lack a lot of low level data structure/algorithms knowledge. I really enjoyed reading the article myself and learned something from it. Sorry that you didn't enjoy it.
Re:Demystifying Radix Trees: How Radix trees made blocking I... by coldtea on Wednesday January 16, 2019 @03:39PM (#18924910)
Maybe programmers should educate themselves in the basics before working on products people depend on? Customers PAY that company for their services.

Would you be ok if the people who worked on your house didn't know about construction basics -- and worse, created stuff that's widely known to be ineffective?

Re:Demystifying Radix Trees: How Radix trees made blocking I... by loeg on Wednesday January 16, 2019 @03:43PM (#18924954)
So you've just written off internship, apprenticeship, or the possibility of any on-the-job training, because? Everyone must somehow become a master craftsman without any in-market work experience before they start working? That's absurd.

> Customers PAY that company for their services.

If the impact of poor programming is material, customers will send their money elsewhere. Customers evaluate products in a marketplace; unless the sale explicitly mentioned the developers' qualifications, it's not like they are defrauding customers.

Re:Demystifying Radix Trees: How Radix trees made blocking I... by jerojasro on Wednesday January 16, 2019 @03:50PM (#18925012)
No, he doesn't. Any of those alternatives you mention (apprenticeship, etc.) require someone senior to you overseeing your tasks/progress. That someone can be a colleague, boss, CS teacher, etc. It's up to the entity overseeing your development (be it a school, or a company) to provide such expertise.

Once again, it's OK that you (person, programmer) don't know that. But as a company, there should be a strong guarantee that you (company) have the knowledge to build a good product. It's fine for a company to have some people who don't know this stuff, but not to not have anyone capable (and in a position that allows them to) notice these kind of mistakes.

Re:Demystifying Radix Trees: How Radix trees made blocking I... by loeg on Wednesday January 16, 2019 @04:24PM (#18925439)
The parent comment is talking about individuals, not companies:

> Maybe programmers should educate themselves in the basics before working on products people depend on?

That remark clearly puts the onus on individual workers and there is no qualifying statement that anyone who doesn't know this particular thing should be allowed to work, under supervision.

Re:Demystifying Radix Trees: How Radix trees made blocking I... by coldtea on Wednesday January 16, 2019 @06:01PM (#18926435)
>That remark clearly puts the onus on individual workers and there is no qualifying statement that anyone who doesn't know this particular thing should be allowed to work, under supervision.

Ever heard of the principle of charity? Programmers should educate themselves, and that includes senior supervision. And they should make sure they used what's best for the job when the ship while still learning -- and if they're unsure, they could check with someone...

Re:Demystifying Radix Trees: How Radix trees made blocking I... by loeg on Wednesday January 16, 2019 @06:58PM (#18926920)
The sarcastic question about my reading being uncharitable is amusingly disconnected from your original, extremely uncharitable comment about the OP.
Re:Demystifying Radix Trees: How Radix trees made blocking I... by coldtea on Wednesday January 16, 2019 @05:59PM (#18926411)
>So you've just written off internship, apprenticeship, or the possibility of any on-the-job training, because?

Nope, didn't wrote off any of those. In fact I encouraged them, saying programmers should educate themselves (and all of those are ways to do that).

What I did write off was letting selling ineffective staff by interns, apprentices, on-the-job trainees ship to customers...

Do customers pay for a quality product or to have whatever done by cheap or unpaid internets shipped to them?

Re:Demystifying Radix Trees: How Radix trees made blocking I... by bahhh on Wednesday January 16, 2019 @03:54PM (#18925080)
I'm also appalled by why they even need to recode a radix tree themselves to filter out a DDOS, considering the many options available without reimplementing the wheel.

any serious hoster filter out ddos with a router. routers are basically build to test IP against subnets, so they can basically run each IP address against a million of hardware subnet testers all running in parallel and decide what to do depending on the result.

And if you don't have a router, any OS worth its salt already have a radix tree implementation for its routing table. The only thing you need to turn a Linux routing table into a ddos filter is to enable reverse path filtering and then add blackhole routes with iproute2.

Re:Demystifying Radix Trees: How Radix trees made blocking I... by groestl on Wednesday January 16, 2019 @01:20PM (#18923374)
The first part of your comment might be true, but regarding the newsworthiness of the post: there is always someone reading this from today's lucky 10000 [0]. It's generally great if complexity theory gets more coverage, here and on company's blog posts. Even if you know this inside out, your colleague might just hear it for the first time, or they might just want to read it up again because they didn't pay attention in class. Which is good for you too. Also, tomorrow you might be one of those lucky 10k.

[0] https://xkcd.com/1053/

Re:Demystifying Radix Trees: How Radix trees made blocking I... by appletrotter on Thursday January 17, 2019 @01:26PM (#18933134)
I think it's great to put out an article like this, for the reader. But it's terribly embarrassing for the company.
Re:Demystifying Radix Trees: How Radix trees made blocking I... by outworlder on Wednesday January 16, 2019 @03:18PM (#18924675)
Well, this is one reason why some companies insist on grilling candidates on "academic stuff".

Guess what, sometimes it's needed. Even knowing that a given data structure exists is sometimes enough.

Re:Demystifying Radix Trees: How Radix trees made blocking I... by fizwhiz on Wednesday January 16, 2019 @04:54PM (#18925807)
I don't know why you're being downvoted, but I agree with your assessment. Your tone is perhaps a bit harsh, but this is precisely the reason large companies grill candidates on basic CS knowledge because like it or not it forms a fundamental base for you to build stuff on.
Re:Demystifying Radix Trees: How Radix trees made blocking I... by mcguire on Wednesday January 16, 2019 @02:51PM (#18924360)
I'm more disappointed than appalled.

It's 5000 times faster than an sequential list lookup.

It is a good discussion of radix trees, though.

Re:Demystifying Radix Trees: How Radix trees made blocking I... by jerojasro on Wednesday January 16, 2019 @03:12PM (#18924588)
This indeed should not be news. It's OK for you as a developer (even a professional one) to not know about this. You can learn it from your colleagues, debugging poor performance situations like this, etc.

But it's not OK for a company to offer a service built in such a naive way (naive from a comp-sci point of view). To me this kind of mistakes are a symptom of having a poor CTO, poor hiring/dev practices, etc.

Re:Demystifying Radix Trees: How Radix trees made blocking I... by whateveracct on Wednesday January 16, 2019 @06:43PM (#18926785)
get over yourself bub