DavidWoof

It's not mentioned because OP asked for documentaries from the last 4 years, and Hoop Dreams must be over a quarter century old at this point.

Great film though.

This is a welcome move, but I keep trying to figure out how this is going to effect Libby users (which is probably 80% of my kindle usage these day) and I can't find any info at all.

Does anyone have any idea?

I don't see any indication in this article that she's in the software or STEM industry. Glancing over the rest of her articles don't give this indication at all, nor does her feeling that she's lacking knowledge of "markets, technologies and trends".

If she were a software engineer, I'd have all sorts of advice on how to develop the skills to re-enter the job market.

Is it really all that unprofessional? We're completely missing context here. Maybe I'm just too forgiving of people's quirks, but I've definitely had people smile/chuckle when I've said my favorite language was Haskell and that's led to interesting conversations rather than uncomfortable silences. People laugh at all sorts of things for all sorts of reasons: the fact that the interviewer had any reaction at all to an obscure language seems like a positive thing to me.

And leaving when the "interview wasn't going well", makes me picture OP struggling at the whiteboard and somebody not wanting to interrupt him. Sometimes people have to leave. To me, this fits into the category of devs often being unthinking rather than actively rude, and those are completely different categories to me.

I feel like we too often ascribe malice to people for what are often just cultural differences.

So a psychologist who wrote a book condemning the original twins IQ study now publishes a paper where she purportedly refutes that study's most famous findings based on the analysis of a single set of separated twins?

Isn't this the ultimate in p-hacking? Is there any reason to draw any conclusions from a sample size of one?

That may be, but this is the first time I've heard of coc.nvim and I've used neovim for years. So I'll bookmark this and at some point I'll look into it and do some research and figure out how to configure it and compare it to competitors, but is all that really worth the very slight performance advantages we're talking about? I can't type 1000wpm after all.

Sure, VSCode is a power hog and it's slow, but I make pretty good money so the cost of a more powerful development machine is trivial compared to the opportunity cost of doing all that research. Some years I really enjoy learning all about new ways to configure vim/nvim, but I recognize that it's really not an efficient use of my time, it's just been something I do more for fun.

> The 100% full reason for me was that I had a job where I needed to SSH into our prod server

Statements like this are common, but they confuse two usages: (a) learning vi/vim well enough in order to use it in any unix environment vs. (b) using vim with a complete plugin/config suite as a primary development IDE replacement tool.

The former is IMHO an essential unix skill, but it's incredibly inefficient to try to use core out-of-the-box zero-plugin vim as a primary development tool. But once you start configuring an efficient dev environment, the GUI editors start to really outshine vim, and they still provide core vim functionality via plugins if you want it.

I could ask the opposite: why do people choose terminal vim when you can easily add nvim integration to editors like VSCode and get 98-100% of what vim gives you along with much easier configuration of all those extras you mention like autocomplete, hover reference, refactor, etc.?

That's a bit of an overstatement, because I really do love vim/nvim and nvim integration isn't that good, but the fact is that adding a feature in nvim still means researching and configuring it where in something like VSCode you open a new filetype, it asks "do you want support for this file", click yes and you're ready to go. I can spend a few days trying to get vim to work in the way I want it for a specific filetype/framework, or I can get 90% of what I want from VSCode in 30 seconds and still have vim navigation and command support.

I think that's more true in the negative sense. It's not that it attracts the "right" people, it's that it repels the "wrong" people. There plenty of clever efficient devs working in Java or JS but they're surrounded by a sea of mediocrity.

And since the interview process is imprecise the point of being broken, it's very useful to attract the right people in the first place.

The "last 3 rounds" part is obviously metaphorical. It says he used teams of observers for a month to record up to 20,000 spins, not that he literally looked at 3 spins to determine the fourth.

It all sounds unlikely in today's data-driven world, but I suppose that in European casinos a half century ago they had roulette wheels that had been in service for 80 years without any real maintenance and would show massive bias without anybody noticing.

The cumulative effect of tipping shouldn't be ignored either. Individual tips may not incentivize a server to do a better job, but the cumulative effect of tipping makes restaurant server a fairly well-paying entry-level job that attracts a very wide talent pool.

I feel this way about Haskell, and I understand why someone would feel this way about F#. No matter what language I use, I now constantly think about how to avoid side effects, how to minimize mutability, how to ensure my code flow is readable and not cluttered by irrelevancies (notice how the author keeps bringing up "noise"?). It's similar to the way that learning TDD led me to think about testability in every design regardless of language.

That's not to say that pure functional languages is the only way to these lessons, of course.

POV: Skip the list and immediately search for Erlkönig...

Found it under Transcendent, Erlkönig: Never loses its power, no matter how many times you hear it.

OK, I endorse this list.

It works on Hacker news since the vast majority of people here share the same interests. The same is true in theory on reddit, where the voters on a single subreddit share the same interests, and importantly reddit has rules against brigading to at least try to enforce that limitation.

The basic problem is whether a downvote on a cat juggling video means "this is a bad example of juggling cats" or does it mean "I don't like cat juggling"? On YouTube, it's much more likely to mean the latter, but it's the former that's actually useful.

I don't have a dog in this fight, but it's pretty revealing that RSF's concerns seem to be limited to the jailing itself and they implicitly accept that he's guilty of a serious offense and deserving of some level of punishment ("alternative measures considered in lieu of his prison sentence").

Even if one shares the RSF's concerns, and I would count myself in that group, that's a far cry from the implication that OP's article is making that the whole case is a sham.

> 1885...Two eggs, fried or boiled, accompanied by the invariable boiled potato, fetch from 10 to 15 cents; steak 15 cents; sirloin, 25 cents; plain omelet, 25 cents;

10c for two fried eggs, but 25c for a plain omelet? Did omelet mean something other other than eggs back then? Or is it that "omelet" implies cooked fresh, while boiled and fried eggs are cooked in bulk and served cold?

TLDR; Most are owned by Bob Ross, Inc., who aren't selling them currently. Also, some unknown number is in the hands of individuals who don't know they own a Bob Ross, the article is very vague about this. Not in the article, but it's actually not nearly impossible to buy one. In fact there's one on sale right now for a cool $95K at the Modern Artifacts gallery, who specializes in Bob Ross paintings.

I really, really hate this style of article. Here's a question, but before we answer it, here's 25 paragraphs of blather.

I'm roughly the same age, and while I can remember all the brick-and-mortar places I've gone to work, there was a period where I did temp work and I'm sure I couldn't name all the agencies I worked for and certainly not all the clients.

If you're younger and grew up in the gig economy, that might be much more common.

Every time I see that clip I feel obliged to point out the green shirt guy who shows up around 1:50 on the far left singing the harmony. He's essential to the richness of the sound of the chorus.

Which always leaves me wondering how common this would have been in the 1800s. Back in the days when listening to music at home meant playing it, was your average group of scalawags always going to have a few people who sang in the church choir as kids and knew things like oblique harmony?

Nobody should be writing one-off command line parsing code. If you don't want something fairly heavy like Spectre, then just pull in a lighweight library like CommandLineParser.

Not OP, and I think never using a debugger is silly, but IMO if I need a debugger to figure out a problem then I'm missing either sufficient unit tests or sufficient logging, and spending my time on that rather than in the debugger will aid future devs as well.

I do think the write/debug/edit cycle is a very, very slow way to program, and I have to admit I'm suspicious when somebody tells me they spend 90% their time in the debugger (but a lot of this is dependent on type of work).

Code coverage is an excellent tool but a terrible metric.

It's basically the lines-of-code of test driven development. It's useful as a general guide for developers, but its use as a management metric is extremely destructive.

Unit testing and TDD

Code Complete 1st edition

Maybe Domain driven design as well

I agree with this, learning Haskell was transformative for me. It changed the way I approached problems in every other language. I treat learning it as one of the 2 or 3 things that has most influenced my development skills.

But the truth is that I still don't feel comfortable writing anything more than toy apps in Haskell. I'm not really sure how to unit test things when I'm passing complex monad transformers around. I feel like I'm just guessing at best practices for arranging, say, a website of moderate complexity.

There's tons of resources for learning the language itself, but very few on actually applying it successfully to anything other than a single purpose command line app.

"Fired" and "laid off" are two different things entirely. OP was laid off, not fired, and I think it's reasonable to assume that the pandemic was the immediate cause of having to cut staff. There's really no way to give several clear warnings about that.

We're all just guessing based on partial evidence, but every time I've mentioned that people should talk up more in meetings, it has had nothing to do with their leadership skills. It's always been as part of a discussion about how they need to try to understand the bigger picture. Being able to describe your designs, and being able to articulate alternate designs, is a very important part of software development. If OP is the kind of dev who gets lost and can't contribute when the discussion becomes abstract, that's an important skill to be lacking.

And let's be honest, lots of people with 15 years experience really have 1 year of experience 15 times. It's really hard to guess at the situation based on no evidence, but I can easily see both sides here.

> But opinions of the case, by my recollection, fell along predictable racial and political lines.

Just racial. Hard to believe now, but polling on racial scandals in the 80s and 90s, including OJ, Rodney King, Goetz, etc. didn't show much difference between Republicans and Democrats.

The opposite is true now, of course. Basically the Limbaugh wing now dominates the Republican party.

Looping isn't "cheating" if you know what you're doing. But if you blindly do that from the beginning without ever learning how rhythm really works, then you're going to be lost when things get more complicated.

And the same is true of the dev who copies tons of code from stack overflow without really understanding it. When issues like thread safety of the app come up, that dev is going to be lost.

Experienced musicians choose loops and samples understanding full well the trade-offs of quantization and timbre. Experienced devs bring in libraries understanding the trade-offs. Answering the question "how well do I need to know this library before introducing it in production?" is a really, really hard problem.

In practice, I see junior devs blindly copying code that subtly won't work more than I see them writing their own DI system because of not-invented-here syndrome. But, admittedly, the latter tends to be more destructive.

I honestly can't remember a time in my career when I've looked at a codebase and thought to myself "what this dev really needs is a more thorough understanding of CPU pipelines and virtual memory". Ed Yourdon once wrote something like "No project was ever cancelled because the developer couldn't address the serial bus". I'm much more concerned with bootcamp graduates not understanding good class design or appropriate unit testing than I am about any lack in low level mechanics.

I don't know if SWE is getting better or worse, but I do think that most SWE operates on a much higher level of abstraction than it used to, and I think that's good thing.

I read it when it came out. I thought it was absolutely amazing.

At the time, I'd say that the vast majority of my computer-ish friends had read both GED and Lord of the Rings. I find it interesting that so many people here are saying they couldn't get through it.