skysight-inc/HackerNews huggingface dataset:
https://news.ycombinator.com/item?id=22391092
A super long article to identify the really obvious?

- People who grew up with Lego over time are now adults and still a market.

- Lego can serve this new market as well as the original market which still exists.
Sirius I found deeply moving and quite different from his more cosmic novels: https://en.wikipedia.org/wiki/Sirius_(novel)
And now they blame Russia for supporting Bernie, it is becoming a bit redundant. Just let whoever want to post, people don't make up their mind because of some bot posts and there are always ways to manipulate the media
The big networks are doing it every day pushing their own agendas to the people, why can't other countries or candidates or whoever do the same thing? Are CNN or Fox are above us that they get the right to do it while the rest of us can't?
>The /real/ question is this: should software be a factory job?

It has all of it: creative jobs, theoretical jobs, and factory-like jobs. White collar and blue collar jobs at the same time.

What we suck at is admitting which jobs are which types and assigning the labor accordingly (as well as setting targets).
There usually is if we’re not scrambling to do too much too late. Again, was a huge miss.
Abstraction can be good. But this reliance on abstraction that does nothing but obscure problems is a weakness of modern software development. And now we're left with no one who can solve them.
I've used several of different brands ones while debugging PCIe NICs, and they are mostly tricky to set up (like sometimes hours or days of fiddling to get a link at the right speed / width).

But once setup, they are incredibly informative.

The last time I used one was ~2015, and it was not nearly as nice as wireshark
Not to mention the huge gap between supply and demand with respect to CS graduates and jobs. It’s really frustrating to hear so many new grads are struggling to get hired despite the gigantic investment in CSE. Articles like these point to the failure of the evaluation process as a bottleneck versus the common understanding that supply is limited.
> There are a lot of anecdotes like that, but the statistics I've seen has clear correlation between performance on algorithm interviews and performance on the job.

I can only claim to have personal anecdotes, but the critiques I hear and have are things like asking you to write Bash on a whiteboard an focusing on minor syntax errors (Bash was not the primary language for the job and the candidate was obviously familiar with the language). Or asking about details from compiled languages when the job exclusively dealt an interpreted language. I'm not saying these interviews shouldn't touch on these topics. I do like to see how deep a candidates knowledge goes (sometimes it can mean they're over qualified and would be bored).

I'm not sure if it's interviewers showing off, because they've "always done it this way," or what, but I often see both job posting criteria and interviews focus too much on things well beyond what the job requires.

Of course, I'm biased and think my way is better. Outside of the minimum requirements for the job I never really care if a candidate has an answer to most questions. In fact, when they get it too quickly it seems rehearsed and I don't think it reflects their skill. For me, the technical questions are a starting point to see them talk through how they approach the problem.
This is absolutely correct, and so is parent. Like any ambitious endeavor, done well it leads to success, and done poorly to disaster.
I'm sad that Norway stopped publishing all tax return lists (ie, taxable income).

The information is still available, but rate limited, and the person you look up will get a notification. So you can still look up last year's tax return of the person offering you a job - but that person might take offense.

That said, there are a couple of good reasons for the change; digital publication is qualitatively different from having to go down to the city administration to look up the numbers on paper - among other things it makes collecting/checking date of birth trivial (it's part of the dataset - which is municipality of residence, full name and dob).
How to Deflect an Asteroid
Partner does most of weekend and evenings childcare?
Another perspective to consider as well: while you are spending the time investing into and training people who needs the training and investment, your competitors are throwing money luring away the ones you have already trained, and leaving you in the dust in terms of velocity.

Turtles all the way down. Once a game shifts into zero-sum, it's not gonna stop getting played until it collapses.

Normally, I would say to avoid entering into any zero-sum games. But the world has made a sharp turn towards zero-sum over the past 5 years, so that advice has rapidly become impractical in today's climate.
I have always hated software engineering interviews. This is a popular topic on this site, but nothing ever changes. Not sure as I would call them dystopian, I generally thought they were a chance for a senior dev to parade his ego. I could tell stories... (As I'm sure everybody else...)

I used to take interviews and I always knew the outcome. "Sorry you are self taught, we only want people with CS degrees." "Or you don't know how to reverse a list." "You don't know what a bubble algorithm is" Why did I keep punching myself in the face?

Well I decided to make a change in the last 6 months, I wanted off the hill, the ski lift or what ever ski metaphors your want to use. It's summer and I'm going surfing. (also we both live in Colorado, it's getting little crowded on the hill and the traffic to the slope is bad.)

I changed my attack, why was I interviewing for these horrible jobs that I really didn't want anyway. So I changed my pitch.

I now write algorithms for futures/stocks/options, I work for a company that have a ownership stake in. My code is good, but it might not perfect. No ego or code reviews. Because the true worth of my code is not how many classes I use it whether it returns profits. I didn't get into coding to so I could debate OOP structure or MVC models. I write code so I can make a ridiculous amount of money. Nothing more or nothing less. The code is just means to make more money.

Enjoy the lift ride, but I'm going to Hawaii.
IMO if you're coming to Go from Node.js, you're much better off spending the extra time learning `net/http` (which is much more idiomatic and will teach you a lot about the language itself) than clinging onto impedance-mismatched patterns from Node.js.

This project is full of `interface{}` (sacrificing type safety for cuteness and magic), has a very weird prefork system (which actually breaks Go's concurrency model) and doesn't even use godoc (which is one of the nicest developer productivity aspects of Go). I would say it can do more harm than good to people new to Go.
Instructions to enable Xcode 11 internal debugging menu
I want to first say, I have a great amount of respect for Netflix's engineering and for Atlas itself, it's great that it exists and is more accessible than other scalable in-memory TSDBs open sourced by large companies.

A few of my thoughts on this, and this has come up before. Firstly Netflix self-identifies it is expensive to run an in-memory TSDB for metrics - for instance Roy's talk on Atlas mentions this as such[0] at the 37min mark of his Operations Engineering talk "It scales kind of efficiently. I'd love to say efficiently instead of efficiently-ish however that's hard to claim when my platform until this last quarter cost Netflix more than any other element of the cloud ecosystem ... Atlas and the associated telemetry costs Netflix 100s of thousands of dollars a week". At Uber M3 cost a significant amount to run as well at first and that is why M3DB was born to drive down that cost as much as it could and still provide a ton of instrumentation to engineers. Either way, giving engineers tons of room to instrument their code will result in a high cost no matter what since it will be viewed as a free lunch, that is why squeezing the economics on this matters since you want to provide as much instrumentation as possible at the lowest cost.

Regarding your points about their documentation on cost:

1) Yes reducing cardinality by dropping node dimension on metrics, etc is possible to save cost - but also keeping things on disk is an alternate and great way to save cost too and keep the data at high fidelity. The challenge is making on disk lookup fast too, which with M3DB is what we were focused on doing.

2) Dropping replication of the data to a single replica is another way to save cost, however also comes with operational complexity as now you need to do backup/restore if you lose data and lose the ability to query that data in the meantime. This is why M3DB always is recommended (as per documentation) to run at RF=3 with quorum reads and writes so losing a single machine does not impact the availability of your operational monitoring and alerting platform.

3) Regarding rollups and tail solutions accurate, we always push for people to use histograms as that can be aggregated over any arbitrary time window and across time series. T-Digests are much more expensive to store raw and aggregate later. Bjorn talked about histograms, their use in Prometheus at FOSDEM[1] and why they're more desirable than t-digests or other similar aggregations.

[0]: https://www.infoq.com/presentations/netflix-monitoring-syste... (video, quote is at 37minutes in)

[1]: https://fosdem.org/2020/schedule/event/histograms/ (slides and videos)
It's pretty obvious that Bloomberg is not running for his direct enrichment. He has a record as mayor of NYC for 12 years. The most nefarious notion you could come up with, while keeping your head grounded in reality, is self-aggrandizement.
Seeing that in over 20 years and very successful track record of getting jobs quickly that I’ve never done leetCode or had an algorithm interview - how did you get that out of anything that I said?

I’ve met “junior developers” who couldn’t translate simple business requirements into code.

The stereotypical “developer” who couldn’t do FizzBuzz.
No math, sadly.
She's just giving a little bit of context of where she’s coming from.
It is relatively common for companies to not use open source for this type of application above a certain scale, even if they use open source for most other things. I've seen it happen at multiple companies big and small. There are two major reasons for this.

The first reason is that open source platforms struggle beyond a certain scale due to architectural weaknesses, which becomes an ongoing operational headache. Most companies just deal with it but it gets worse as the workload grows.

The second reason is that it is expensive to run the open source platforms due to their very low efficiency. I've seen companies reduce their hardware footprint by a factor of 10 by rolling their own metrics/time-series implementations due solely to superior software design. When you are running a petabyte of metrics per day through these systems, that adds up to a lot of money.

tl;dr: it is technically straightforward for a company to design their own metrics infrastructure that massively outperforms the open source tooling, and the limitations of the open source implementations are often painful enough as the data models scale up that many companies do.
I would call market prices more “consensus” than “objective”, since they’re based on the aggregate subjective valuations of those involved in the market.
There's been a shortage in the Bay Area, too.
This and above comment: what is the purpose?
The closest to a standard (and only for FAANG) is Cracking the Coding Interview, but even that is a large pool of questions to keep in one's head far above what you're likely to do on the job.
It's pretty standardized. 99% of the questions you could possibly be asked are on leetcode for most large companies.
The way the (very briefly described) question was asked does sound like a clever way of getting some ideas about candidate views and beliefs.
Not M3 specific, this the summary in a nutshell. If you need both scale/performance and operational cost efficiency at the same time, there is not much in open source for you.
Except programming and engineering is about overcoming the unexpected. Adapt and improvise. Not everything is textbook and, at least this is my opinion, the better engineer is the one that can solve unexpected problems. You can really only judge that utilizing past experience. Canned, standardized questions similar to Mensa intelligence questions or any type of "brain-twister" puzzle are pretty crappy. Once you know the tricks they're applying to the question, they're easy to solve. But that's not the same as actually "figuring out" a real world problem.
Hack the Planet: Leaks, Glitches, and Preposterous Futures
Thank you, this is really interesting. Never considered the absoluteness of rotation before.
In my experience a great way to hire and train juniors is to have them do tasks that need to be done but you can’t over allocate or reallocate an existing engineer for it. Like refactoring existing code.

Why? The only guidance then a more senior engineer would need to give is during code review and where they may have questions. It’s a great way to get them familiar with the code base and train them up. I haven’t seen this be a productivity killer.

Also, with the shocking frequency I’ve seen, code based need more tests. Have them write tests! That’s a fast way to get up to speed.

One other point: senior engineers in one code base may have an uptick if a “junior” in another depending on existing quality, circumstances etc.

I think organizations are lying to themselves that they can only hire seniors. It’s a myth. Just like 10x developers.

I need hard data to be convinced otherwise not anecdotal evidence. All the hard data I’ve seen points in the opposite direction of any anecdotal information I’ve come across.

There are so many volumes of books devoted to these topics alone that I think most ideas around developer productivity without the firm backing of numbers are mostly hand wavy and myths we tell our selves to feel better
Maybe so but what the parent comment is suggesting is that we do not have a democratic process. Maybe it's possible to do this as just a constitutional amendment instead of a constitutional convention. I think that's even less likely to succeed.
Friend Links for Medium – All my posts to the end of 2019
Thanks for details! Really appreciate it.

> It also uses a magnitude of storage space less than raw prometheus

AFAIK, Prometheus compression is about 1.2-3 bytes per datapoint. A magnitude less is 0.12-0.3 bytes - are these numbers correct?
Feels to me it would be in company's interest only if the salaries were more transparent. Otherwise company will pay as little as they can to keep the person working for them, even if that's well below the value the employee delivers. If the employee doesn't realize that, they'll just stay. And as long as the company doesn't lose good employees, there's no incentive for them to pay people more.
I was hoping that the ISAs would fix the worthless-classes problem. My theory was that if the institution's compensation was more directly tied to how much they helped the student, they'd be better at helping students.

Unfortunately, there's still a fundamental broken feedback loop here: the people purchasing an education are definitionally unqualified to evaluate it. I don't see a way to fix that without significant regulation, which unfortunately acts as a brake on evolution of both program content and educational methods.
I understand the idea behind it, I just don't think "not choking when asked to code in a stressful situation" correlates well to "being able to design and write functional and maintainable software that maps well to customer and company needs".

If the devs at your company need to put out fires constantly, then maybe it's a good test of whether they'll be able to do that.
I think "don't be an asshole" is a pretty good rule of thumb.
That sounds like a lot of work to oppress a few programmers.

If you want to be a dick and systematically screw people, just hire an army of agency contractors in some out of the way place.
Do you maybe have an extra zero typo in that number?
How to disable all security checks for the login process to my Google account?
Google keeps locking me out of my accounts because they don't recognize the device (I don't let them track me as much as they would like, I guess)... A login and password is sufficient for most of my accounts.
How many school graduates will end up studying quantum mechanics?
Ok, but why is that a bad thing for engineers that are interviewing?

If the interview process is largely memorizing 200 or so commonly asked algorithm questions and that is the gateway to a $200k+ job then it's a good thing for applicants, not "dystopian" at all.

Again, it would be much, much more painful and time consuming for the interviewee if they were asked to code up some fullstack project for every interview. That is far more time consuming, and in my opinion more "dystopian" to expect those interviewing to do dozens of hours of work specific to one interview for free.
This is incomprehensible for me. If someone happen to see your question before it is bad sign? And also, what exactly about my internal process are people trying to learn from "how I approach a problem and work through it"?

I think I tend to make good impression on these ... but I am aware it is interview skill where I somehow picked up social signals I am supposed to send. I am adjusting what I am saying to how interviewer looks like (happy, annoyed, bored, etc). It is social skill, but not same social skill as pretty much anything I do in actual work. In actual work, people are not interested to listen to me work out problems in front of them.

It is even more useless if you know the answer and then proceed pretend to split it into smaller problems and then work your way up or down. That neat thought process is neat precisely because I know the answer and I am performing idealized problem solving process.

In case of actual real problem, you don't do that so nicely. You have at least some bad turns, random guesses, break it multiple times badly and so on.
can a web app play music and run js with the screen off?
The evidence you supplied suggests that "this kind of people" can tell what's really important from things that are not (either outright fads or not applicable for this particular business), and they have a track record to show for it.

This was a great opportunity for you to re-examine your beliefs in, for example, necessity of QA [1], and learn when and how to save a lot of time by not writing tests yet achieve business goals for stability and continuity. Instead the lesson you took from it was "20 years of experience - the same year repeated 20 times".

[1] It's not too late though, the knowledge is out there
Because she think its important, she can write however she want.
I'm aware of only one public benchmark including some competitors - https://promcon.io/2019-munich/talks/remote-write-storage-wa...
Would like to see more of this.
For anyone else wondering ... an ISA is an Income Share Agreement. Lots of comments here mentioning this but I didn’t know what it stood for
Despite your (and many others in this thread) assertion, this is fundamentally new because it hasn't previously been done in political campaigns in any meaningful scale.

The mere existence of a few private campaigns of the sort doen't diminish how much of a departure this is with what has previously been considered acceptable in the political realm.

If we assume that the widespread every-politician-is-corrupt cynicism goes along with/is rooted in a wish to see less corruption, you are also applying rather harmful tactics: by claiming everyone plays dirty, any differences between the candidates are erased, and so are any incentives to behave ethically. The cynicism is self-fulfilling: politicians only ever getting superficial accusations with no discernable relation to their actual behaviour will soon stop trying, because why bother?
I think it would have to start as a smaller movement on the local level, which (assuming it had positive outcomes) would eventually grow into a nationwide idea.
Lots of these comments seem confused about the purpose of this. It's not about using linked lists (that's easy, they're in std::collections), it's about implementing them. So the common non-kernel/embedded use cases are well supported, just use std::collections::LinkedList! But if you're in a no-std context then you might need this.
But this is just stupidity. Does exist also a lot in the western world, but I don't see, how that can improved with restricting information flow?
Indeed! This cultural / historical angle of looking at the issue hits the nail on the head.
It has been done, I've seen the numbers and they work. Other companies have probably done the same. Of course this isn't popular, instead people up-vote anecdotes from people who say that they once had an algorithm wiz who performed badly, or how some stellar performers were rejected by this kind of interview.
It doesn't seem to be all fakers. The situation as described by advocates of FizzBuzz and the like, is that large minority proportions of people who have already held down jobs in the software development field, actually can barely do things that we think of as basic programming, like implement a very straightforward function. The implication seems to be that there's just too many to all be actual liars; that they're doing some kind of cargo-cult, cut-and-paste, stack-overflow based work to keep themselves in a job, changing things by tweaking them but not actually capable of anything else.

It seems implausible. It's counter-intuitive. But the idea seems pretty persistent.

It's an interesting question for me personally. I'm a mechanical engineer who likes to program a little and I've sometimes wondered whether I could work as a programmer. I haven't got the right qualifications or experience with enough popular technologies, so moving fields would be tough. But I know I can implement basic things from scratch. It doesn't seem like much (and clearly it wouldn't be enough for the prestigious places with really tough computer science interviews) but it would be interesting to know if that actually was enough to clear a certain low bar of competence.
> What we suck at is admitting which jobs are which types and assigning the labor accordingly (as well as setting targets).

Huh, never thought about it that way. That's a very useful perspective. I will start incorporating it going forward.
I presume you're referring to the value of retaining employees?

I'd be curious to see an economist take a look at what's going on here. The software-development profession continues to incentivise employees to constantly change jobs, despite that employers pay a real 'onboarding penalty' for employee churn.

If someone knows the answer I'd be interested to hear it.

> as much as is consistent with the value the employees deliver

But what does that mean? If an employee delivers $100,000/year of value, how how much should you pay them? Surely the answer (regarding the employer's self-interest) should factor in the odds of them leaving at any given pay-grade. The answer presumably isn't $99,999. The employer is looking to 'capture value', after all.
Click Here to Kill Everybody: Security and Survival in a Hyper-Connected World
AKA "rush to keyboard" syndrome.
The second one there isn't as bad as it looks in the photo. The main hull is made up of many separate pieces, as is visible in the instructions.[1]

[1] https://www.lego.com/biassets/bi/4493625.pdf