skysight-inc/HackerNews huggingface dataset:
Not so complicated if you plan for this sort of stuff ahead of time, or even at migration time. You can prepend your hashed fields with the algorithm used, and have a library that automatically handles them.

This also makes generating test data easier, as our library has a "plaintext" hash type, so we can just insert "$plaintext$password" rather than having to run a hash on the password.
Note: This is not mine. All credit goes to Hannah Mittelstaedt. I just happened to see it on Twitter and thought it was worth sharing.
There are probably lots of settler novels, but I found Vilhelm Moberg's books the most captivating things I've ever read. They are largely based on some Swedish settlers' diaries from the 1800s in northern USA.

Bootstrapping from very modest means, but in a very rich land (climate, soil, water, forest etc). It took a while to reach equivalent standard of living compared to the Southern Sweden they left.

https://en.wikipedia.org/wiki/The_Emigrants_%28novels%29
Such a personal choice. I don't mind the reflections, and I strongly dislike matte - everything looks dead & second-rate to me on a matte screen, so much so that I just gave away a matte 4k monitor rather than use it.
Apple's date/time support (part of the Foundation framework in both iOS and Mac OS X) is fantastic. Better than anything else I've ever seen.
A little more honest marketing would do the world some good. I'm all for having someone check and call out bs where it is found.
But you know what? It's not luxury to sleep on the sidewalk and get peed on by dogs after your house was bulldozed because it doesn't have indoor plumbing. Or because you didn't start building it in the first place. 30-story apartment buildings might be fine, but declaring buildings "uninhabitable" because they lack luxuries — and prohibiting people from living in them — is an injustice that falls heavily on the poor.
Ready-Made Java Containers, Part One
It is targeted to ARM uC's and also works on AVRs with enough RAM and program space (yes I've tested it). Write support requires a significant amount of RAM; I think about six 512-byte blocks. When compiled in read-only mode, it should need no more than two.

One reason for the RAM needs is that I use a block cache and I take care do to "atomically" certain related operations (on the block cache level). These are things like marking a cluster as allocated, decrementing the number of free clusters in FsInfo, and linking the allocated cluster to the end of a chain. These things require multiple blocks to all be present in the block cache at the same time.

I suppose the asynchronous design also contributes to the code and RAM size (though I did not actually measure the code size or compare it to other drivers). It may look like more that it really compiles to. Anyway would be very surprised if you show me another asynchronous driver - I couldn't find any!

Also consider that my code supports VFATs (decoding only, file creation is not supported anyway).

The design is intentional, I have sacrificed some RAM/program size for asynchronous operation and better reliability in case of random write failures (because of the block cache, all writes can reliably be retried later, avoiding corruption as long as they eventually complete).

Update: I estimate the code compiles to about 10kB with gcc for Coretex-M3 using -Os. This is certainly within limits of most ARM uCs and many AVRs.
Elon Musk: Fastest Way to Heat Up Mars Is to Nuke Its Poles
> First: Read the Mythical Man Month

I have, it's a brilliant book. Helped me greatly during my career. However it's about scaling an already broken (and late) project in a very naive way.

Luckily we've learnt a lot since then - and it turns out that decomposing the problem into 4-6 person chucks and optimizing for minimum dependencies is a good strategy to close-to-linear scalability :)
I forgot about games! although i'm not sure how much of a hayday it will be; ideally 3d touch would represent a progressive enhancement to the app, and not a core feature that is required for usage.
I can see it on your response (and it was what I was looking for) but I see no sign of it in the posts to this thread https://news.ycombinator.com/item?id=10093590
JointJS diagramming library v0.9.5 Released
Why Kik Let a Student Design a Major Feature
>Using something like "professional-looking LinkedIn picture" as a filter is just throwing out candidates for the sake of getting the number lower.

Who said hiring is fair?

>Any company that would be this lazy as to potentially throw away their best candidates in the first round of filtering on criteria that has such little actual signalling is not one that I would want to work for anyway.

For most companies (not talking Facebook and Google level stuff) it doesn't really matter -- and they could care less if you would work for them or if they get top talent or not. Any decent-ish programmer can do the work they require, so they are OK with being lazy in hiring.
I tweet mostly about new things I learn, interesting designs I see, etc.

This has the added benefit of being able to look stuff up if I forget about it.
Easy login sessions with Ember.js and Torii
Pretty neat trick porting over python unit tests to go. Any plan on sharing more details or open sourcing that part?
The startup scene is bigger one county south - in the Provo/American Fork area. But the Mormon culture is heavier down there. (Every place I've worked, there's been coffee in the lunch room. Everywhere else, it just was there. But down there, it felt like religious tolerance.)
I'm okay with a very light matte. Laptop displays however tend to be way too strong, and I prefer glossy for that. I can control my room lighting--I can't do anything about text looking like I'm seeing it through wet wax paper.
Netstrings look neat although I find the use of a redundant comma delimiter somewhat confusing.

Buffer overflow concerns are not applicable to SSMP however, as the spec explicitly restricts message size to a maximum of 1024 bytes.
Tap. Pay. Done.
Matte all the way. I can't understand why anybody would choose a glossy screen for any purpose.
Dupe of https://news.ycombinator.com/edit?id=10199162.
Another approach (used by qmail and I'm sure other programs) is to use the file system as a database. Process 1 creates a file into a temp directory. Once writing is finished, the file is atomically moved to the working directory where Process 2 deals with it. That wouldn't work so well if you need them to be processed in a specific order, though.
"This is about three years overdue."

I couldn't agree more

Recommended write-up: What is Heroku: getting started with PaaS development

[0] http://cloudacademy.com/blog/what-is-heroku/
Sounds like a nature inspired design by the brain tousands of cores at slower speeds.

Most likely maybe we will have a few speedy main cores for non parallel code like mobile Arm big little and then the thousands slower cores in parallel. Will there be transparent cloud execution where workloads can migrate from local cpu out to massive cloud cpu and back?

Kind of like GPU but for main CPU?
I still think of the scene in Zoolander where he takes the flip phone out of his pocket and it is about as big around as thumb. It was comedic at the time because manufacturers were trying to make smaller and smaller phones to differentiate themselves from the brick cell phones of the past, so this scene was mocking how far it could go. The irony is that now kids probably have no idea why it's funny because all phones are competing to offer larger and larger models.

I don't have a problem with the larger phones, personally, but I think it's interesting to see how quickly the industry has come full-circle.
> This is basically a marketing piece, what good is fact-checking it

Not sure about the US laws, but here in Germany, all marketing claims must stay to the facts, or the company can be sued.

(Which is why most marketing speak uses fuzzy terms that sound nice but don't convey any information. But that's a general trend anyway.)
Hackers R grabbing insider info making millions in quick stock mrkt transactions
Well that's not a very good point.
No, but it's resistant to parallel cracking, which is the hole being plugged.
Deploy anywhere, with hybrid deployments (Aptible + Heroku + AWS + whatever) and still have automated compliance evidence would be the holy grail. It's still difficult to extract all of the control information you need from many (any?) providers, which is why we built our container service.
It's just a personal preference. I don't think being a developer has anything to do with it.
Have you tried the emscripten port of SQLite? It's worked well for me... http://github.com/kripken/sql.js
Lots of chips are missing so what is it for?
Haha, oh the temptation!
Isn't that what I said in my second paragraph? As I said, for that to happen, you need people smart enough to come up with that scheme but not smart enough to realize how insecure it is. Possible but unlikely. "Imply" does not require a complete guarantee.
To tell the truth, Python is an easy target here, but I doubt 99.9% of the projects in C or C++ care to manage memory as closely as GHC does under the hood. (The same way as they don't manage concurrency.)

Some times, it's even better not to look.
The generalized popular programming industry, largely in web, desktop, or mobile high level programming. Not an entirely useful generalization, but one that is common enough to habitually pick up on when "we" is used in such a context.
>Noone actually does that in real life

You'd be surprised. Might not be so explicit, but randomness (ie luck) plays a huge role in filtering process.
Really interesting...this is the first I've heard of them (I'm nowhere near the finance industry). I wish finance companies weren't so tight lipped, I can't find anything about their tech stack.
Current IBM Dev here. I know several IBM teams that use slack & github. There should be no problem with that.
Ask HN: Potential IP conflict with currenct company?
I came up with, what I think, is a good business idea. Admittedly the idea was tied to what the startup I currently work for does. I've been working here for 4.5 years, and we've been around for 8. I'm starting to think we don't have what it takes as there is a lack of clear direction from the top, and marketing and dev are undercutting each other in product planning meetings (the CTO and VP of Marketing have very different visions for the company and the CEO just splits the difference, which is starting to not make any sense anymore).

I proposed the idea, and there was definitely interest in it (particularly from the CTO and CEO). I came up with a reasonable proof-of-concept, but they now want me to create the full blown idea in my free time, without any officially allocated resources. This will likely take at least 100 hours, many of these hours could be reduced if they gave me a dev that knows parts of the architecture that I don't. If I leave the company and just do the idea for myself, could I get in trouble?
The iPad Pro Has a Product Marketing Problem
What does react use typescript and coffescript for? they are listed as a dep in package.json
How to Prevent Stress from Spreading Like a Disease
Meaning that any language that doesn't have monads, you're defining to not be useful? Or meaning that monad-the-pattern is everywhere, in every even barely useful language, even if there's no explicit monads in the language?
I implemented a character manager using TaffyDB[1], loading lots of static data upfront. Made calculations using cross "table" lookups much simpler from a coding perspective.

[1] http://www.taffydb.com
Open Source Legal Terms on GitHub
About your point about Lotus Notes: I interned at IBM 3 times, and was never forced to use Lotus Notes. No one whom I worked with at IBM used Lotus Notes either. We used either Open Office or MS Office.

The most popular IBM software we used was SameTime for instance messaging and it was actually not bad at all.
We just test that their class systems work properly with React:

https://github.com/facebook/react/tree/v0.14.0-rc1/src/isomo...

We don't use either one outside of the tests.
Brain Computer Interfaces for Mobile Apps
This versioning is pure crap.
"However it's about scaling an already broken (and late) project in a very naive way."

If that's all you remember of it, you really need to reread it (and I find myself mildly skeptical that you did in the first place - although it could very well be that it's been long enough you thought those ideas were elsewhere). The title - and Brooks' Law - is about that, but the book covers a whole lot more. Including discussions of approaches to decomposing problems into <10 person chunks and optimizing for minimum dependencies.
If the upgrade process from 10.9 to 10.10 regarding homebrew is the same I'd disable and remove homebrew before upgrading. It made the upgrade process come to a complete crawl.
How to design for mobile UX
My family once built something like this. We used ready-made roofing materials, but the rest was branches and small tree trunks, dried grass, and clay. The process went something like this: dig a hole until you hit clay. Put four posts for the corners such that the hole is in the middle. Put up a basic slanted roof and put straight branches over it, nailing it all together. Put grass and mud mixture on top of that and let dry, then cover with roofing material. Now you have a shady place to work! Keep digging clay out of the center hole and store it. Put more posts where walls will go. They don't have to be super close: 1-2 inches apart is just fine. Mix clay with water and grass again to make mud. Fling it against the newly created walls and smooth it out with a board. Wait to dry. Repeat form the inside and out until you have a solid 6-8 inch wall and none of the wood is exposed. The door was another ready-made item but technically didn't have to be. Once the four walls are up and the door is installed, create a floor and a hatch into your new cellar.

We then expanded this one room, adding three more. We built a wood burning stove in one of them using clay bricks and another stove outside. Once you can stay at a place like this work goes much faster. There is a huge advantage to using clay as the main material too: it keeps the inside very cool, and it is very cheap and easy to work with.

Then we got even crazier and bought a bunch of bricks. We laid the foundation of a brick house around the mud hut, then built up walls around the mud hut. Once the walls and the roof was up, the sledge hammer took care of the mud hut and the materials were carried out the front door.

Edit: oh, and we had no power at this location, so we did all of this using only hammers, manual saws, screw drivers, and a manual drill. Almost all the nails and screws were salvaged.
I am curious if the TSA even uses these keys? I am sure 90% of the time these TSA approved locks are attached to luggage with zippers.

For some reason I have a hunch that TSA agents probably just part the zipper with a bic pen, do whatever inspection is necessary, and re-seal the bag. Seems a bit quicker than fumbling around for the right key.
>there's no useful information in a photo

There's lots of useful information in a photo.

A talented HR/CEO can size up a lot of things from it, even from the way the candidate is dressed in the photo.

"Hmm, too old, too quirky looking, doesn't look a good fit for our culture, fucking hipster I hate them, too slopilly dressed don't like working with such guys" etc.
Apple Pencil – it's about what's needed now
> but that's less clickbaity

They cracked millions of AM passwords. That's not an exaggerating, but the fact of the matter.... since when to titles need to be tl;dr's
Can you help us understand why?
As much as I fear this will drag StrongLoop, I feel that this is an excellent fit. StrongLoop has been focused on building "Enterprise" tools and module around node, as well as working on whitelisting/reviewing various modules... This is a good fit for IBM and their clients who are inclined to also want to have "approved" or "certified" modules to be able to use separately from the rest of npm.

As much as I like the power/openness of npm, a lot of corporate environments move more slowly... modules need to be cleared by legal and usually limited to specific versions. Having more resources to do this is a good thing and can only help people who are working for financial institutions (as an example).
Perfect is the enemy of good I guess. If I'm building a product now, I want a library that works well now and never breaks when I upgrade to the latest version. If someone gets a great idea for a better library, make it a separate library. So backwards compatibility is definitely a feature I want.
Good luck keeping users by forcing a long, random, unique password on every one that signs up.
I tend to think that a certain amount of rote arithmetic is required, and, well, if the student doesn't like it, I'm not sure what to do about that. Reading and spelling are the same way... if you want to be a fluent reader, you need to put the time in.

What I learned in elementary school is OK. (There my objections would center more around the cohort system being terrible, but that's another objection. Also, I have to qualify that because the education system considers screwing with elementary math education one of their primary mandates.) But math education flings itself off the rails when it starts doing symbolic manipulation. (And if anything, every time they screw with it they're flinging themselves off the rails harder and sooner.)
China’s startups are lying to you, and there’s not much anyone can do about it
Um...

that's exactly how salary negotiations work. If I don't do a good enough job, you demote or fire me. If I do a good enough job AND the market says I should make X, then X - Y isn't fucking good enough, and you should be warned that I'm happy to find an employer that WILL pay me what I ask for.
So I guess you're saying that microservices are pointless, the real problem is tight coupling?
Because their senior UX designers could veto anything they didn't like anyway, and because nobody much cares for Kik so the stakes weren't that big in the first place -- besides they could use the PR.
Evolving ASP.NET Apps – Replacing the Mega Postback with Web Api
> the Russian decision in the late sixties to develop as their next national computer series a bit-compatible copy of the IBM 360 —the greatest American victory in the cold war!—.

https://www.cs.utexas.edu/users/EWD/transcriptions/EWD05xx/E...

Your quip reminded me of the above quote from Dijkstra!
Show HN: Paint with Donald Trump
Decode Your HTTP Traffic with Open Source Sysdig
There are multiple definitions of species, and we choose whichever abstraction is most useful for a given approach.

The concept of species exists purely as a human, scientific abstraction: evolution/biology doesn't give us absolute categories that you can unambiguously put any organism into.
Or maybe, "Huh. That's interesting. Maybe I'll make a new filesystem object type or add an optional disk buffer for pipes."
10,000 years is only 500 generations. Consider that we usually have reliable ties from the present going back 4-6 generations (our great grandparents, assuming everyone must age to be older than 20 before reproducing) and you realize that we're privy to a shocking 1% view of human civilization timewise. Amazing!

My grandparents grew up without running water, as did everyone before them.
Semantic Versioning is not a magical cure-all. It's still up to the author to make the right choice about which number to bump.

We have a node/gulp-driven build with, ultimately, about 500 dependencies. We don't store node_modules with the code, we run npm install with each build. This leads to periodic failures because some sub-sub-sub-dependency bumped number 3 when it should have bumped number 2, causing unwanted build-time behavior. Even if our package.json lists specific versions of top-level dependencies instead of ranges this will happen. It's aggravating.

Projects exist to bundle up known-good node_modules and restore at build time to avoid this. NPM offers the concepts of shrinkwrapping and peer dependencies so you can tell consumers which specific version of each runtime dependency they have to use as well. IMO if SemVer actually worked in practice, none of this would be necessary.

Some of this is an indictment of node/npm - maybe Ruby is just better - but I still think SemVer is overestimated.
Hi. Your post read like a blast from the past. I started out in a Ruby on Rails shop with an internship making $10 an hour. My laptop was an old HP, with fans that whirred (for some reason HP can't make/procure fans to save their lives). Everyone else had sleek new equipment. I built a couple great features, squashed tons of bugs, and learned a lot along the way. Near the end, I talked with the founders about raises a couple times, but it's clear what they needed was a way to save money on development for as long as possible. And what I needed was the experience of working with a real software team.

We all got what we were looking for. It's just a question of when you don't need that basic training anymore. Sounds like that time came for you around the same time it did for me. I can tell you - at that point, the only way up is out. You are much, much more employable now. Don't "beg for work" ... present yourself well and ask for market-rate. You said that's $75,000 in your area? Better yet, say you're looking for a range of $80-90k and see what they say.

I've got a question for you, and maybe an idea. Did you sign a non-compete agreement beyond just your term of employment?

Even if you did, it might not be enforceable in your state. Go to the billion-dollar rival and tell them how you've got almost a year of domain expertise under your belt working on a similar product. You're looking for that next step - full-time Software Engineer, and a chance to build on what you already know. You're able to make clear comparisons between the two offerings, and I bet you have some ideas about how theirs could be the best of both worlds. Oh, and when they ask you...

"Why did you leave your previous job?"

Don't panic. 18 story points on your last week, remember? You're a sharp web developer who rapidly rose in value - far faster than your perceived value to a CEO who forever saw you as "the cheap intern." Since you couldn't reach an agreement that met your salary requirements, you parted ways. Now you're able to devote more of your time to the search. That's all you need to say - so practice saying it with confidence.

Email real people at the target company (email is the new cover letter) or start asking questions on Twitter - don't just drop your resume in an upload. Start a conversation. Get your Team Lead and as many coworkers as possible to jump in with recommendations, when they ask for references.

My next offer after the internship was a real one, at market salary in Silicon Valley. There's light at the end of the first-job tunnel. It's tough now, but please believe me when I say it does get better.
> It's bad for performance, security, and maintenance.

Compared to what, exactly? Ruby? I'll give you Node for double performance and roughly equivalent (and annoying) maintenance, but PHP's security story, with or without the various popular frameworks, is at least as good. Any stack built on the JVM has its own set of tradeoffs -- I would rather maintain PHP than any standard JavaEE solution, but I would rather maintain anything built on Clojure's Ring than PHP. These days Python with Flask is my go-to solution for quick things where I might have used PHP in the past, but even then there are tradeoffs, near the top being you can't just deploy to any shared hosting service that's been around for over a decade.
Optimizations are so fun. But the key is always to measure from end to end before you investigate, and after you change things, in a comparable manner. Too many people guess or theorize or make random changes.