happyslobro

I will phrase it differently in the future, but I stand by the sentiment.

Wait 'til NPR notices 10K shares, 0 referrals from facebook.com. That ought to start a whole new fire.

This man is a hero of our times. I am going to show his story to all of my Facebook friends. Fuck Zuck.

Mentoring is hard. It makes me question everything that I know, and worry about what this guy's code will look like in a year if I criticise this, or praise that. I wish there was some way we could all just work together, for real, in real time.

I miss construction. Back then, I could just tell someone "Hey! You! Don't fuck that up, I'm pouring concrete around it tomorrow!" And we would still be cool at lunch break.

Trial by fire. Unavoidable in battle, untenable in surgery.

The problems start when you notice that your untyped key-value store has a bunch of NaNs where you were expecting a number. At this point, all you can do is pray that those numbers weren't very important, in the grand scheme of things.

I guess. But the political moderators in the corporatocracy would all get laid off once they finished training the AIs. Then it would count as a technocracy.

I think their long term plan is to literally take over the entire internet, by replacing every feature of every successful category of website. The free Facebook-net for India and Africa, this Facebook for enterprise thing, the embedded games, video... I fully expect to see Facebook for schools soon, followed by diplomas and then degrees granted by a Facebook online university.

Maybe they will even try to roll out a voting app some day? It could start as a polling app, and then slowly take over the voting booths in areas where they can buy the necessary permissions. Those governments that grant them control over their elections would celebrate increased voter turnout, and accept a massive campaign contribution (in "premium" Facebook ads) for being the party that opened the door. Jesus, now that I think about it, we could actually end up with a real technocracy in a generation or two, run by... Facebook. That is really, really scary. Brawndo.

Plot twist: he's actually hoping everyone else shorts, so that he can buy and go long ;)

Is there a simple way to process a list of files with this restriction? Something like `ls | xargs $(my-cli < $MAGIC_XARGS_VAR > $MAGIC_XARGS_VAR)`?

I know that it could be done with a loop, but that's a little unwieldy compared to `ls | xargs my-cli`

Airlines are already specifically the Note 7, I saw a notice at the security check in Amsterdam (Schiphol) about it. I wouldn't be surprised if a patch goes out soon for those color-coding x-ray scanners, that automatically detects a Note 7.

Having said that, this is a pretty small incendiary that we are talking about, and aircraft are several layers thick everywhere that a passenger can access. How would a terrorist actually use this to put a hole in a plane?

Got it. You can also set up an NPM repository like that, but I don't think that that is commonly done by small dev teams. This does lead to hilarity like the left-pad clusterfork.

I would use it to pre-process Github issues for me. Attempt to reduce some random user's rambling to a clear set of repro instructions, prompt for more information from the user when necessary, ping other devs' chatbots for help. Basically, issue templates, taken to the next level.

Also, I would use it to troll bureaucrats when I give up in frustration. It should try to force the bureaucrat to admit flat out that their logic is fundamentally flawed, and then ask them to propose a solution }:)

Where would a CI server retrieve dependencies from, if not either over the network, or from within the repository? Do you keep a module / library cache on the CI server itself? In other words, what do supply as input to your CI process, besides a Git URL?

I see that you found the same outdated notice as me, when I googled: it refers to an exchange program, not a recall. Check out this foot-in-mouth quote:

> Canadian Note7 Software Update showcases Note7 device is safe for use.

At this point, I think that it is most likely that there will eventually be a global recall (how could there not be? that would be madness) but they just haven't gotten around to updating all of the other countries. Recalls are complex, I guess. But they should at least shut down the exchange program ASAP, that's just a waste of time at this point.

The recall notice only seems to apply to people who bought the phone in America. If you change the "us" in the url of the official notice to something else, like "ca", you get a 404. http://www.samsung.com/us/note7recall/

Is this recall only available in the US? Is the rest of the world basically screwed, unless their own governments put some pressure on Samsung?

From the FAQ:

> 4. I participated in the U.S. Note7 Exchange Program. Is my replacement Galaxy Note7 affected?

> Yes. This applies to all Galaxy Note7 phones _in the U.S._ (emphasis mine)

Is HN open source or something? How is it that everyone knows this algorithm?

Protip: setting your user agent to GoogleBot eliminates a lot of bullshit like this. Most sites, including Quora, won't hold out on GoogleBot, although the WSJ does. I guess they don't care if 90% of their article doesn't get indexed, that's pretty brave.

There is a plugin for Chrome that makes that easy: https://chrome.google.com/webstore/detail/user-agent-switche...

This guy has the right idea. The problem, is that your doors are not the doors of a billionaire.

https://www.youtube.com/watch?v=IJIAOosI6js

Keep Summer safe.

https://www.youtube.com/watch?v=m0PuqSMB8uU

I think that the psychological option holds a lot of promise. At least, it plays to our strengths of big data, analytics and centrally controlled social networks.

A while ago, I worked with an all male team of about 20 programmers. The odd thing was, though, that there were a lot of women writing code, but not officially as production programmers. They were in high level support positions, mainly working on infrastructure and data, and helping my team work within in their system. This role is now commonly referred to as dev-ops or data analyst, elsewhere, and pays very well. But, because their job title was "L2 support", they were paid less and missed out on a bunch of perks.

I had a friend in "support" who had build a lot of a data normalization system that I often worked with, and we talked about the phenomenon a couple times over lunch. Basically, she was a little offended about the lower pay and the "support" title, but would rather keep her work / life balance and relatively powerful position within the infrastructure stack, than join the production team for a raise. In hindsight, someone should have fought for the whole L2 support department to be better paid; there was certainly money for that (we were in a wildly profitable niche), and the support engineers had the high ground. But we were both young technical types, and didn't have the business / legal skills or the confidence to confront management.

I'm not sure how things have played out there in the years since I left, but if they wanted to, that entire L2 support team could take off and form a devops / analytics consulting firm, and probably multiply their incomes by some small integers. Then they could hire from the product team too, if they needed web/UI ;)

Thanks for the heads up, sorry about the knee-jerk reaction.

Ugh, that title though... WTH is a time crystal, and who decided to call it that? I'm not clicking the bait to find out.

Right, let's dedicate a new department to that. And, just in case other departments start expecting similar leeway, let's make this department clearly separate from the others.

Or inspect element and delete the overlay. Same effort, less surrender.

Oh man, this sounds like a plot device in a horror movie.

This! A thousand times this. Investors know that infinite growth in a finite environment is impossible. But, they always seem to expect that their project should be an exception, or at least, it should push everything else aside and take the world for itself. Can't we all just get along?

I propose that we call this the Scarface effect: "The world is not enough."

An example of a current problem in NPM land, is "peer dependencies". Suppose 30 of your direct and indirect dependencies require one popular, fast moving library, say, React. For safety's sake, and to spare the effort of regression testing, many of these modules specify a fairly conservative version range for their own React dependency. Normally, NPM would just give you multiple versions of React, and each library would get the React version that it expects.

There is a small problem and a big problem with this. The small problem, is that your build size will be unreasonably large. The big problem, is that this React library has internal state - you can't just initialise multiple copies of it, and expect them to share a single state.

Enter peer dependencies. Each library that needs React, demands that the root module, your application, specify a normal depency on React, that satisfies their version range requirements. Clearly, this quickly becomes impossible. So, version mismatch is treated as a warning, not an error, and you (the application developer) learn to basically ignore that warning.

I can think of lots of solutions to this problem, all of which have problems of their own.

- All libraries factor out their state, so that they are stateless. Now you can load multiple instances of a module, but if they have different major versions, then they are totally going to mess up that state that you are holding for them.

- Application developer: it is your responsibility to patch your dependencies, and their dependencies, so that they all accept an overlapping range of React versions. But who has time to test 30 modules for regressions?

- Just build more, smaller, simpler applications. This is where I am right now. I still get version warnings, but it is a little less risky to ignore them.

How do you handle this issue in the Java community?

Apparently, even discussing the issue is no longer permitted. We've flown way past offense, deep into taboo territory.

Thank you for the tabs and buffers reminder, that is something that I should keep in mind now that I'm using Vim on a 4K monitor. At that scale, it feels perfectly natural to have 9 to 12 windows open, so that all of the sources that I might need to even consider are within my field of view.

I just wish I had more control over window layouts. Something like the controls of a good tiling window manager, like I3. There is just no way to open 12 files in a list of windows, and then arrange them into a sort of rectangle tree, but I prefer to open all the files I will need at once from the command line, using globbing operators and brace expansion.