skysight-inc/HackerNews huggingface dataset:
Thought the same thing, I thought this was common knowledge. But I live in the upper midwest where low D levels are common in winter, so perhaps it's just discussed here more.
I’m most excited not about the cars, but about all of the battery factories (hopefully) being spun up to meet the demand. 18650s are still relatively pricy and challenging to get cheaply without risk of a scam. Once the price-per-cell drops we can see all kinds of great innovations with batteries.

There’s some really cool easyEDA projects being designed that will let anyone build a power wall for their home. The biggest cost factor is always the batteries.
I have no idea why they disallow those. But you could email them and ask. They usually respond in a day or two.

Side note: Posteo does not allow own domains (you can only choose from the list of Posteo.* domains that the company owns). The reason for that is mentioned in their FAQ (in short, the company doesn’t want to have or store customer identifying information wherever possible).
> What is a government except as an entity to ensure people's natural rights are not infringed.

If the nation is under existential threat by a tyrannical invader and there aren't enough volunteers for an effective defense, should the government stand by and allow everyone's freedom to be lost permanently?
Yea, but seeing someone spread his asshole in a self-pleasuring manner isn't really the same as a daily parade of conspiracies and snuff videos content moderators have to deal with
If I leave Fastmail, I think I'll most likely switch to self-hosting email with Helm instead:

https://thehelm.com/

For a family of four, the annual cost would be about half of Fastmail's standard plan.
A partner to the Peter Principle, particularly with respect to managers, is the Dunning-Kruger effect: "In the field of psychology, the Dunning–Kruger effect is a cognitive bias in which people of low ability have illusory superiority and mistakenly assess their cognitive ability as greater than it is."
"But you’ve launched at 40F and it was fine, and then one day you had to launch at 35F and it was fine, and then on a particularly bad day you had to launch at 30F and you’re fine. So you normalize this deviance. You can launch down to 30F, if you really have to. But then one day you’ve missed a bunch of launch windows and it’s 28F and the overnight temperatures were 18F but you did a quick check of the designs and specs and you probably have enough safety margin to launch, so you say GO."

Now contrast this with the wiki entry "NASA managers also disregarded warnings from engineers about the dangers of launching posed by the low temperatures of that morning, and failed to adequately report these technical concerns to their superiors."
Bread was the staple food for most of that period. GP was contrasting modern and paleo diet.

It would be wiser to contrast 1918 with 2018 (and I agree with you that refined sugar and starch are most likely involved in the current mess).
Yes, sorry, the line length is indeed limited to 255 chars (or is it 252/253?)! - I guess I just meant that there are no specific additional limits on variable name lengths.

I couldn't find any evidence of a 40 char limit on BASIC II... the full length of the variable name appears to be stored and compared.
The article details that these moderators in the article were outsourced through Cognizant.
He was also smoker. He also lived in Los Alamos during its development where the cancer rates where significantly higher
> You cannot write a small MVP of a browser, an operating system, a search engine, a game engine, a 3D modeling suite, etc

I don't think that's true at all. You absolutely can and should build an MVP of all these things. You certainly could release an MVP search engine (or even a browser-based game). You probably can't hope to gain traction at large with an MVP browser or operating system, but you can start using these things internally and dogfooding them.

IMO, iterative development isn't necessarily about releasing something fast to the public, it's about rapidly building a working version that you can interact with, test properly as a whole working system and show people, so you can quickly figure out what are the most obvious issues to address and improvements to make. You can test this software internally, show it to your friends, have a small private beta or even hire testers depending on your project and budget.

This is in contrast to a more traditional/naive development model where the team isn't even trying to have a working/testable version, and instead focuses on spending weeks/months building components separately, which they hope will come together into some grand vision at the end. This approach is terrible because things likely won't come together seamlessly. The different components can fit together poorly, effort is wasted on features that weren't actually good ideas in hindsight, etc. Software projects developed this way are often late, overly complex and poorly designed.
> The entry with the name consisting of exactly one dot is the pointer to the root directory

Is it? Wasn't single-dot entry pointer to current directory since DOS 1.40?
Model Market Fit
Ah, that makes sense, then. Thanks.
Ask HN: Knee Pains, Reasons and Cure?
To All of you, as hackers, what's the best way to
1- cure and prevent knee pains
2- cure and prevent knee swelling
3- when your age is >40 or <40 (i assume treatments will be different)

Thanks
My amazon account has 2FA enabled on it.
You can have quick-and-dirty for initial release, but it's rarely practical from a maintenance perspective.

A related rule: Design software for maintenance, not initial roll-out, because maintenance is where most of the cost will likely be.

An exception may be a start-up where being first to market is of utmost importance.

Other rules:

Don't repeat yourself: factor out redundancy. However, redundancy is usually better than the wrong abstraction, which often happens because the future is harder to predict than most realize.

And Yagni: You Ain't Gonna Need It: Don't add features you don't yet need. However, make the design with an eye on likely needs. For example, if there's an 80% probability of a need for Feature X, make your code "friendly" to X if it's not much change versus no preparation. Maybe there's a more succinct way to say this.
Everyone always conveniently forgets Price's Law (derived from Lotka's Law) It states that 50% of work is done by the square root of the number of employees.

Interestingly, Price's law seems to indicate 10x developers exist because if you have 100 employees, then 10 of them do half of all the work.

This idea is particularly critical when it comes to things like layoffs. If they get scared and leave or they are let go for whatever reason, the business disproportionately suffers. Some economists believe that this brain drain has been a primary cause in the death spiral of some large companies.
Year round
I've never used a protector since my first smart phone in March 2010. I've had an iPhone 3G, a nexus 5 and a nexus 5X.

I once dropped the nexus 5 and it hit a paving slab on the corner and broke it, but it was already getting old. I'm fairly certain if it hadn't hit at that particular angle it would have been fine as I occasionally drop my phone from time to time.

I have seen multiple friends with shattered screens though (still working), so I think it depends on you. One friend had a habit of putting his phone on top of the toilet when he went to the loo, and more than once had to fish it out. It really depends on your habits, care and clumsiness with your phones.
I have a very old Thinkpad X40 convertible which I use occasionally as pretty much a dumb terminal. It runs the latest i386 version of xubuntu. CPU is a single core Pentium M something, 1.5GB of RAM, 40GB hard drive.

https://www.thinkwiki.org/wiki/Category:X40

It works totally fine for SSH sessions and a web browser interface to not-very-complicated intranet tools accessed via a VPN, such as ticketing system, network monitoring software, etc.

If I want to leave a monitoring display of something running, I fullscreen it in a browser, rotate the thing into its tablet mode and prop it up against something on my desk.
Aside from the working overtime part, what sounds dysfunctional?
More or less, yeah.

It's not as directly defensive as salary hiding, which can obviously help conceal everything from wage collusion to Ledbetter v. Goodyear style inequities. But it still stops labor from sharing information and helping to share in concessions.

I didn't include it above, but a related part is that layering on NDAs makes it harder for non-employees to get involved. If you post your whole contract online, a random employment lawyer might happen by and go "hey, you're getting screwed, 3.A.ii is non-standard and probably illegal". But if you restrict it to employee viewing and low-specificity discussions, you're less likely to have lawyers or activists get involved unprompted.
> They put their passwords in their wallet and in their phone.

The author is underplaying the problem here. There were tests that showed burns through the o-rings and the reports rationalized the danger-- not by normalization of deviance but through deceptive language.

It's a lot more like having an audit that shows that no users were observed writing a password on a sheet and putting it in their wallet. And since extant passwords sheets stored in wallets don't match an idiosyncratic definition of "written down" they pass the audit.

That's not to say that normalization of deviance didn't happen. Obviously both it and a more direct type of corruption happened. But I get the sense the author here is trying to cram everything into the former to make a tractable problem out of a messy political situation.
Weather.com needs to properly size images
Backups ..or generically tarballs/zips/..etc. There have been way too many times I've had to split zips/tarballs etc just to copy over stuff over a fat formatted usb disk. Of course I no longer do that but there was a brief period when this was a problem.
The engineering problem of A/B testing
How to display random anime faces with neural networks
Poor people generally can't afford to live within bike or moped or good transit distance to work.

A schoolteacher living in North Bend isn't going to moped 30 miles down a freeway to get to her workplace in Seattle.
Eventually all artificial lights that don’t help with vitamin D deficiency should be banned.
I put in "software engineer" and got 'technologyologist'... which feels right!
And that happened to people with private insurance (SF General was “out of network” for the two examples.) But upwards of $20 thousand for very simple things is outrageous,

This has to become a national effort to curb these exploitative and unfair billing practices. It’s simply outrageous.
I don't agree with that quote being used to define software rot, and I don't think the examples illustrate rot either. I'm just fundamentally opposed to the terminology of the rotting metaphor when it's applied to projects that receive active upkeep, even if the project drifts further from its original scope and vision. For that, we need a name for that that alludes to scope creep and refactoring, but one that isn't suggestive of decomposition at the mercy of the environment of things immobile and abandoned.

I've always understood software rot to refer only to cases where the dependencies, including libraries and platform APIs, are changed so that an already-delivered copy of the software can no longer function, and the maintainers have since abandoned it, or can't do a quick fix to get it working again.

A recent example is the removal of support for NPAPI plugins in Firefox [1] in 2017. Firefox is in the role of the 'platform API' here, and this change of theirs broke any extension that didn't update. And, the replacement API differs in features, so the effort of updating an extension approaches that of a rewrite.

Another example is the game 'Star Wars Episode I: Racer', the podracing game from 1999. Newer versions of Windows and DirectX have changed things so that the game's original executable doesn't run [2].

Even open source isn't a remedy. Random projects one can find on a source repo, last updated x years ago, are code that are susceptible to this. Sometimes they're shipped without dependency management, pinned to old versions that themselves no longer work, or track the latest when they should be pinned instead. If more work is required to get it running than just the instructions provided by the author (assuming those were sufficient at some point), then it has suffered software rot.

[1] https://support.mozilla.org/en-US/kb/npapi-plugins [2] https://www.play-old-pc-games.com/2013/12/02/star-wars-episo...
I've been using pug with the babel plugin for a React project, and I really like it. I'm a fan of Haml for server-side rendered Rails views, too. I'm surprised pug isn't more widely used in front-end dev, since it is so popular in Node apps.

Also: projects are still using the "jade" name? I thought they were forced to change?
Whether relevant things fit into L1 cache will make an order of magnitude more difference than whether you're using a nominally 2-cycle or 4-cycle assembly instruction. I don't believe any human programmer on a modern CPU is able to keep track of what cache level their code operates at entirely in their head; certainly such a human would not be thinking in terms of x86 assembly or normal language stdlib functions. So attempting to execute the code in one's head is overwhelmingly likely to be a waste of time.
It's not useful to use the same term for very different kinds of things. Shared resource deadlocks are common and disastrous problems. Share nothing mutual blocking is uncommon, not necessarily a problem at all and can be completely harmless and automatically recovered when it is a problem. For example, spawning actors to wait without timeouts would be absolutely ok, parent can do all the timeouting and kill the children.

Two processes blocking on a socket is not a deadlock. Surely there are timeouts on both sides, because using sockets without timeouts is just ignorance, and both will just timeout and move on.

Also strictly statically declared event handlers per actor are 100% mutual blocking and deadlock free. Because they can't wait for messages in a way, that blocks other event handlers.
A mutant variation of this: Greencodd's Rule: "Every sufficiently complex application/language/tool will either have to use a database or reinvent one the hard way." (from c2.com)
https://unanimous.ai/what-is-si/
Scientific datasets, for one.
LED lights safer, more effective in producing Vitamin D3 than sunlight (2017)
> Interestingly, Price's law seems to indicate 10x developers exist because if you have 100 employees, then 10 of them do half of all the work.

Or 0.1x developers exist...
Technically, STM requires that you're not updating your state via side effects. That's a different proposition from requiring your functions to be pure. For example, you could have a function with a print statement inside your STM transaction just fine.
Times Michio Kaku Blew Our Minds
You deserve what you’ve achieved. You are not a fraud
That time a CEO complained to Congress about Windows file extensions
If you can make this a tolerable experience on the Oculus Go, it should only get better from there. After using several VR setups (including the Go), I think it might just hit the baseline sweet spot of affordability, ease of use and performance-- with the latter obviously being the biggest concern.

You might want to consider throwing in a quick check on internet speed & latency at the user's location, and simply not allow them to connect if it's not up to a certain level (or gracefully degrade the experience to a lower-bandwidth, more latency-tolerant secondary UI).
/tpg/ on /g/ is probably my favorite aspect of 4chan besides /prog/

Thinkpads are wonderful machines with lots of upgrade options. A T61 with an SSD and ram upgrade is quite usable for most everything except high quality video playback .Performance on win10 is ram dependent but with i3 and debian installed ram usage at idle is so so so low (sub gig)
That's pretty much the opposite problem of what the GP is asking about.
Iterative is the key insight ( and main value ) of methodologies such as Agile and XP. It is essential in projects where fantastically detailed requirements aren't known in advance (i.e. any non-trivial project).
In short, no. It is based on the experience of 3 former CIA officers and theories and methodology one of them has developed as a result.
Do you have the website? Get different results searching for Bookworms podcasts
AR Boosts Email Marketing Engagement 75%
Huge fan of Geoff's post. His X62 post is what inspired to build my own. Though we should probably put a 2017 year stamp on the title.
I'm pretty sure the papers took it into account. I still cannot find the things, but they mostly were talking about non-Vietnam troops. I remember Germany being mentioned.

I'm well aware of Vietnam as it didn't go too well for some of my relatives.
This is a common trait of new parents. It weans off; quickly for most.
Not surprising, I use a 2018 mbp at work yet prefer my thinkpad x220 which came out in 2011.
I'm genuinely surprised it doesn't have a touchpad. I don't think I've ever seen a laptop without one, and I used laptops back in the early/mid 90's.
Billion Dollar Unicorns: Qualys Acquires 1Mby1M Company Adya
> if you broadcast clearly that undocumented behaviors are subject to change, then users can decide if they want to accept that risk

That sounds nice in theory, but doesn't really work in practice. If you're building infra and a core piece of your company's product relies on these undocumented behaviors, you can't just change the behavior and shrug your shoulders when the whole product breaks. Similar if you're providing an external API to users/customers, you can't just break their stuff without worrying about it.
Here lies humanity, they tried to do the same things 15 different ways and squandered their resources doing so.

(Not saying you’re advocating for this, just that it is the current plan it seems)
Tunable Neural Nets
I thought there is a great level of control over these and none of these run Minix and connect to the network. The actual functionality that ME is supposed to provide is purposeful.
I learned to program from old books a coworker of my dad’s gave me. Some of my favorites were two books of computer games, where you would type in the code word for word.

Each line would have symbols that told you which versions of basic used that line, so there would be duplicate lines for different versions of basic. They didn’t have the version I had, so I had to figure out the differences on my own.

I learned so much.
Will I be able to disable SIP when I need to?
I disagree. In my experience, direct coordination on interfaces tends to create unnecessary special cases (hey, can you add this field to your API, just for us?) which add complexity and make maintenance more difficult down the line.

The main advantage of distributed system, and particularly microservices, is the ability to have each system completely independent: individual components can be written in different languages, running on different platforms and use completely independent internal components. Basically, it is just like using an external library, component or service: the authors provide documentation and interfaces, and you should be able to expect it to behave as advertised.
> And yet for any but toy-level (and logic/relational math research) programming, you have to pay attention to how it works under the hood.

Maybe 30 years ago. It's really not so important nowadays. Computers are fast.

> For practical use of SQL, you need to be able to choose between equivalent queries based on how the database engine actually turns them into lookups.

Maybe there are some cases where you need to, but there are also million-dollar businesses that have succeeded while only ever writing their SQL queries as naively as possible. The notion that all non-toy practical uses need to understand such low-level details is just utterly false.
Variation 2: If you factor duplication heavily and go ultra-meta, you'll end up with Lisp or a clone of Lisp. However, only Lisps fans will be able to understand the code.
This is a great opportunity to encourage everyone to delete your facebook & Instagram.
I assume any extension that consists solely of any combination of \x00 and \x20 is to be understood as "no extension"
HoloLens for Good, Not for War
Electric scooters can be hijacked remotely – no password required
Resolving to be more open in 2019
ExpressVPN is the best.
> No, it's not, it's a subset of physical illness. It's not even possible for it to be otherwise without magic.

I think GP's point is that you can't determine a mental illness with physical characteristics/measurements. Can you diagnose schizophrenia with a blood test? X-Rays? Nope. Perhaps an MRI? Maybe, though AFAIK this still isn't really possible.

With physical illnesses it's easy. Broken bone. Cancer. Viral infection. All of these can be diagnosed without communicating to the patient at all, simply by making physical observations using chemistry and physics.

Not so with mental illness. With mental illness you basically have to just talk to the patient, take their word at face value, and then deduce based on symptom pattern matching. A determined fraudster could fake a mental illness, and it would be impossible for doctors to be able to tell AFAIK (correct me if I'm wrong), the same which cannot be said for tumors.
I wish I could remember the title and author, but this reminds me of an (unrelated) book on pain management, where the author's thesis is that most musculoskeletal pain is psychosomatic: you can essentially will yourself out of chronic pain once you accept this statement as fact. Does anyone recall the book I'm talking about?
Are you saying that there aren't enough people cleaning up or that cleaning up should be done differently?
I think experiencing that kind of behavior is what led Joel Spolsky to write about how you should never rewrite something from scratch
https://www.joelonsoftware.com/2000/04/06/things-you-should-...
+1 for Quiet. Great book.
I think this argument has been being made by people for two thousand years (this generation is too soft! Uphill both ways in the snow!) but I've yet to see a causation demonstrated.
I'm not sure I understand what you think is incorrect; your explanation seems to align with the common interpretation.

Here's the article I was thinking of. Totally worth the read, aside from discussion of Murphy's Law...

https://www.theatlantic.com/magazine/archive/1998/03/the-les...

"Keep in mind that it is also competitive, and that if one of its purposes is to make money, the other is to move the public through thin air cheaply and at high speed. Safety is never first, and it never will be, but for obvious reasons it is a necessary part of the venture. Risk is a part too, but on the everyday level of practical compromises and small decisions—the building blocks of this ambitious enterprise—the view of risk is usually obscured. The people involved do not consciously trade safety for money or convenience, but they inevitably make a lot of bad little choices. They get away with those choices because, as Perrow says, Murphy's Law is wrong—what can go wrong usually goes right. But then one day a few of the bad little choices come together, and circumstances take an airplane down. Who, then, is really to blame?"

Of course, regardless of which way you interpret Murphy's law, the law itself and this alternative are both hyperbolic exaggerations. The main question is more of which way of looking at it is more useful.

In terms of thinking about safety, it seems like both points of view have something important to say about why paying attention to unlikely events is critical.