skysight-inc/HackerNews huggingface dataset:
Once I got past the slow start, I quite liked it. But the first time I played it (rental, IIRC) I didn't care enough to get past that part.

The second time I played it (bought, for Wii U) I didn't get any further.

But the third time I finally decided it was time to get somewhere in that game, and I ended up playing it until I beat it, over a couple weeks.

I'm still debating whether I care enough about Skyward Sword to deal with the idiotic controls.
You can't get 9 women together and produce a baby in 1 month. A lot of developments within a programming language ecosystem originate from new ideas discovered outside of it. It doesn't matter how many people you have working on a project if the crucial piece of tech they need hasn't been discovered yet.
Did you try PyPy? If so, how did it perform? If not, why not? PyPy adoption is at only 1% or so, and it'd be nice to see more PyPy usage.
Yes. Yes, that is exactly what I'm saying.
My personal suspicion is that the problem there wasn't OOP, it was frameworks.
Cybersecurity Breaches Cost UK Firms £30B in 2016, Says New Research
Unless I'm missing something he got approval for 2 weeks to dig in ... doesn't say how long the entire project took (typically something like this would be a part-time task while working on immediate team/game needs).
Fantastic work though and wonderful that insomniac have open sourced it.
I personally wish that more schools taught this kind of stuff.

But at the same time, most of those things on that list many people would consider "obvious", but when the deadline starts getting close they start slipping (because shipping on time is more important than some stupid logging shit!).

Then before you know it you are a month after launch and you are drowning trying to figure out what the damn emails mean when they just say "The app won't work" and your boss is still pissed from the deploy you did a week ago that ended up taking over an hour because you never tested the restore system, and every few days you get a report of the whole thing crashing but you have no idea where, why, on what platform, or anything about it.

That's the kind of "lesson" that I ended up learning. Pushing the ship date back a week or 2 isn't really that big of a deal in 99% of cases. And having good ops in place, a healthy amount of testing and support code, and some nice documentation doesn't take that long if it's done at the start, and can save you a LOT of time and grief in the not-so-long run.
That's the wrong way of looking at it. Question why people are like that. Humans aren't infatuated with their work by some corporate conspiracy. Work has always defined the individual. Look at the history and origins of family names.
I can't speak for the UK, but in the US, if you go to anything other than a luxury boutique, they will jump all over you for a $7k sale. That customer may change their mind or take the sale elsewhere if you put them off for 90m.
> I also teach Web dev. We use MAMP which is cross platform. We install VSCode, interact with the FS, create a local DB, file uploads, programmatic image resizing etc. My understanding is that this is not possible without jailbreaking (is that the right term?) a Chromebook.

Sure, you can't do that locally on a Chromebook without breaking out of the default system paradigm (I'm not sure it's technically jailbreaking, but that's not really important to the point.)

OTOH, if you aren't attached to locality, you can do most of it from a Chromebook without doing that, if you are running appropriate software on the backend to support it (e.g., for pretty much all but the "install VSCode" part, running something like Eclipse Che.)
Or this footnote:

1 Eficient in the same sense as ML: tends to run fast, but with some effort pathological cases can be constructed.
Considering that banks use poor customers as a source of fees to make money, the GP comment is spot on. They've regained control, and honestly your "just check a thing once a month" is hardly the kind of visceral knowledge from watching your wallet get thinner as the month goes on.
Windows exposes personalities above the kernel, in the NT days that meant OS/2 1.x, POSIX and Win32.

Nowadays on Windows 10 it means UWP, Win32 and Linux syscalls.

In theory someone could call the ntdll.dll and create a new personality but those APIs are undocumented and only possibly made available to Microsoft partners.
Ethereum is ASIC-resistant, so GPUs are as good as it gets, at least at the moment.
Ruan writes in his book in chapter 4 "The Engine: Safeguarding Itself before Safeguarding Others":

"In addition, there is a basic guideline for realizing security: Never rely on security through obscurity. When designing security hardening features for the engine, it is always assumed that all firmware source code and internal architecture documentation may be obtained by attackers. The engine’s security design principle is to harden the product by applying proven cryptography and security primitives, rather than rely on hiding secrets in the code or documents."

So they cast their secrets in silicon I guess, which would be incomparably harder to recover.
Tried bose qc2 but got rid of them because of the "anti-noise" "pressure" giving me a headache after a few hours. They constantly pump sound meant to cancel the ambient noise. It was too intense for me.
Apparently according to syste some of the best arguments came from emails, so he could have put those arguments anonymised and trimmed down to the main points into the blog post, which would have respected the company's privacy while still sharing good arguments, unless there was a NDA which would prohibit that.

So I disagree with you, because you look at this very black and white while the reality is grey.
I was kind of disappointed by this article, it seemed very distant from the real flourishing intentional communities that exist today. Seems like the author did a little reading and that's about it.

If one is going to connect intentional communities to startups a good one to think about is the Factor E Farm that's part of the Open Source Ecology project [0]. The community is a hacker space for implementing and experimenting with machines for self sufficient communities. It might not be the best when considering intentional communities since the community supports the project.

Another community worth considering is called Dancing Rabbit [1] in rural Missouri, it was founded in the 90s by Stanford grads. Its model is that of an eco-village. Residents are economic free agents, many of whom free associate into a variety of co-ops. The land is owned by a trust and the rules the trust holds residents to place an emphasis on ecological stewardship. It has around 75 residents.

Twin Oaks [2] in VA by contrast is a classic collectivist community. Its modeled after the community described in Walden 2 by BF Skinner. The community is centrally planned and is income sharing, that is, residents work on business and chores for the community who receives the revenue, pays all expenses, and gives the individuals a small allowance. This community has been around since the 70s and has over 100 residents. Its businesses include hammock making, tofu making, book indexing and agriculture.

[0] http://opensourceecology.org/about-factor-e-farm/

[1] http://www.dancingrabbit.org/

[2] http://www.twinoaks.org/
Can confirm, I fell into this trap. Read books for about a year and realized I don't know shit and barely could code a hello world app. Then started actually applying those skills to hobby projects and learned 500x much more that way.
It is a question of personal taste. I personally don't like it, there's too much distraction and too little substance. It might be interesting to illustrate some concept, but not everything imo.
Learning JavaScript the language is trivial compared to learning JavaScript the eco system. I've currently started working on a project using Vue, webpack, babel and bunch of other tools I've never used before and I feel like I'm learning an entirely new language and 90% of the time my actual JavaScript knowledge is completely useless.
My Adventures in Self-hosting
This is an interesting assertion, but I don't see any independently corroborated support for this argument.
Awesome - I have been waiting for something like this for years.

I am sure the next steps will be better visualization and simulator accuracy.
> because the restaurant was "too cheap" to handle processing and transaction fees.

I applaud businesses like this. The fact we slowly let a few giant private corporations enact a 1-3% fee against pratically the entire consumer economy would be ludicrous in any other situation.

Plus the privacy concerns just are not worth the convenience. Whenever possible I use cash, simply so I slow the day coming where I can't function in society without having my entire spending history out there for any agency to decide to take a look at.
I've had similar experiences, where I learned about something ops was doing -- such as a really complex script to configure something -- that was easily solved by a simple code change. I always pushed for feedback from ops, saying we'd make whatever changes they needed, but they never asked for much.

What was happening is they just accepted the software the way it is, and because they were capable of writing this complex script, they didn't see the need to ask for help or changes.

I've spent some time recently learning more about the specifics of their deployment and have some changes to make as a result (though since deployment is working, it'll be a slow change since it's more like technical debt and not an immediate problem).

However, I think I'm actually going to suggest we do what you're doing, and actually make a developer go sit with ops whenever they deploy a new release. That's a great idea, thanks.
I remember just three things about the book "Show Stopper!: The Breakneck Race to Create Windows NT and the Next Generation at Microsoft" (1994): the death march, that they tested the OS by writing a file over and over (!) and that they thought the graphic part written in the new object-oriented C++ would save them a lot of time (it didn't)
If you don't want to swap jobs, another way to get very good exposure is to deep dive into any external code base you have access to.

I was a sole developer for a time, but we had the intention to grow. In preparation I spent a lot of time cleaning up an old codebase to best practices. I pushed every tool and library we used to the limits to get maximum benefit/introduced complexity, which meant reading and understanding the source.

My go to language is Scala, and I learned a huge amount from SBT, akka, slick, play and others.

Were now up to 4 developers with no official hierarchy, but its agreed that these investments have paid of.
No Problem! It was kind of nice to actually write it down, a bit of an ego boost to really lay out things that I have learned!

I will give one warning that a lot of what I really learned is when to prioritise one of these things and when it's okay to let it slip.

Like should I push the launch date back 2 weeks to implement bug reporting? Is it okay to launch even though I don't have 100% test coverage? When should I prioritise writing tests for the remainder of the code? How much time is too much time to test a particularly difficult to test portion of code?

I don't really have answers or rules for those, but after living through each of them, I have a much better feel for what to do. And as always, shipping is better than not shipping. Code that you never release because you are always trying to make it perfect doesn't help anyone. At some point, good enough just needs to be good enough.
A Quick Primer on Creating a Gopherspace
The freedom to try stuff.

I started my "real" development career (I'd played around a little before then) while employed as an Admin Assistant at a company that used an Excel spreadsheet to track work coming in and out. Every task had to be repeated 4 or 5 times, as the company needed different views for different managers. Oh, and of course, only one person could use the spreadsheet at a time.

After a few months of typing this in over and over I got sick of it, and fired up Access. In the spare time I had here and there I put together a database everyone could use at once, input once, then open up appropriate views for different managers. I did a lot of this with the Access visual query creator tool. My manager was blown away when he saw it and gave me permission to keep building the feature set out - I'll be forever thankful for that, because many in the company resisted.

I added and added to that database, learning VBA for the more advanced stuff, until Access became too limiting (I honestly can't remember why now). We didn't have admin access on our machines so I couldn't install Visual Studio Express, but I could install SharpDevelop. So I did, and created an alternative front-end in VB.NET using the same Access database, eventually graduating to SQL Server (again, I forget why, but I think regular backups were one particular reason. I remember a phone call with a very confused rep from our outsourced IT provider wondering why an Admin Assistant wanted a SQL Server database).

Nowadays I work in Node, create iOS apps, all sorts - I've left that original environment far behind. But I wouldn't be anywhere near where I am today without those sandbox environments that let me learn and grow very quickly. People are quick to dismiss Access, VBA and all that, but they shouldn't be.
It's very complicated to articulate exactly who can block Bitcoin transactions. The traditional simple answer is that "a majority of mining power" can block an individual transaction by refusing to include it in blocks.

However, they have to be pretty committed to this, because if someone outside of the group does eventually mine a block that contains the censored transaction, the group members also have to be willing not to build on that block, and to trust each other not to do so. Just agreeing not to include the transaction in blocks themselves would be insufficient.

At that point there are complicated questions about how stable and credible the arrangement will be, since systematically avoiding building on certain mined blocks involves slowing down the consensus slightly, and also trusting that the eventual consensus will exclude those blocks.

If, say, 51% of mining power committed to censoring one particular transaction, that might yield an effective fork of Bitcoin for some period of time because the other 49% might gamble on their ability to get their rival blocks accepted in the long term (or, if they didn't know about the 51%'s policy, not see any reason why they shouldn't simply build on what appeared to be the longest chain!).
Painkillers without dangerous side effects
Consider the inevitable conclusion that all information shared "publicly" will eventually make its way to the public domain.
> Humans aren't infatuated with their work by some corporate conspiracy

I don't think he/she implied that.
> there are weaknesses to the Lisp "image"/"world"/whatever model that Lisp-M partisans aren't quite willing to acknowledge

I'd be interested to hear this expanded upon.
I suppose I know who to call on when a real zebra's head transportation emergency arises.
Peeking into relocation of function static in shared library
I am actually somewhat surprised that rural school districts haven't argued for pooling state funding assets. The focus always tends to be on the Urban vs Suburban divide (and cultural politics involved with suburban flight, etc.) - but rural schools would far and away be beneficiaries of such a policy change.
My comment was in reference to topics covered beyond SELinux.
If they're successful, it means they managed to survive on their craft even before a lot of people wanted to see them. So why wouldn't they be able to continue to do that after they became better and more successful? You simply assume everybody sells out, you don't even say "many street magicians shill for products", or most, no, they just categorically do. I guess you can't tell me the exact threshold when they do? Is that different for everybody, but everybody still does (or would if they were just successful enough) at some point?

And why still call them street magicians then? Why not marketers? You don't call people who make advertisement spots filmmakers like you would call Hitchcock a filmmaker, and you wouldn't call those who write "copy" authors like you would any of the ones serious authors aspire to. But most importantly, you don't call someone who sings loudly to distract someone so another person can pick their pocket a singer, you call them an accomplice.
Very cool stuff.

Fun fact: A certain game-dev kit had another machine sitting along-side on the bus. It enabled you to sample the Program Counter at N=1 for a small amount of samples(I want to say ~4k) off of a breakpoint.

The amount of perf stuff you could trivially track down was staggering. Load-Store-Fetch? Boom, there it is. Cache misses? Clear as day.

Never worked on another platform with such an incredible profiler and still miss it to this day. You could set N to any power of 2 for coarser profiles but it always shined at N=1.
Is it significantly more immoral then selling weapons that kill people to militaries?

What about selling weapons to the people fighting those militaries? Or two militaries fighting eachother?
I'm not a big fan of credit cards, but cash isn't free.
The key: AKL. Always Keep Learning.
While we're at it, you absolutely need to remove that cronjob. No package should run their own update. That's the domain of the systems package manager.
Are you really having difficulty parsing what he's saying? I thought the pronouns were clear.

If that was someone describing a sports match, would you quibble with the word "praise"?

"When the <opposing team> poured into <the area>, the <home team> almost blew it. Then they were vicious, they were horrible, but they put it down with strength. That shows you the power of strength. Our <team> is right now perceived as weak … as being spit on by the rest of the world—."

Is it just because you know the current president of the USA is describing the deliberate murder of about 1000 pro-democracy protestors by an authoritarian state that you're experiencing cognitive dissonance and not wanting to accept the obvious interpretation?

He has a bunch of these kind of comments, about how Saddam used a little gas, and "everyone went crazy". You can watch some of them on on video, so no-one can influence your take on them.

I personally find that when Trump is talking about some atrocity that say a terrorist group has committed, he seems more angry that we're not allowed to behead or set fire to people or whatever, than he does about the fact that some individual got their head cut off or got set on fire. But maybe that's just my take.
I take the opposite view.

"ln" isn't "link". It's ln. My brain has particular concepts bound onto the command 'ln', which are not the same as the concepts for 'link' in general use.

"grep" comes for Global search, for a Regular Expression, and Print it. Grep doesn't 'find'. It PRINTS occurrences of a regular expression (not just a string), and continues globally rather than stopping at the first occurrence.

Another advantage is precision. "I did ln -s" is more precise than "I linked the file". "I grepped the file" is more precise about what I did than "I found the file" or "I searched the file".

Re-using English words directly - which already have rather broad and fuzzy semantics - in a domain that is a) more precisely defined than English b) not always consistent with the English meaning and c) international is not a good idea imho.

Heck, even ln/cp/grep etc are already ambiguous enough as it is! Depending on platform, UNIX commands may involve subtly different semantics (e.g. due to things like HFS+ filesystem data fork vs ext3 vs ZFS copy-on-write). Or different grammar. Quick example: cp dirname -rf works in linux, but not in BSD since you need to place options first in BSD.

Having picked up bits of some foreign languages, I've also found that my brain learns the correct meanings of words most easily when they are similar but not the same as English.

When the words are the same in two languages, my brain keeps its binding to the English meaning, and I tend to not to remember the subtleties of using it in the foreign sense.

When the words are completely different, I sometimes struggle to remember the new word. [I sometimes cheat and pretend I'm learning a new word of English. Somehow, that helps]

When the word is very similar but subtly different (for example, Geomatikk in Norwegian vs Geomatics in English, it's a) easy to remember the word and b) easy to remember any subtle differences in meaning.

So I believe the unix way is the right way.
I would add : Design-Ship-SELL-Support cycle :-) Nothing as enlightening for a developer to get confronted to user frustration in the Support phase AND prospect's indifference in the Sell phase
That makes sense... Li is typically 4% of the weight of a Li-Ion battery, so that would align pretty well.
> Text is simple.

Sigh. I am not here to argue with your out-of-context sweeping generalizations. So I won't.

BTW, do you have a particular gripe with S-expressions / LISP? You ranted twice about parens in your comment towards me.

And no -- me, the OP, and several others in this thread will definitely not stop with this "vague FUD", "bs", "trolling" -- all your quotes from other comments -- simply because it's something we struggle with regularly.

We all have day jobs. When we stumble upon a piping problem -- be it unable to find an erroring process easily and quickly (sometimes not at all), or unable to understand an exit code, or having to actually look for signal values, or stumbling upon a bug in an older version we're stuck with -- we try our best to get the problem out of the way and move on. Most non-tech-savvy bosses would react extremely bad if you told them you're spending hours or days on a problem they perceive as one small piece of the glue you're using to put a painting together, and especially when they find out that you're not even at the part where you must hang the painting on the wall (example: deployment). And that's a fact of the daily life of many devs. You can call that a vague FUD if you wish. <shrugs>

So forgive all of us working folk who don't keep Star Trek-like exact logs on every problem we ever bump into. /s

The negative impressions build up with time. You can try calling for 100% scientific method on this but I can bet my neck that if I've known every single minute of your life, I'd catch you with your pants down on many occasions that you don't keep a detailed record on everything that has ever frustrated you. Can you deny this? If not, then I don't understand why you are holding on to a strictly scientific approach on things people bump daily into but can never excuse spending huge amounts of time on, in front of their bosses. Peace?

TL;DR:

Since we have jobs and we must go on about it relatively quickly, most of us never spend the effort to write down every single instance where the UNIX shell semantics have made our lives harder but we managed to pull through via a workaround and just went on about our business minutes or hours later.
It's a long running tradition, especially in medical education.

Here's an edition from 17 years ago: https://www.amazon.co.uk/Human-Brain-Coloring-Book-Concepts/...
Hiring a diverse team may not be as hard or expensive as you think
Ancient skulls may belong to elusive humans called Denisovans
Again, my question is: how is this state-sponsored?
That's only in post agricultural societies. Look at most Pacific new Guinea tribes (where scarcity isn't much of an issue) and you see a lot more focus on social networks and leisure time.
What makes you think that these tactics represent "the only two possible paths?"