skysight-inc/HackerNews huggingface dataset:
Not at all. A well-chosen semi-formal jacket can be serve as a great contrast to worn denim lowers. But without attention to detail, you get a pale blue polyester leisure suit jacket over black stretch "jeans". And that doesn't express playfulness, so much as a doubling down on bad taste of biblical proportions.
Alexa Intercom
Hong Kongers look for an exit 20 years after handover to China
The carpenter may simply know that turning the screw is imperceptibly instant in his experience, and that if the bookshelf isn't getting built quickly, the bottleneck is virtually never because he's waiting on screws to be turned. He's going to have to make a trip to the store anyway so he isn't concerned with whether turning the screw requires a tenth or a thousandth of a second.

He's more focused on the design and craftsmanship of the bookshelf, because he's built many excellent bookshelves to industry standard effectiveness in the past and measuring the number of screws he can turn in a second hasn't been relevant to the work.
Not for the first few weeks, usually. But given enough months the desperation is really just a quirk of the implementation.
Botox and Disney :)

It wasn't easy to come up with that list, was it?

My point is - AR and VR is way overhyped. As if a lot of people were trying to find the next big thing and that's the best they could come up with. As an additional layer to smartphone apps, I agree. But the next big thing - a huge NO.
And for me that was a perfect interview. First quick question by email to see if I was interested, then some simple test to see if I can really program, then quick interview to see if I have required domain knowledge (all questions were about knowledge required to program effectively, not abstract "how to move mount fuji"). For an introvert programmer like me it's a perfect interview schedule. Also it helps when you are already working and want to check conditions in other company without risk of being thrown out from your current job.
Microsoft Could Surpass Amazon in Cloud Computing This Year
Westpac shock as Apple bans its messaging payments app after three months
Asking questions like that can, all by itself, be a correct answer to the question.
Routers don't store IP addresses as strings... They use 32 bit and 2X64 bit unsigned ints usually.

And you can't compress something when measuring cardinality. Each route takes up an entry and the minimum space you can use with a non probabilistic structure is 1 bit per entry in a bit map.

There's compressed bitmaps but the random nature of routes will not compress well.
My advise is when you care about your "career" stick to the one with the largest user base (or depending on your location). Learn it, love it, embrace it. Then experiment with whatever you want to.
Cross region load balance is probably only thing, although I understand you've asked for far distance.
Some engineers I interviewed got "offended" by ElonMusk-like questions and refused to answer :)
Monitoring and Logging in Wonderland
Fair use critiques is designed for the photography itself, not for the subject of the photography.
You're right, it is common and it's easy to forget that.

Python in 2007 was Django, web.py, Subway, Turbogears, Pylons, Werkzeug, Zope, and a bunch of tools a lot of people have never heard of competing for space. Who needed all of those frameworks anyway?

It took awhile but slowly what works and what doesn't was figured out and we've got better approaches. Web programming circa 2007 was by its nature simpler and despite that the Python community (which is a blip compared to the JS community today) churned out a lot of stuff.

You can still build websites like it is 1999 but you've got a lot of other options now, too. Use the best parts and dip your toes into that stream of new stuff when you feel like it. Competition and progress beat the hell out of stagnation though.
> but are still accessible to practically everyone.

Unless one is going for a used device I highly doubt this. I know a lot of people who truly can only afford the 50€ to 100€ phone that usually lasts them 2 to 3 years.
You don't, but if you found that a candidate carpenter couldn't tell you whether they could fasten 10 or 10,000 or 10,000,000 screws in a one-hour period, you'd start to doubt their ability in general.
This seems like a bit of a troll?

You haven't given any substantial reason for why North/South Dakota makes sense, while North/South California doesn't, except that "Republicans... wanted 2 states that would vote Republican", which obviously is not a legit reason. If it were, we would split North Dakota into 100 Dakota's so that it would give 200 Republican votes in the senate.

Also:

> Yes, as someone from North Dakota, you're being rather stupendously ignorant of the midwest and the differences between North and South Dakota.

And North and South California are massively different, yet lo-and-behold they are the same state. Even more different is central vs. costal California.
Why Portability Is Not the Same Thing as Compatibility
You're thinking of a known criminal holding ill-gotten funds, whom his new country would like to prosecute as much as the old one.

Think instead of an ordinary person fleeing a disintegrating economy and/or an oppressive regime, who had stashed away some e-cash for such an eventuality.
Zerocracy Project Data Model, 0.24.2 Released
Haha, thanks for the recommendation. However, I have no problems with buying the things I like or need. I don't need overpriced services to provide me with basic groceries at steep margins. There just aren't any Japanese candy stores near here, hence Candy Japan.
https://appear.in has been the best software for demos for me (p.s. just a happy customer)

works from within the browser
excellent video/audio quality
good screen sharing
set up meeting with just a simple url
I did at some point, but then I am just distributing the diabetes to others and paying for it myself. So at the end having a $30/month subscription for candy is just not worth it to me.
>In iOS 11, Apple redesigned. It decided to combine this recently used apps list with the control center, so that you could put as much information on-screen at once as possible. This produced an interface with teeny tiny images, and lots of user confusion overload.

The provided screenshot doesn't show that. Rather it shows large window icons and big enough targets for everything.

The rest of the post goes downhill fast.

Not to mention that it fails to account for all the ways in which the new app switcher (and assorted options mentioned, control center, etc) make iOS 11 a much more powerful machine.
Thank you so much for those book suggestions. They will either be exactly what I wanted to know or a great reference down the road.
It also works for solving SAT. Try two literals and recurse on the one that can be made to satisfy more clauses.
> Is there any open repository of house images (OpenStreetMaps, etc.) that could be used as a substitute in the interim?

OpenStreetMap doesn't store images, just map data. Mapillary and OpenStreetCam are "crowd sourced Google Street View" alternatives, which could be used for that.

At an extreme case, you can put a photo on flickr with the correct tags and geo tagging information?
Kafka connector for MySQL
This question is trickier than it sounds. Sure 109 clock cycles per second, but estimating for actual human-perceived ops for an algorithmic problem one should use 106. (Source: USA Computing Olympiad problems.)
So a book that teaches a programming language with a "toy" software project does more harm than good? This is industry standard stuff.
Yes I very much agree. I would probably subscribe again if I would receive 0.25 or 0.33 of the packages throughout the year at 0.25/0.33 the price.
UK, EU, Brexit and EU Citizens
Users aren't meant to manually manage apps. Perhaps it should not even be offered as an option in the first place, except as something like "force quit" of last resort.

Apps are shown by recent-use, so that takes care of "which I'm using for this task now".
People who are wanting to get into complex cryptography today have to start somewhere. Showing working models, with huge disclaimers, in blog posts and on github is a great way to lean, if you invite others to show you flaws and break your implementation.
Neural Network Libraries by Sony
I can absolutely sympathize with people that want an affordable way to get more space for their family

But a McMansion will almost always cost you more than a more 'modest' house offering the same amount of space. Also that house will almost certainly be better constructed.
Under what circumstances would the initial connection need to be faster than 250ms for arbitrary HTTPS access? I can think of maybe it mattering to people that work with financial data, but outside of that I can't really see it mattering.
In context it sounds like a flippant reference to the 'creative thinking' type questions that were all the rage a few years ago. Ask someone an oddball question with the aim of having them talk through their process of solving a question they've never heard before because you just made it up.

As long as you make it clear that the actual number they come up with is irrelevant and you just want to see how they think (and you're also open to pragmatic answers like "why the hell would I be trying to calculate the weight of an Airbus A380 when I could just look it up on wikipedia?") I don't see why it's that bad a question.
Maybe the data usage would have alerted the infected.
Let Your App Engage Audience Through AI Technology
AI embedded mobile applications are creating a buzz in the industry with user-centric features. With their user-centric approach, these applications are getting much popular among the users.
Well, in C#-land, we often use / abuse attributes to get information about a class or property at runtime. This way, framework or library code can inspect entities that you've authored, and dynamically deal with them. Perhaps a decent example is validation, where a declarative style has gained a lot of popularity. A JS example might be:

@required firstName;

This simply declares the intent / rule, but does not provide the implementation.

We can argue terseness vs verbosity, implicitness vs explicitness all day - I'd argue that for certain basic things that you do highly frequently, a terse and implicit style is not a bad thing. It tends to increase the signal-to-noise ratio of your code, allowing the developer to focus on things that really are interesting, and not have to read through a lot of boilerplate.
>Often I want to properly exit the app because I don't want it starting next time where I left off, but instead from its default opening state, starting screen, initial menu, a clean slate.

That might be legit as a wish, but it's not an encouraged (or expected) use case in iOS though. The default is "return where one had left", so this is in some way an abuse of the system to do something it can manage, but wasn't designed to offer.

In which case it's expected that it might clash with other UI choices.
Please, Nothing is ever _more optimal_.
Dockerizing GitLab Review Apps
When the number of server changes you slowly ramp up from mod n to mod (n+1). Flip a biased coin for each user to decide whether to use n or n+1, slowly crank up the bias to the n+1 side.
Would love to hear about the solution, are you going to implement it or publish an article?
> Bards pre-literate-times in Greece purportedly could recite Homer's Odyssey themselves after one hearing

That sounds highly unlikely. Do you have a legitimate sources to back this up? Certainly bards had great memory and were able to recite whole epics (perhaps with a level of improvisation akin to "freestyling" in rap), but under what circumstances would they only hear an epic once?
In a lot of the places where NaN is generated, I would prefer it if an error was thrown.
What type of questions do you mean?
This is the kind of thing where I wonder if a shaming award wouldn't help. Imagine an award, let's say every half year, with a top twenty (one for each of the three big platforms) of needlessly inefficient popular software programs. Ideally with these kinds of breakdowns to back up the claims.
A lightweight Audio Logging application
> background-blind interviews, looking at coding skills, not credentials or resumes.

Subtext: "Did you create a famous open source tool, write a book, have patents in your name or architect some amazing system at a big company? Doesn't matter! Our hiring process prefers code monkeys who can solve our puzzles instead of system thinkers."

> An interview can result in a bad engineer being hired and later fired (a false positive).

Subtext: "A hire can either be good or bad. It's never management's fault if it doesn't work out."
Why is this Ubuntu's sole responsibility? Can you not get a UEFI firmware update from your vendor?

> I think it's a fair and tame adjective considering this is processor microcode we're talking about...

Processor microcode updates haven't, to my knowledge, ever automatically been applied by distributions in the past. In light of that, I don't see how it's reasonable to have an expectation otherwise.

> You say Ubuntu has a bug to track the microcode package as an exception, but that doesn't seem to be having a positive effect, does it?

By being careful before pushing out an update to millions of users? I'd say that's a positive effect.

> ...what is it that they're trying to decide in the bug?

Whether to continue to let users have a choice, or by taking that choice away by doing things automatically for them. There are also packaging-based regressions to consider; not just the microcode ones. For example: if the wrong microcode is applied to the wrong processor because of a packaging error, who would you be blaming? Intel or Ubuntu?

> But I don't think Ubuntu could reasonably choose to skip all microcode updates for 1.7 years like it did in my case...

Ubuntu didn't "choose to skip" all microcode updates. Ubuntu didn't choose at all; pushing an update requires a specific effort.

In light of this issue, Ubuntu is now considering what to do about it, responsibly, for all users. Both for this particular issue, and for microcode updates going forward.
As others have already pointed out, this explanation focuses on the RSA key exchange, which has been deprecated. It's not recommended for use with the current line of protocols (TLS 1.2 and earlier) and it's been completely removed from TLS 1.3 (work in progress, but close to being finished). The key weakness of the RSA key exchange is that session encryption keys are transported over the network encrypted with the server's public key. When the server's private key is compromised in some way, the attacker can passively decrypt all traffic, they can also "go back in time" to decrypt all previous conversations they might have recorded and kept.

For a more secure handshake approach, consider the Diffie-Hellman key exchange, which is a way for two parties to agree on a secret number (a very large number when used for encryption, of course) that third party can't discover from looking at the network traffic. It's a very simple and intuitive algorithm; there's a great video that explains it here: https://www.youtube.com/watch?v=YEBfamv-_do Today, we generally use the ephemeral elliptic curve DH variant (ECDHE), which has better security characteristics and works much faster.

However, DH is not sufficient, you must also authenticate the other party. Otherwise you could be negotiating your key exchange with the attacker and not the real recipient. This is where public cryptography comes in. After the key exchange, both parties use their private keys to sign the transcripts of the entire conversation up until that point. When this is verified you know that (1) you're talking to the right person and (2) that you have a secret (session keys) that you can use to efficiently protect the conversation.

Disclosure: I am the author of Bulletproof SSL and TLS, already mentioned in another comment here. Feel free to ask me anything.
Digging Deeper into Your Brain: The Neuroscience Behind Leadership
Hmmm a required flag is a nice idea (but better exposed using interfaces as an idiom I’d argue) but it’s not selling me on the wider use case.

If we were talking about very basic things then yes, sure, but I’d also argue that if they are truly basic then we could restrict decorators to built-in ones only (as those are the basics).

Much like there are “magic” Symbols like Symbol.iterator.
>They removed very simple two step gestures like swipe-delete in music player

Thank god for that. I hate swipe to delete anywhere, very easy to accidentally trigger AND confirm.

(I also hate the "shake to undo" -- and I hate to imagine someone with disability/arthritis etc having to go through that, but I digress).

>In the iOS10 search bar, if you search an app and start that app, the 'search button' remains active on the top left, press on which leads you back to search. (Why would I want to go back to search after I've found my app?"

Because multitasking. I often want to launch several apps.

>As someone who listens to music wherever I go, I liked the music control access on lock screen. But in iOS 10, they put AirDrop and Airplay controls on the first tab of control centre and music control is on second tab, requiring a second swipe(I'm walking on road and I'd like least amount of distraction)

Then just use the headphone controls?
> coding when EVERYTHING is immutable by default is a royal pain in the arse

Not sure I'd agree with that. Scala is a pain to write at times, but it's not because of the immutable data structures--indeed, the APIs are structured such that it's pretty painless. And while under the hood Kotlin's "immutable lists" aren't actually immutable (they're just ArrayLists, the interface is more akin to C#'s IReadOnlyList<T>), the API they present on top of it makes this pretty straightforward.

In both cases, you can do mutable things, but it's extra work.

I tend to think it's more of a Clojure-specific thing, and I think your #2 is more to the point: people don't use Clojure because it looks funny and is foreign to read for people who don't already know Lisps, that's all.

(I've used Clojure, but I don't claim to "know" Clojure. YMMV.)
It's not my favourite language, because I don't program in it myself, but maybe you'd like Pony. It is an actor based language that is actually designed with efficiency and strong static guarantees in mind, with both of these goals informing each other.
Totally have time to read huge PDF's every day.
"time matters and you have to think on your feet"

I've been in many stressful situations at work - none of them involved finding algorithmic solutions.
>So even when a design is perfect, it just has to be changed eventually because everything has to be reviewed and modified.

a) which design is perfect?

b) which elements do users not complain of it being "stale" when it hasn't been changed in a while?
The Hackers Russia-Proofing Germany’s Elections
Lean and Agile in Software Development
Maybe “sure” was overly optimistic. “Hopeful” might be better put.

I like the idea but I’ve yet to see a case that leads to better Code than other implementations.
I am pretty certain paintings used for containers have little to none in common with paintings you get at the home improvement store but some observations I have made concerning water vs. oil based paintings:

* Water based paintings dry much faster than oil based paintings

* The durability is pretty much the same

* The scratch resistance of oil based paintings, once fully dried, is light years better than that of water based paintings.

In some aspects the green movement has brought us water based colors where you could water your home plants with but are inadequate for some (read: wide) range of application.
Except that she points out McMansions are shoddily built and won't last-- one of her photos shows a McMansion with especially severe water damage, for instance. Re-roofing that wackadoodle roofline is so cost-prohibitive you might as well just burn the thing and start over. If you ever have the money for "personal gratification", why not buy an actual mansion built with actual quality?
Like Mercury on a foggy day.
When they believe that they face an existential threat, military planners often consider options which would otherwise be considered crazy. Look at mutually assured destruction, for example...

(Whether Israel actually does face an existential threat is irrelevant here; the fact that they believed they faced such a threat from their Arab neighbours explains their actions, regardless of whether that belief was correct.)
Out of curiosity, have you seen the latest changes to npm? Since they've added lockfiles I've yet to have any issues with dependency management, really.
It's absolutely relevant. On more than one occations I've had performance issues land on my table with the developer that wrote the code saying "it's not that bad, it's going through 100.000 elements". They simply don't have a relation to how much a modern computer can do in a given timeframe.

Usually I can guide them to understand where the bottleneck is, but every so often I have to rewite it so performance is acceptable.
This is what happens when the US makes it very difficult for generic drugs to exist on the market and when it bans importation of generic drugs from other countries - even from more heavily regulated countries such as Canada.

http://khn.org/news/government-protected-monopolies-drive-dr...
For testing/debugging, yes. For compiling, no.
> If they're living on the other side of the country, I don't care.

Is this not the textbook definition of NIMBYism?
Maintenance Release 2016.1.4 of Caché and Ensemble
I usually only fly on planes with 2-seat side rows when travelling in a group of 2.
I use zsh, it has a variable called REPORTTIME that will print a report after long running commands. I have a custom report that includes the bell special character.

This way any long running process will bell when it is done and also show the runtime and cpu time of the process.
Wouldn't 0RTT be safe for GET requests that doesn't contain cookies or private data?

Granted I suppose such interpretation would have to be done by browsers.

And even then it could be used to figure out which site you are visiting.
While it's easy to get frustrated especially if you are following each twist and turn that js takes, I think if you step back a little, you can see things are getting better as a whole.

For the longest time, js was just a thing I did on weekend or as part of tertiary projects at work. I first used js as a kid for my geocities page, used jquery and YUI for a work projects starting about eight years ago, experimented with Angular, and most recently embraced React and es6.

Almost two years ago, I quit my job and started building a side project in React and Fluxxor for fun. At this point there were a bunch of Flux implementations and no dominant library had emerged. I got frustrated with the build process and then got distracted with other life experiences.

I returned to javascript less than a year later and was amazed at how much better things got. I could do npm install and npm start and there was a good chance things would actually work. I was doing the same google searches but noticed that the documentation was a lot better. I also had a friend this time around and he steered me toward Redux and es6. Javascript suddenly became an enjoyable language for me enough that I plan to focus on it. This is after more than close to twenty years of fits and starts.
If he is good, he can reason about it on the spot. If he can't, I very much doubt that he can design anything excellent. That requires critical thinking to understand what it is being used for, what is good, and importantly what solutions are unsuitable for the problem he is trying to solve.