skysight-inc/HackerNews huggingface dataset:
I know there's some flats you can buy in London close / connected to some major luxury hotels that provide that. E.g.

https://www.homesandproperty.co.uk/luxury/property/1125m-apa...
Airport searches may uncover illicit drugs, but aren't run by the Drug Enforcement Agency. The Transportation Security Administration searches are looking for weapons and explosives.
Would you be able to give an example of how limited in scope you're talking about?

Is it just a single "write a method that does this" type problem? I ask because I did a take home very recently which I know I could knock out quickly, but it took much long because everything you listed ballooned the amount of time it took me to complete it. Specifically:

- Has the engineer followed a language standard (PEP/PSR)?

For JavaScript, it takes some time to setup a new project from scratch with linting and formatting configurations. Then documenting it in your README.

- Were unit tests provided?
- Were sample cases the engineer ran manually provided?

Once you go beyond a few "features" to write, this balloons in time due to both writing it with good descriptions and documenting it for the reviewer.

- Was the code "elegant"? Could another engineer at the company look at the code and maintain it in a year.

If what you ask is of sufficient complexity, it would just be normal to take time to think about what the interviewer is expecting here. Like what future features could there be? How might this be used in a larger codebase? etc. Then once you've decided on this, you'll want to spend time commenting and/or writing up an explanation in your README about your design choices.

Lastly, this isn't mentioned but I did this on the take home I recently completed - using version control and properly branching & merging on each deliverable. Doesn't take time, but if you are making atomic commits with good comments, that's just another way for you to lose time. Of course, I don't think the fact that I did this is going to be noticed as it wasn't written out as a requirement.

If you notice what I'm nitpicking, it's all the setup and writing that becomes a time sink for most. In isolation, it wouldn't break the bank, but with all those requirements combined, you've lost much more than 3 hrs. When I'm given take homes for interviews, this is where I've burnt the most time - taking the time to document well.
Large-scale wood-based construction in paleolithic cultures did exist, notably in the Alps:

https://en.wikipedia.org/wiki/Prehistoric_pile_dwellings_aro...

Not fine woodworking, perhaps, but possible.

Most early construction was based on found shelter (caves), hides, sod or turf, brick, or stone. Locally-available and hand-workable with very simple tools.
Been thinking about this for quite a while. Now, trying to make it happen - https://primechasm.com

:-)
This debate will keep happening for years to come, but everyone's just repeating the same talking points over and over. I have to sum up my thoughts like this:

I really don't think we're ever going to find a perfect hiring method. You will always have a nonzero chance of false positives and false negatives, and there will always be downsides that piss people off. So, pick a reliable hiring method(s) (talk about experience, solve whiteboard q's, do take-home projects, or whatever) and try to make it better over time. If you don't like it, you can switch to another method and start improving on that. Etc. But your method will always fail some good hires and pass some bad ones. It sucks, but we are still able to hire mostly good/trainable people, so we should stop worrying and move on.

I hypothesize that there are a lot more interviewees than interviewers getting involved in the debate. I only have to tell the former group to keep trying and stop complaining. If you're not sure why you're failing interviews, that's a solved problem -- just do mock interviews with your friends or on interviewing.io. But stop blaming the process for your own failures.
That's a pretty bold claim, care to elaborate?
Error correction provides the same value as a checksum, but better. (the tradeoff is ECC codes are much larger and more expensive to compute)

It's also worth noting the CRC is used for power-loss and doesn't actually provide error detection for metadata-blocks.

Checksumming data is a bit complicated in a file system, mostly because of random file writes. If you write to the middle of a file, you will need to update a CRC, but updating that CRC may require reading quite a bit of additional data to build the CRC back up.

To make random writes efficient, you could slice up the files, but then that raises the question of how large to make the slices. Too large and random file writes are expensive, too small and the overhead of the CRCs gets costly.

You could make these slices configurable, but at this point we've kinda recreated the concept of a block device.

The block device representing the underlying storage already has configuration for this type of geometry: erase size/program size/read size. If we checksum (or ECC) at the block device level we also get the added benefit of also protecting metadata blocks. Most NAND flash components already have hardware ECC for this specific purpose.

TLDR: It's simpler and more effective to checksum at the block device level.

And for MCU development, simpler == less code cost.
> You lose out on the discoverability that centralized hubs give you.

This isn't a real trade off. Consider how the web traditionally worked. Everyone has their own website, then you have search engines like Google or Yahoo that allow you to find anything anywhere.

A third-party search engine doesn't have most of the centralization problems you get with a Facebook or a YouTube, because people only use them to the extent that they're good, which means returning the search results people want. Moreover, if YouTube goes bust, all your videos disappear with it, but if Altavista goes bust, Yahoo and Google continue to exist and index all the same information.

You can have things that index all the other things without them being a single centralized monopoly.
The Great Pyramid of Giza was constructed about 4,500 years ago.
I don't personally usually bother, but an EE approach would be to put a diode between the 3.3V supply and the MCU/flash power supply pins with a large bulk capacitor, and use the voltage just before the diode as your brownout detection. It can't discharge back into the power supply or other parts on the board because of the diode so the capacitor just needs to store enough charge to run for a specified time after power loss.

Then you can configure how long the MCU runs after power shuts down. Put 470uF there and I imagine you'd have your milliseconds easily.
> You lose out on the discoverability that centralized hubs give you.

Obviously you can have decentralized services that address this important 'presence' issue.

IMO the issue is that we have conflated the 'functional goal' with 'architecture'. The 'goal', for me at least, is public information systems that protect civil rights and resist the rise of tyranny. That goal, after thinking about this space for the past 25 years, can be served with a combination of centralized and decentralized services, and a mix of grassroots and corporate players.

To get there, we need (a) societal consensus that privacy in fact matters quite a lot to, and is a bedrock of, our civilization, and (b) [the recognition that] ideological bias is a deadly sin for a system architect.
Right.

One thing is for sure, and that's that I'm the best me, and you're the best you.

I spent most of a day yesterday trying to get openssh 8.0 working on Debian 2 (with 1998 era kernel, glibc, etc). Because I can.

Genuinely more fun than all the toys money can buy.

It didn't even work. Fuck.
It gets boring. Hotels are full of airheads. Even Trump got bored of it.
It seems to me that the minority can dictate things that are inconsequential to the majority.

Take the halal example: as the author says, the kosher eater won't eat non-halal food, but non-kosher eaters don't mind eating halal. If it wasn't so, I don't think a Kosher minority would be able to impose anything.

Seems like the author is picking and choosing examples.
Executables are easy. You don't even need symlinks. Just a wrapper script that does an exec. What's harder is stuff that's not executable like configuration files. Here you have to use symlinks.
There are frequent delays on the Empire service in New York. When I once asked the conductor what was going on, they said we were waiting for a freight train to pass, because the track is leased from CSX. From what I was told, Amtrak is legally/contractually entitled to right of way on such track, but the freight companies basically don't care.
That's a good point, but I'm not sure it changes anything. Signal will fall back to SMS today if the target number isn't using Signal. That's one of the big reasons I use it, I don't need a separate app for my contacts that use dumb-phones.

Given that RCS will also need to fall back to SMS for phones that don't support it, the only distinction I see here is whether it's easier to get all of my friends to move to a new phone that supports RCS, or if it's easier to get all of my friends to switch apps.

Either way, my friends that refuse to change will need to get SMS messages, as they already do today.

On the Matrix side of things, this is theoretically solved by making the protocol separate from the client. This allows any company or phone to have their own Matrix client, and allows users to swap out their clients if they have other preferences.

For existing clients that don't support the protocol, you use bridges. There is already a Matrix to iMessage bridge, although it's really not practical for most people to use because Apple locks down iMessage so hard. But the same question applies -- will it be easier to get Apple to switch to a brand-new protocol, or will it be easier to get Apple to support a bridge to their existing protocol?

Of course, in the worst case a Matrix client could fall back to SMS for unsupported contacts, which (again) RCS is already going to need to do.

The problem with Matrix pretty much comes down to security. I keep hearing people say that they're going to turn on E2E encryption by default any day now, and as far as I know it still hasn't happened. My impression is the technology is still a little immature to rely on for security-critical tasks, although when the alternative is SMS, that may not matter.
Yeah that’s what I was thinking—that the store is so over saturated right now that it would be hard to make your app visible.
I recently took part of this route (DC to Chicago then Chicago all the way to LA) in December of 2018, the people were really fascinating. Lots of folks, especially older ones, who just didn't like taking flights and weren't up to driving cross country and then some who were train enthusiasts and just loved trains and then a few families. It's a real shame that they're doing searches like this, it sounds pretty sketchy.
> * At this point the only reason I stay is they sync macOS extended file tags and comments; both things I make heavy use of. To my knowledge Syncthing doesn’t, nor Google Drive for that matter.*

iCloud Drive does that too, and should be good enough if you stay within the Apple ecosystem, can’t say about support/reliability on other platforms.
Sounds interesting. Do you have a way around the paywall?

Edit: This worked for me: in chrome, right-click the "web" link and choose "Open link in incognito mode". Then pick the first search result.
Yeah, it reminds me of the more optimistic 'Golden Age' sci-fi in the West - I mean Asimov etc.
Lisp and Smalltalk programmers worked this same way. You develop bits of code incrementally to build up to a larger program. It’s a benefit of a REPL, which is what you’re doing with print stmts. keep in mind interviews are mostly random, most interviewers are terrible. Don’t let it get you down.
Tracking value increases with rarity. Data is packaged and sold, not simply stored and empty cells can go for crazy money if the target is hot enough.

How much would you pay for Elons verified personal number?
Well, none of the above. Anytime you try to gauge someone by counting, it's not going to work well. You need the best developer at your company, to do the hiring. Filtered by HR for personality and so on.
What’s the deal here? Is this a case of US high tech sabotage (like the famous stuxnet) and Trump making a joke about it on Twitter?
AWS EC2/RDS Outage in us-east-1
Thanks for the response. That’s pretty cool to hear. So it sounds like you get anywhere from 15-30 downloads per month. That’s not bad for money earned while you sleep.

I’m thinking of getting into the space to see how I can do. My eventual goal is to earn $1000 / month without too much maintenance / time beyond the initial development.
I actually played a game where whales spent huge amount of money, after a while it continued mostly because I wanted to understand who these people were.

Several are exactly like you describe, others need the anchor of money to loose as to feel invested, others simply have a lot of money and for whatever reason want to win in a game, and others simply thrive on causing misfortune to others through their financial advantage.

Those very whale friendly games are, as a sort of ecosystem echo, as fascinating as they are disturbing.
"The apparently free, participatory open-source software communities have frequently depended on the charismatic and arbitrary authority of a “benevolent dictator for life,” from Linus Torvalds of Linux (who is not always so benevolent) to Guido van Rossum of Python"

GRAB. FORK. It's all there. Nothing stops you. Sleepless nights, stay on your toes.

Nothing stops people from complaining either. And if you fork, people who didn't will begin complaining about you.
Hong Kong police spraying protesters with blue-dye water to mark for arrest
Google depends on thousands of external software projects.

They heavily support a VPL, Scratch.
> I encourage new developers reading these sort of posts to just ignore the fluff and plug on. You'll get there.
> And if not? In five years you might want something else entirely.

No offense, but this isn't good advice. You just contradicted yourself within two sentences.

Here's the "true" version of this statement:

You may not actually "get there". You may or may not want something else entirely, after that potentially traumatizing experience. You also may be six figures in debt now, good luck!

In software development, we have this tendency to not take things seriously. Career choices are some of the most serious choices you make.

I'm afraid we're luring all these otherwise uninterested people into this career path by promising them lucrative and future-proof jobs. What eventually happens is that an oversupply of underqualified candidates flood the market. Meanwhile, other trades that aren't always in the headlines are starving for workers.

Despite what you may want to believe, many companies are afraid of hiring sub-par developers, because the narrative is that they will eventually ruin you. We can argue about how true that is, but that is irrelevant to the outcome. What matters is the perception.
Who is and who isn't working on a state-backed digital currency?
I've always wondered how dog hits are seen by courts as different from officer testimony. Of course they're well trained and qualified and accurate, one would hope. But they can also get a subtle cue off the handler to simply sit because they've learned it's expected. So back in court, you're back to officer testimony that they did or didn't cue the dog to show a hit; it might even be subconscious. If that's the case, the dog isn't neutral and might as well be skipped as theater.
> if you stay within the Apple ecosystem

That’s the rub really. All my machines other than my main Laptop run Linux and my phone is Android. I’ve really set myself up for pain.
Also river vallies, but principally coasts.

For most of these cultures, "cities" did not exist, and even assuming they did, from the times of the first early-agricultural settlements, might have numbered a few thousand, perhaps tens of thousands of souls. With little transport, food was either sourced locally, or brought in on boats, rafts, or barges. Total collection areas for bulk goods of more than a few kilometers would be highly unlikely, though longer trade routes for rare materials (timber, metals, spices, hides) might have existed.

A principle relic of such settlements are their rubbish tips. Again, lack of transport meant that waste and filth were moved a few meters, for as long as the settlement existing -- decades, centuries, or millennia. In many places these are the principle evidence of early settlements, particularly shell mounds (shellfish are an easy, reliable, and sustaining prey), and can themselves measure several meters high and tens of meters across, particularly on otherwise flat aluvial or riparian landscapes.
It's a very interesting mix of economic decisions that each actor is making.

The first thing that is happening is that people are choosing to eat enough fast food that the demand exists for these companies to employ workers and agree to long term supply deals with landlords and ingredient suppliers.

If everyone decided to only eat from grocery stores, the industry would disappear.

Next, we have the laborers. Many come to fast food as a temporary bridge. They need some money to pay for school or as a bridge income before they get a different job.

Others want to stay for a long time. They do good work. They rely on this income.

The fast-food industry is doing everything it can to eliminate these workers, and it uses headlines like the above to garner public support. "Of course we have to roboticize everything, look at all the turnover we have!"
This generic advice isn't always the best one. Only do this if you're actually guilty and they can't come up with PC. You have to play it by ear, I've talked my way out of more than a few tickets by just getting a sympathetic police officer, if I had annoyed him by doing the 5th I'm sure he would've just written a ticket etc.
Driving is largely unregulated, so I doubt this is about preventing travel.
Now give me count distinct in pivot tables, and limit rows in a book only by the ram in my machine.
Software Against Humanity? [pdf]
Whatsapp and Instagram are Facebook. The same company owns and runs all three.
They are brave agents of freedom.

You find those in every country.
You could as a sanity check, it would be useful to insure no corrupted data gets passed into your system. Though this wouldn't protect the filesystem completely.
I use Leiningen as well and I have no issues with it. REPL startup is a bit slow, as is expected from most JVM programs but a bit more so for Leiningen.
Political problems require political solutions. Us nerds in tech too often assume some magic bullet protocol or other data structure or algorithm will fix how humans relate. But at the end of the day, power is about power, and a protocol or a platform is just on form of power.
"An email uncovered in a federal drug trafficking case from last year showed that Greyhound tried to kick the DEA out of its Albuquerque station. [...] Greyhound declined to comment about the email or what has happened since."

Sounds like someone has been gagged by a National Security Letter.
Are you arguing about the centralized role Linus or Guido have? I think what you point out, the lack of a formal requirement for centralization just makes the point that centralization emerges from these networks anyways a bit stronger. And hence the point that we need to build accountability (git annotate for source) into the new systems is strengthened.
Reddit has been quite dysfunctional for me the past hour or so.
> The response was stunning: we were greeted by near silence. We assigned 20-30 issues to developers, and almost none of them were acted on. We had worked hard to get the false positive rate down to what we thought was less than 20%, and yet the fix rate—the proportion of reported issues that developers resolved—was near zero.

Duh? If I am assigned a low priority bug, I will put it on the bottom of my todo list. My manager has the ability to reprioritize items on my todo list, but that doesn’t seem like that was done in this case. If you want people to fix your low priority bugs, just filing them and praying isn’t going to work.
From Zero to React
Make a hardlink instead? Needs more oversight, but not as visible to DropBox.
Why AI Is Reading Your Resume and What Can You Do About It
As a man with long hair (and a dark-ish complexion), they are constantly requesting to search through my hair at the airport. It feels like an absurd request every time, especially since most women with long hair aren't being searched in the same manner.
Your "best developer" probably doesn't want someone better than them on the job.
And that's how you make stealing legal. Perry is a thief, plain and simple, not to mention the many other derogatory terms that could describe this subhuman shitstain. He is the embodiment of the American idea of creating a problem where one doesn't exist and then "solving" it for profit. This is known as the war on drugs. It's extremely profitable not only in terms of money but also in terms of creating fear used for societal control, especially for controlling minorities. Ruining people's lives and society to make a buck. I hope it really does get dangerous for this scumbag. The world would be better off without him and all the rest of the people like him.
I recently took this route, I enjoyed it because I have a weird bucket list and this was on it (and I like trains) but I have to agree. I know it's not a profitable route and the NE corridor makes most of their money but I consider infrastructure to be a symbol of national pride. What does it say about the US as a country when our trains are unreliable and dirty, our roads are full of potholes, and quality public transport outside a few cities is basically nonexistent? I compare it to my experience living in Germany/Shanghai and it's just totally opposite, the experience on the train on this route (Dec 2018) was closer to train rides I've taken in Ukraine/Romania/Hungary (nothing against these places, I'm writing this from Odessa and love it here) than the train rides in much of W. EU
Butler + staff + cleaning + food + chef combined would be either in striking distance or more expensive than renting a suite for a year. The smaller suites are around $2k to $3k per night. You can usually get up to a 40% to 60% discount if you pay upfront for a year (or three) and they throw in all kinds of stuff for free.

Assuming $1.5k as a conservative estimate, we get about $550k/yr. Or, $45k/mo. If you have a mortgage, then for a marginally expensive home ($3M in the bay), a 20-year mortgage all in at 3% is $21k.

A good butler starts at around 9k/mo before taxes etc. And goes up to $12k/mo to $15k/mo. Let's assume $10k, then that's $31k so far.

Add about $6k more for household cleaning and a part-time chef (pricey!), then we get to $37k before the groceries are brought in.

Depending on how you shop, this can be between $2k/mo/head to $5k/mo/head. let's assume $2.5k. So $39.5k before utilities, upkeep etc are taken into account.

Add $2.5k in high-speed internet and utilities. If you want a house with a good HVAC system, air purification and all the other bells and whistles that are incidental in a hotel. We're now at $42k with a $3k difference so far. I'm sure that can be easily made up if you buy a more expensive property or the property taxes go up or you refurnish your home...

It's fairly price competitive to live in a hotel for a rich person versus having your own gigantic household. The biggest tradeoff is space. And I'm happy to do that for the greater peace of mind.
No you aren't wrong. Java the language has a reputation of being verbose, boilerplate-heavy, and inspiring over-engineered OO cruft. JVM on the other hand is a pretty modern and performant and nice-to-debug platform.