skysight-inc/HackerNews huggingface dataset:
> Most importantly using JWT tokens make it basically impossible for you to experiment with an API using cURL. A major impediment to developer experience.

Why can't a developer do exactly what you did in your second video, which is to save the JWT to a variable, and then use it in the request?

Heck, you could create a quick wrapper "jwt_curl"/"jwt_http" or something that automatically pulled in that variable…

There's two big things about this scheme that leave me confused: how do you know what the correct certificate for the client is? Do you just send it over HTTPS? But then, one of your opening premises is that we don't get TLS verification correct and are open to MitM, so this seems to contradict that, or are we hoping that "that one request won't be MitM'd", like in HSTS? (which seems fine)
Agreed.

But feel compelled to add: Agile is only a problem when teams pretend to follow it but actually don't.
There's "Agile", the buzzword that all sorts of advice-givers have capitalized on commercially, and then there's the Agile Manifesto [1]. The Agile Manifesto has merit and is a set of values, not a methodology - it would precisely agree with your advice to chiefly "use your brain". It's unfortunate that the latter has been turned into a Frankenstein's Monster of the former. [1] http://agilemanifesto.org/
7 transactions per second is just a tuning parameter though, it's not a fundamental flaw in Bitcoin. The problem is being attacked from two angles right now: The release of segregated witness and increasing the block size.

The real question is, what is the maximum real throughput of the system if we could adjust the tuning parameters to be as high as possible? It's well north of 7 but I bet also well south of, say, 1,000.
In big-O senses Radix sort is one of those more persistent misconceptions. At scale Radix sort has to be nlog(n) because you should really consider the possibility all your numbers are unique.

This does not even start on the reality that memory access really is O(n^(1/3)), addition is O(n) and a lot of other things we assume are O(1) are not.
2016 Olympic Day Run for May 25
I would recommend hack reactor as I have consistently heard good things about the quality of training from their grads.

my ex-company hired 1 junior engineer from hack reactor and she has since then gone on and accomplished good things at other companies. And 2 of my ex coworkers transitioned into dev roles after going through hack reactor as well. They have all had positive experiences.

I have also heard good things about hackbrite if you are eligible. One of my ex-coworkers is an now instructor there and she cares passionately about cs education.

Source: I used to work in edtech in the valley so I have relationships or heard 1st hand accounts about these boot camps.
Well, Java does have a UI lib of its own and it doesn't make shipping an executable simpler.
Fuck FTDI.

https://www.google.com/?q=ftdi+brick
I spend 50 minutes a day on Hacker News.
I've had life long friendships start based on the fact that they had a C64 Disk Drive and/or printer.
"We are now more squarely in the age of Microservices, Mobile first, Polyglot, post-Java JVM languages, GitHub, Docker and the emergence of a world being eaten by Software."

sigh

I can see how Docker is relevant, Microservices are arguably relevant, maybe even GitHub, but that still leaves 4 out of 7 items that have nothing to do with continuous delivery.
https://www.youtube.com/watch?v=hPm54nXMX7E
Ask HN: Why can't we talk to each other here?
Someone made a comment on one of mine quite a while ago, and I feel I have some information that could make their life easier as a result... yet I am unable to do anything to help them because of the time limit.

I know it takes time and money to develop, but I also know its not very hard, and there are plenty of fanboys who will do it for you (me). So can we have some kind of PM functionality?

There is someone out there who is not as informed as they could be imo. Let me help them please... or perhaps I am less informed and they will help me even more than I could have imagined. :)

HN is clearly a community. I'd love to see it furnished with the tools to help it maximise its potential.
And then we get to the extreme paranoia where everything is generally recognized to cause cancer. And I'm not even convinced they're wrong, given the rates of cancer in people who (most likely) have never been exposed to anything (that they know of).

Although, then again, there's the problem of grandchildren of smokers getting cancer, when never having been exposed to the smoking first or second hand, only genetically through their parents.
I guess you missed the ironic intent of my comment. To spell it out explicitly: Signal desktop still doesn't work if you have an iOS device.
> Most other cultures were the same way. Everyone having sex with everyone made for a pretty bad society.

The opposite of true. I recommend "Sex at Dawn" for a good treatment of this topic

https://www.amazon.com/Sex-Dawn-Stray-Modern-Relationships-e...

TL;DR "Everyone having sex with everyone" pretty much maintained social cohesion in small societies for millenia.
I think that asking a question like this says a lot about your country.
Indeed. As a software guy I was sufficiently proud of my hardware effort that I neatly organised everything as a flying lead coming out of the Mephisto complete with strain relief and a tidy professional looking connector. Not as good as a mounting the connector flush somehow, but pretty good for me. It's still in my cupboard and it still worked well (as a chess computer) last time I tried it, although after 25+ years I wonder whether the EPROM is due to start shedding bits. Trying it out as a 68K dev board is more problematic - for reasons discussed in the main article - occasionally I consider having a go but these days I usually find life is too short for those sorts of things.
I like how he tries to supplant agile with something that doesn't even attempt to solve the same problems that agile (like waterfall before it) attempts to solve.

Both agile and waterfall methods attempt to give you a pattern by which you can predict when software will be delivered. That's the main business value. The suits don't care how the devs operate, provided they can get things on time.

Waterfall tried to do this by trying to understand the problem as fully as possible, to liken it as much to previously solved problems, and to involve gurus to say "that kind of problem will take X amount of time to resolve", and thereby create milestones and delivery dates.

Agile instead said "look, we don't know enough at the start of a project to do that. Let's instead keep track of everything we want to do. Let's try and estimate each set of tasks (stories), individually. And then let's rank them in priority. We can measure how good our estimates are, we can modify them, we can generate more data and determine what we'll have at a milestone, and then can either push back the due date, or at least recognize that we won't be able to ship the entire feature set at that time.

Continuous delivery can be done with either one of those (it almost never is in waterfall, but it -could- be). But by itself it offers a business nothing for planning purposes. All it does is allow an immediacy, a "as soon as it's done it's out in front of the users". This may or may not be a good thing to the business, but it doesn't solve the basic issue that business people want to know when they can expect a given set of features to be live.
Well, the malicious application can inject a password-field, and an unsuspecting user might not realize that (s)he is giving an app/attacker the password, and not the correct third party.

User education only goes so far, this type of attack can also make a web view that traditionally asks for a TOTP one-time password code susceptible to leaking a users password, even if the normal login flow doesn't ask for that password.

[ed: note that it's pretty trivial to eg: set up hidden cameras in voting booths, if you want to spy on a few people, or perhaps have people film themselves in a voting booth - the point is rather that if most people make an effort to follow the common rules wrt. voting booths, the system is reasonably secure. And it's not trivial to make similar claims about a (presumably) centralized on-line system.]
As someone with their BS and working on their MS are boot camps actually worth it or am I going to spending a lot of time learning basics.
It's legit.

The quality of education that you receive through the GT online masters is on par with the in-person version, and you'll receive the same ms degree as a "regular" student. It is not watered down at all.

However, since you'll receive the same education as a regular ms student, the coursework is heavy and intense especially if you hold a FT job.
Ah, good to know. I assumed the index was hosted as part of crates.io but I didn't actually bother to check. The point I was trying to make (even if I didn't communicate it properly) was that if crates.io goes away for good, the index will too and so it won't really matter that the code is inaccessible because cargo won't know where to find it anyway. Of course, based on what you said, it's certainly possible for everyone involved in crates.io to get hit by a bus and crates.io vanish when the S3 bill goes unpaid while still leaving the index up on GitHub, but if crates.io is taken down intentionally then presumably so will the index.
Isn't this made a bit murkier by the fact that practical training through work experience can be a legitimate part of such a course of study? It's not like they were working at maccas or something.
Yeah, I definitely didn't mean it as a downside to EVs, just that home charging stations are private facilities, not public ones. The smear campaign to discredit plug-in charging (and its lasting effect on public perception) is one of the most annoying consequences of GM's attempt to get out of the old CARB EV mandate (before they just bought off some politicians or whatever they did to make non-plugin hybrids count as "EVs"). Witness the Prius being sold with "you never have to plug it in haha" as a selling point despite the fact that converting it to a plugin hybrid dramatically increases fuel economy. Gah.
That link doesn't work for me, says request not found.

Can you clarify this a bit? I.e what does the Dropbox app do if you take a picture in portrait mode, and what does iOS do? Is the rotation info lost completely?
>There's a possible simpler explanation: his work was always priority #1 for him

The thought he knew more than doctors about medicine. That has nothing to do with work being priority #1, it's entirely based on your head being up your own ass.
Continious delivery is Agile.

In fact, regular deliveries are by many considered the single most important indicator of a working Agile process.
Except not all dependency managers support it. I'm not even sure if it's safe to say that a majority of dependency managers support it.
I don't know. I'm in favor of legalizing prostitution.

But I don't think all work is created equal. Doing intimate and personal things for money COULD be argued to be such a mentally or emotionally damaging task, only people being exploited would ever take the work.

I think any work which falls in to the category of /no one would do it unless they are horribly without options/ is work that society should strive to eliminate.
Here comes a mostly true simplification.

Printers speak an extremely low level protocol of "Once the printer ready pin indicates the printer is ready, load up one byte of data across 8 pins, smack a pulse out that says yo here is another valid byte, wait a bit, then repeat until you run out of data in the buffer to print". This is actually not too far from how parallel port hardware and port driver OS software worked. In practice the hardware ends up as something like 10 general purpose TTL IO ports, in fact in the REALLY old days our NON-integrated parallel printer ports used actual 8 bit latches like you'd see on memory busses from S-100 cards and stuff. Not the abstract concept of a latch but an actual TTL DIP chip like a 74LS373 or whatever printers use (I don't remember inverting or not or whatever) Newer hardware is way more complicated and "automated" and "buffered" but at some level the original PC compatible API locked down how low level it had to be and you have to be able to at least pretend you're GPIO to be "IBM PC Compatible". Standards being a great idea there are of course at least four SPP, EPP, and some others that spec'ed slightly more advanced but whatever.

So the high level protocol PLUS industry monopoly compatibility meant if you sell it as "IBM PC compatible" its gotta be able to speak at a 10+ pins of general purpose IO level.

The USB replacements do something different and appear to be printers and can no longer implement general purpose IO they implement "print a character" at the USB level not bit fiddling. I've not written a USB driver for a printer (on either side) so I'm a little fuzzy but what I've heard second hand is the USB level lives at an abstraction of "here's a packets worth of UTF-8 stream"

Note that there were weird situations for RS-232 serial where you'd synthesize signals by weird pulsing of DTR leads or CTS or whatever that can be pretty well messed up by transitioning to a USB implementation of "heres a bit stream".

I guess another way to look at it, is its easier to maintain compatibility across hardware generations for a single stream of bits so serial has it easy, whereas parallel was always a mismatch of high level byte transfer vs GPIO in the same system. The USB emulators only mass market making a printer work, not concerned about providing 10 or so pins of GPIO.

There is other fun... to a first approximation (aka its untrue) no one implemented multipoint networks on parallel ports. So latency was approximately zilch and much hardware hacking relied on that. USB of course is shared and totally non-deterministic and just maintains a long term average bandwidth. So trying to synthesize a beautiful sine wave works fine on actual hardware, not so well over a jittery USB. Its very much like the technical challenge of output sound to a local sound card vs stream VOIP across the public internet, which is really hard.
I was thinking last week how places like Nigeria will be the location of the next start up bubble as they pass through the threshold of punctuated equilibrium. They have unique problems that a bunch of tech geeks in the Bay Area and hipsters in Portland would never think of needing to be solved.
No, sorry. I started down that path, got frustrated, and eventually just did it myself.
FBI Harassing Core Tor Developer
I learned through logo in middle school.
A language sophisticated enough to later (high school) write programs that would take equations and graph them.

Plus who doesn't love writing software to create spirograph graphics.
let's not talk about reddit then
Exactly. Usage patterns and "deriving value" seem like very different beasts.
If it's not an error condition, you return it.

Libraries must not do any covert IO (in fact, any covert anything). A logging library is the only one that should log, and not their own messages.

They may write into some main application supplied collector, if it is not global, or if it is clearly handled as a message passing API.

The Java way is simply bad.
I know what you mean, it's great to feel like you've contributed to the sum total of humanity's knowledge like that.

And now my ego demands that I go check to see whether the one paper I've published is up on there! :D
A toaster running freebsd that connects to azures machine learning service, and automatically tells you if the Virgin Marys face is burned on there.

You helped create the future.
I suggest you to read Momo by Michael Ende[1], it is basically about this topic. Obviously, not only Facebook is guilty.

[1] https://en.wikipedia.org/wiki/Momo_(novel)
I wonder how much of an overlap there is with "waiting in line." because that's a big use case for me.
Fear of being at the bottom drives the able upward.
Is Nokogiri easy to install yet?
Yeah not gonna happen. Literally the only thing I use it for is chat.
While people are spending more and more time on FB, I find it that there is less and less original content uploaded. It's all likes and re-shares.
This is an extremely poor analogy. Chickens are not people, and I'm not alarmed by chickens getting sick. Prostitutes , however, are people and forcing them into hazardous situations out of desperation is not okay.
Whoa, wait a second. First you say cause and effect is backwards, so prohibition of prostitution resulted in the bad effects?

But then you say it made it more hazardous.

Those are two different things.
I think leaving contact information on profiles is enough.
USB latency is generally 0.25ms. PCI-Express latency is around 250ns. That's three orders of magnitude lower. I'm not sure how you can say that this will suffer from the same problem.
This file lock cannot exist outside of some intensely locked down binary blob which will be cracked in minutes. Your idea might make sense legally, but it doesn't make sense physically.
You can also do it out of band and have an API call that returns the server you're supposed to be connected to.
1,500+ Drone Pilots Speak Their Mind About U.S. Drone Regulations
But more importantly, you just can't beat the URL. How many more times will we convince the entirety of humanity to know how to visually parse "www.zombo.com" on a billboard or in a text message? It's easy to take the Web for granted, it's fun to snark about its warts, and there's a cottage industry of premature declarations of its death. But I personally believe that the humble little hyperlink is at the heart of the Web's power, competitive strength, and longevity. It was a century-old dream passed on from Vannevar Bush to Doug Englebart to Xerox PARC and ultimately to TBL who made it real.

URLs are great, but they don't have to be limited to the web. Or, rather to say, the thing on the other end of the URL doesn't necessarily need to be something the browser handles directly.

I'd like to see something developed that lets you do something like:

x11://myapp.example.com

where clicking on that link in a browser launches the remote app and then renders the UI locally using X11 remoting - as opposed to trying to render the application UI in the browser.

OK, I know, go ahead and say it.. X11 sucks, X11 remoting doesn't work on WAN links, etc. To which I say:

a. Fine, let's invent something better, that still avoid the need to pack every ounce of functionality in the universe, into a web browser.

and

b. That doesn't jibe with my experience anyway. Just earlier this week I was playing around and decided to launch a remote X app using X forwarding over ssh, over a public Internet link. Worked like a champ. In fact, it reminded me of how fucking awesome X11 remoting really is, and makes me long for either a resurgence of interest in it, OR (see a above) the invention of a newer, better version that everybody can be happy with.

There's also a lot to be said for delivering applications using Java Web Start as well. JWS is wicked cool technology that is tragically under-utilized. IMO, anyway. :-)
It was expanded back in 2013 to all federal organizations that spend more than $100M in research.

That was just an example link.
Of course, and I totally agree with their approach. I'm just saying the narrative eridius is pushing that somehow they can make assurances about things never being deleted totally false. For example, I'm sure if someone somehow put child pornography in a Rust crate it would rightly be taken down pretty fast (and not require a court order).

Also I just wanted to give a little history because eridius's original comment made it sound like it was a novel concept.
I see no indication that agile is dying. The consultant speak cult that developed around it is. The hugely processed SCRUM version of it seems to be. Yet the fundamental idea behind Agile (in the manifesto) seems to be as relevant as ever:

>Individuals and interactions over processes and tools

>Working software over comprehensive documentation

>Customer collaboration over contract negotiation

>Responding to change over following a plan

The process we've designed and use daily at Gridium most definitely adheres to those principles. We've tested and abandoned the idea of "sprints" and weekly estimation cycles. We have no idea what our "velocity" is.

Yet we collaborate with customers nearly constantly. We are highly responsive to changes in the business. We integrate continuously. We deploy very often. All ideas that I think where present when we all fell in love with the idea of "agile".

* Edit: Shame on me for not reading the article, because I basically summarized it :) Heap your downvotes on me HN!
Objective-C was the major inspiration for Java - you'll notice how little it looks like C++ - and therefore C# and co, so it's been very influential ever since the 90s.

It's not worth listening to anyone who dislikes Obj-C just because of the [] syntax, which doesn't matter after the first 48 hours.
There are other visas for that. I did an internship on a J-1 for example. I would find it hard to believe these students didn't know what they were doing was questionable.
Outside of hacker school (now recourse in NYC), I would recommend against attending a boot camp if you have received a quality CS education from you undergrad years.

Specifically, going to a boot camp is both a time (3-4 months) and a $$$ (20k - 30k) commitment. They will teach you the tools of the trade well, e.g tools and frameworks and will make sure you come out with a certain level of knowledge that fill most junior level roles.

However, if you have a bs computer science degree, you probably won't get much value of of these boot camps other than learning the tools of the trade, which are things that you can pick up on your own since you have a solid cs foundation.

However, it's not a bad option if you have both the time and the money, and feel that the commitment of a boot camp will be beneficial to you.

bur the quality of these boot camp varies and I would only recommend going to the highly recommended one, eg hack reactor, hack brite, app academy, and recurse.
At least the UNNJ t-shirt should be some kind of collector's item.
Am I the ink one who wants one of those UNNJ t-shirt?
Yes, but does the bottom have to be dehumanizing for this to happen?
I'm guessing this partially depends on region, and is of course partially dependent on both, but what is the primary factor limiting the lifespan of road surfaces: usage or weather (rain, snow, winter salt, etc.)? Certainly, there are some types of city infrastructure that deteriorate less from usage and more so from exposure to the elements over time (telephone poles, bridges, drainage systems). It seems that increased housing density would increase the amount of tax dollars for a given area of land without necessarily increasing the need for more roads or roadway area. One might argue that higher housing density means more cars, but if doubling the number of cars doesn't half the lifespan of the roads, then it's a win. Also, double the housing density doesn't necessarily mean twice the cars, because higher density regions are generally more walkable and there are greater opportunities for carpooling/ride-sharing/public transit.

So, basically, increase housing density so that more people are sharing established infrastructure. Fund the maintenance of this infrastructure using taxes that are population (or perhaps income) dependent, rather than property taxes.

Oh, and based on the cost and longevity numbers provided in the article, why would anyone ever use asphalt over concrete for a roadway surface? I assume some key factor has been left out of this comparison.