skysight-inc/HackerNews huggingface dataset:
Agreed, I'm not a huge fan of junior/senior. What we should be talking about is inexpert/expert, which doesn't always map 1:1 with how long you've been working, or practicing. Though obviously, the longer, the more likely you learned and became more knowledgeable. But some people spend 10 years doing the same thing over and over, and that's not broadening and deepening their skills the slightest.

So in my opinion, there is two type of unreadable code, there is the code that's just plain bad, convoluted, overly complicated, like a Rube Goldberg machine. That one is often written by inexpert programmers, sometimes they are juniors, and sometimes they're senior as well. And then there is code that you personally can't read, but which is great code, simple, coherent, to the point, etc. You just haven't learned the vocabulary and grammar to understand it.
Hmmm. To me, it seems directly related.
Without auditing, driver code makes sense to me. Guessing there is a lot of vendor churn and therefore a lot of caveats to keep track of ... right up until the point the driver is obsolete and put on life support, never be looked at again.
I have. It seems like a tragedy of war, which unfortunately happens some times.

I didn’t think it was some great revelation about the US military.
I would love to see video game licenses as ERC-721 tokens that you buy and can use and move between the different digital game platforms out there. If you own the token in your wallet then the DRM or whatever system lets you play the game. If you don't own the token then no game unless you pirate it like today.

This would allow games to be purchased at many different competing stores (like you can with physical boxed games today) and also allow selling games on any market out there (again, like boxed games and ebay). It keeps all of the upsides of boxed games but since it is digital has all of the convenience of digital downloaded games.

This concept extends to all media like music, movies, etc but games seems like a great first use case. I hope someone at Valve pitches this idea.
I agree with you - specifically because you said "accept that it's going to be wonky forever".

The advantage of TODO/XXX/etc. is that you can grep for it. I look for it before committing, vim will syntax-highlight it as an error, etc.

There's no point in grepping for every possible improvement someone might have wanted to do at some point in any part of the codebase. It's much more useful immediately. (I use XXX as a marker to myself for "finish doing this before sending out code for review," specifically because it does get highlighted as unusual in vim.)

If you've got something you want to do in the future, that's totally fine, just don't put it as a code comment. File it in a bugtracker, or if you don't have a bugtracker, put it in a todo file or something and check it in. That lets you at least slice up the work by area of the code (since there is likely no contributor who is equally well-equipped to fix a TODO in any arbitrary spot in the code and equally interested) and by priority and continued relevance. If you have the luxury/curse of doing this for a paying job with scheduled, paid developers, then proper project management will eventually cut the things you never plan to do (or you can use the backlog to decide to hire more developers). Whether or not you do, it's valuable to look at a proper issue tracker, or even a text file, and say "Hm, this thing is so full of unreached improvements that maybe we should flip out and improve it" vs. "You know, this is working fine, it's worth documenting for posterity if someone comes back to this code, but it's not worth specifically calling attention to."

If someone wants to document things about how and why the code was written a certain way - including possible other ways the code could be written, but isn't - a perfectly normal code comment will do the job.
TODO, aka I have the best of intentions but I'm probably not doing this in the near future or ever, for that matter.

I'm guilty for quite a few
Scientists Put a Human Intelligence Gene into a Monkey
That's a lot of revenue! What's the cost structure? That can make all the difference in the world.
I just meant that one way to make threads "work" is to use IO, so I assumed the OP did a trick along those lines. Basically two threads can receive data or read from disk a the same time. Same thing can be accomplished with a select/epoll setup but threads would just be less lines of code.

Otherwise another trick is to identify a call which uses extensions or releases the GIL once it goes into C.
Cover art, when available, is via the Cover Art Archive API: https://coverartarchive.org/api

(The Release lookup has a `cover-art-archive` JSON object which contains information about what can be fetched from CAA.)
The point is that the practices that almost unavoidably lead to bugs in C code are not even tempting in modern C++. So, if you are interested in correctness and memory safety, stepping to modern C++ provides more value for time invested than the sum of most other choices.

Equating the two is extremely common, even by people who are certainly equipped to know better. When you feel a need to tar C++ as if it were C, you signal the weakness of your argument before you have even expressed it.
Author writes a lot but says very little.
You're right of course. I assume the OP used a trick by going via IO somehow. Though granted, it might require having a forking server to do the actual summing or using another language, which would be more than 10 lines of code
If Amazon has to enable reselling of ebooks, then surely the "used" book would have the same features.
I suspect it falls under the "discourage truthful comments" umbrella... Beware of misguided incentives.
50 Years Ago: Cargo Cults of Melanesia (1959)
> For a reader point-free is appalling and way too clever.

I used to believe this, but as I started to read more and more Haskell, I realized that I just had to get used to that style of writing Haskell. I now read it fine, in general. Learning to read point-free is a learnable skill.

Tons of non standard sigils, on the other hand, is a bane.
This article itself is about someone who is on Medicare (government-run health insurance) getting a surprise bill because the hospital has mis-assigned his procedure to the wrong category to allow them to run up the bill.

FTA: “In a feeble attempt to ameliorate the problem, Congress passed the Notice Act in 2015, which requires hospitals to inform patients of the implications of their observation status within 36 hours after observation services have been initiated. In other words, hospitals must advise patients of their observation status only after they have already incurred the expense of surgery and hospitalization.”

This type of thing seems like the most immediate problem. It makes no sense that the price can be raised 36 hours after a procedure has already begun. How is anyone supposed to negotiate that properly?

Just saying, I don’t think “capitalism” is necessarily the boogeyman here. The government itself is failing to negotiate properly with the providers when running its socialist healthcare system in this instance. (And non-government payers will run into the same problems, getting unfair bills that couldn’t be anticipated or negotiated before agreeing to the service)
>I've only had issues twice in the last 12 months, and in both cases the vendor blamed their equipment for the failure rather than me.

that's... about what I'd expect, and personally, for a twice a year event, I'm carrying a backup. (for that matter, my credit card fails a lot less than that, and I still tend to carry backup cash or another card) it just seems like it would be super awkward to eat a meal and then not be able to pay.
I think it looks a little different if you don't think of it from the perspective of how many times it was sold. Think of it from the perspective of how many times it was consumed. The first consumer's enjoys the material and the creators get paid. The second consumer enjoys the material and the creators get nothing. In your example the creators only sold it once, but in mine it was consumers twice-- two sides of the same coin, and either perspective is accurate (though I would also say both are incomplete)

The difference from physical goods is really only one of degree though: Reselling physical goods has a lot more friction, especially when compared to something like the Steam marketplace that has something like a stock market's bid/ask price, which is a much more efficient and friction-less method of price-finding and connecting buyers with sellers.
I guess that a key question is whether one can trust iOS airplane mode to fully take the phone offline.

And under what circumstances does the phone leave airplane mode, and go back online.

But even if that were solid, you'd still be ~unable to install apps that Apple doesn't provide. Unless you play the developer game, and I gather that's limited in app number, and how long they'll stay functional.
But your computer does need internet, see https://support.apple.com/en-us/HT201442

> If your computer can’t communicate with Apple's software update server, you might see one of these messages.
I think we all occasionally write code we like, but I also write code I don't like, but only the most vague idea on how to improve.
TODO is for when you know something specific that can be improved and want to document it, not just generally that nothing is perfect.
Having more options is inherently better in C++, a language designed to reward mastery. Having fewer choices is better in Go, a language designed to make onboarding a new developer easy.
This sounds like an amazing war story that I just want to hear more of. Is there any more? What's your c++ stack like?
Comparing meta-analyses and pre-registered multiple-lab replication projects
Given that interview skills have an extremely high correlation with the quality of job you are able to get, and that tech companies like competitive Leetcode style interviews, you should try competitive programming on Leetcode and elsewhere.
I use this pattern across my codebase for the "critical functionality missing" scenario:

#if DEBUG
#define TODO(msg)
#else
#define TODO(msg) #error msg
#endif

Works like a charm. I've got another PRERELEASE() macro that lets you do an unofficial preview build, but would break an official stable release.
If this ruling holds, my expectation is simply that games will sell at higher prices, or keep their original prices instead of having frequent Steam sales with deep 70-80% discounts. That would keep the after-market price higher as well, and then sellers could have more modest sales that just seek to undercut the secondary market for a few days. I also think people would be more willing to purchase at higher prices if resale were possible: I used to buy a lot more games at full $60 price when it was all physical and I resold most games a month later for 60-70% of the purchase price. I'd experiment a lot more with games I wasn't sure of. Now I only pay that much for games I know I'll like, and otherwise wait for the inevitable deep sales.

I would also not be surprised is Steam sets things up so that they collect a sizable transaction fee like the iOS app store for such transactions, and that publishers demand a cut of those proceeds as well in order to publish on the platform. In fact it would be forward-thinking of Steam to initiate that on their own. Finding a way that everyone gets what they want may be the best way forward here.
Imagine you're not carrying an id and backup cash, which many people don't.

There you go.
If you think the best answer to predicting things is to just throw a neural net at it, you should probably learn more control theory. :)

(Less flippantly - neural nets are mainly for the case where you can't effectively do manual feature engineering because your inputs are too varied and complex, you don't particularly care about the mathematical properties or guarantees of the solution, and where you don't even really know what the solution should look like [so are forced to randomly initialize a huge nonlinear system and optimize it until useful behaviors pop out]. Something like predicting path saturation would be far better suited to traditional approaches.)
Let us know when you ship your perfect alternative to Linux.
Reliable software used swapping for years. Artificially having a low virtual memory ceiling by disabling swap is just austerity for almost no benefit.

Paging into swap often has almost no perceptible effect in regular usage unless you are running software with microsecond guarantees on infrequently accessed processes (those that get swapped out).
This is stupid to the point of borderline racism. An uncharitable reading of inane journalism ascribed to an entire nationality. Fuck you very much too.
I am in the same situation. I had to stop burning the midnight oil on side projects. I just work on one now but over a much longer time horizon.
In my experience, new developers are not normally charged with determining the details of build flags, deployment systems, etc.
The AWS Lambda series (part 1)
And a lot of hate and insults to the guests on the show. If he doesn’t like them, just don’t watch it.
I feel like you're beating a strawman. Using threads to speed up IO in Python is common, and for computation heavy work the fear of the GIL is 100% justified, as your example shows.
The actual events had a very great deal to do with specific choices Churchill made and enforced, such as refusing thousands of tons of food aid offered by other countries. Crop failures cannot usually be blamed on a single official, but famines usually can. Stalin and Mao are likewise personally at fault, but for both.

Stalin could easily have rolled over most of Europe while the Allies were still mired in Holland and south/west France, and probably beat them back, too. But he chose not to. From 1939 to '44, the western front was barely a distraction to Hitler. The Battle of Britain consumed some aircraft production capacity, and not much else, but that and tank production increased every year right up until 1945. By the time the Allies actually landed in Europe, Germany had been pushed out of Russian-claimed territory, and there was no doubt about its future.
How are people finding your website? How did you get first customers to list their products?
PhantomJS back in active development with PhantomJS v3
Are we still talking about a language that protects its users from the ability to write generics?
Nice! I’ve been meaning to do this for years. Decades. But still haven’t got round to it
> prior to 1.2, the Go linker was emitting a compressed line table, and the program would decompress it upon initialization at run-time. in Go 1.2, a decision was made to pre-expand the line table in the executable file into its final format suitable for direct use at run-time, without an additional decompression step.

Sounds like a good case for a flag.
> I wrote these principles after reflecting on the content of contemporary newspapers and broadcast media and why that content disquieted me.

I agree that the principles listed are highly present in American media, especially during an election year. However:

> I really think that most Americans believe these things at a deep level.

I don't think most Americans "believe" these things, so much as these are just typical human cognitive biases that Americans succumb to. If you were to ask most Americans whether they agreed with these statements, they would say "no". But come election time those same people who answered "no" would probably go and vote for a candidate who exhibited these principles. Or given the choice to save money for the future or buy some junk on Black Friday, they would probably choose the junk.
It's not about the brace format. It's about the mentality that went into the underlying design decision. The more you look into why they did it that way [1], the more dysfunctional their decisionmaking process sounds.

Basically, while (e.g.) Python's mandated formatting style arose from Guido van Rossum's philosophy of best programming practice, Go's mandated style arose from the fact that it was easier to implement from the point of view of compiler authors who had evidently never used a lexer before, much less written one.

[1] https://stackoverflow.com/questions/17153838/why-does-golang...
Now, I'm not particularly a fan of Haskell, but I think it is disingenuous to compare it apple to apple. Most junior devs had multiple years of training in imperative OOP languages prior to joining a company. So if they join a place that uses C#, and they don't know C#, but they already know how every single feature and concept of C# works, well ya, they'll be proficient in two weeks.

Similarly, had they'd been thought functional programming, some category theory, and a bit more about type theory, etc., then they'd probably be able to ramp up to Haskell in two weeks as well.

On one hand, they come knowing all the concepts and only having to learn a syntax and tool-chain. On the other, they know none of the concepts, and have to learn them all as well as learning the tooling and syntax.
It may well be magical thinking, but magical thinking isn't synonymous with cargo cults. Cargo cults seem like a particular sort of magical thinking; a subset of magical thinking. As I understand the concept, a cargo cult is specifically characterized by one group of people superficially emulating another without understanding the underlying mechanisms in play.

If the Protestant approach to forgiveness is relating to cargo cults, perhaps it's because they witnessed Catholics talk about forgiveness and decided to adopt that aspect of the Catholic philosophy without also appreciating the importance of the Catholic concept of penance (Catholics talk about forgiveness a lot, but don't give so freely as Protestants.) So perhaps Protestants are cargo culting Catholics.

I know a few Catholics who'd probably smirk in agreement with the above, but I'm not convinced of it myself. I'm neither a Protestant nor a Catholic and although I was raised as one and grew up surrounded by the other, I never felt I understood either particularly well. So it's possible I've gotten it all wrong.
My wife.

She runs her own web/digital marketing company and is the only full-time employee (which includes time for school pick-up/drop-off). She has a few freelancers for graphic design and content writing and I help out as I can while working a full-time corporate job.

Her company revenue is over 300k/year.
I'm not sure where you are getting this definition of the purpose for warrants, but it's not based on any historical fact that I'm aware of.

The way I'm aware of history, a warrant simply allows for an individual or group to take an action on behalf of the state, specifically by statement from a judge, which would have otherwise been illegal. For some individuals and groups, specifically sworn Law Enforcement officers, they fall within warrant exceptions or broad granted "warrant authorities."

It has no relation to a suspect being notified of a warrant and there is no legal mandate to notify the suspect as far as I am aware.
Back in 1989, I had this dream that the Poqet PC would evolve into a smartphone. And that one could install Linux or *BSD on it. But no, it just died.
Interesting perspective. I don't per se disagree, but my gut feeling (that is, I have no idea if I'm right) is that the farther away from the source code those notes get the less likely they'll ever get looked at much less addressed. I think your view requires more discipline, which, of course, is what we should be striving for.
Transpiling TypeScript to ECMAScript5 using Webpack (as is done in Angular and React) seems to be how folks are solving this. It does strike me as a rather convoluted solution, but it’s a solution.
What's the advantage of throwing away context that could be useful in the future? I've taken ownership of codebases with technical debt before, and when modifying the code for something time-sensitive, I often annotate issues with the code whose solutions (usually refactoring) can't be fit into the timeline of the current project. I (or others) can then take advantage of these annotations when I have time to dedicate to refactoring, or in many cases, fit the refactoring into feature work. The fact that a portion of the design groundwork has already been done (as captured by the TODO) makes it easier to fit in the cleanup work. IME, this approach leads to much more rapid improvement of legacy codebases than your description of do-it-now-or-forget-about-it.
I don't want to brag about my skills, so I won't answer that.
'without an actionable plan, tWithout an actionable plan, the alternative is Mad Max, which Market St. has already become. he alternative is Mad Max, which Market St. has already become. '

thats called catastrophism.
>> “process failure would generally be compensated-for at a higher level”

> I don’t quite get it. What does it mean? You re-run the process at an other time? On an other machine?

I expect the commenter means whatever thing kicked off this job will detect it failed and do something about it (try it again elsewhere, log an alert triggering an admin to go provision more capacity, etc.)

Their view is that a failure is easier to troubleshoot and fix than success with intermittently anomalous characteristics.
Tragedy is a synonym for calamity

It took me a little while to figure this one out, since I've always treated the two words as synonyms (non-ironically, I hope). In case anyone else also paused at this one, a tragedy is something horrible happening because of a weakness in someone's character, whereas a calamity is just something horrible happening. The point of the principle is that victims* of the American cargo cult treat every tragedy (blame or causality) as a calamity (no blame or causality), thus losing the opportunity to reflect on their own potential responsibility.

*term used ironically, I hope
It's one thing to have a backup plan. It's another thing to downplay urgent problems like climate change because "all we have to do is start colonizing other planets".
An issue here is that statically linking against glibc is generally regarded as a poor idea and I’ve seen a couple non trivial programs that refuse to run with other libc’s.
Error: GraphQL error: connection error
They have consistently OK coffee. You could be lost in North Dakota, or roasting in New Mexico, or snowed in Wyoming- if you find a McDonald's, the coffee will be OK.

I try to support small remote gas stations & buy stuff there, but the coffee is often undrinkable.
I mean doctors. Cost of medical care is directly attributable to doctors enforcing a cartel of care availability.
> micro-aggressions

We're adults here, can we please not talk like tumblr blog posters?
That's a terrible advice. When I worked at Google, many code reviews added more TODOs because the reviewer identified a potential source of problem but also correctly decided that fixing it right there was not the best use of developers' time.

When code has potential issues, I want it to be marked with TODO which basically says "The original developer was not an idiot, but was working with limited resource and the best way to fix the issue wasn't clear then."
Two books:
1. Straight Line Leadership: https://www.goodreads.com/book/show/11556152-straight-line-l...

Still going through the chapters and it is illuminating.

2. 12 Week Year: https://www.goodreads.com/book/show/10009377-the-12-week-yea...

Some might find it very basic but I found that breaking my intentions to 3 months and tracking them has helped me see what I want and where I want to go.