skysight-inc/HackerNews huggingface dataset:
I doubt it would be hard, but I don't see why anyone would bother.

At my last job, we would occasionally need to dig up old code because Microsoft finally removed something they had deprecated several years before. I think it was always amusing.

One case that stands out was a utility program that would update data for our users each month. I needed to change something about the string handling. After updating the data, the program would enumerate all running software and kill any copies of our program (so that they would need to read the new data on startup). I noticed that we went through the trouble of enumerating 32-bit and 16-bit programs. Since we hadn't shipped a 16-bit version of our software since the '90s, and we had changed our data format significantly since then, I happily ripped that code out. I don't think you can find information on 16-bit Windows on MSDN anymore.

I guess, to put it another way, who's shipping 16-bit programs?
Ah, thanks for catching that subtle-but-important mistake. :)
The master's in CS can be useful if:

1. You have an undergrad degree in liberal arts
2. You pay as little tuition as possible
3. You take no time off and continue to work FT

These apply to me -- my undergrad was in English, I paid 6k total (27% of the 21k total cost) and went to school at night over 4 years while my career continued to progress.

Most of the people in my program couldn't write a FOR loop if their life depended on it, they viewed it (incorrectly) as a jobs program while the school needed the $$ to keep the dept afloat, so I'm not surprised they fared poorly in technical interviews.

But that doesn't mean the degree isn't useful. If you're already a programmer, it helps get your foot in the door at many places. HR managers/recruiters feel more confident forwarding on your résumé, they can't parse your GitHub repos.

The degree is icing on the cake, it's not going to magically turn you into the Cinderella of Programming if you have no real-world experience. I got my master's with a QA and a paralegal and today? They're still a QA and a paralegal.

That being said, timed technical interviews are almost universally asinine, IMHO. When in real life do you have 10 minutes to figure out a problem? Or are prevented from Googling the answer? The measure of successful programmers is how efficient and professional they are in problem solving, not how much useless information they can keep in their head.

Things I've never had to do in 'real' life:
-Never had to split a linked list given a pivot value
-Never had to reverse a string or a red/black tree
-Never written my own implementation for Breadth First Search

etc etc

Personally I'd rather see take-home assignments that roughly approximate the type of work you'd do, which in my career has been churning out new features or applications. Does knowing the time-complexity of radix sort vs heap sort really have a material impact on your effectiveness as a programmer? No.
I'd be interested in learning about the DOS version. I remember using it but it was a text mode application as far as I can remember (2.0?)
I have no idea why they would do that, it just counters the claim "obviously, there will need to be some people with the means to actually buy the goods". If people are needed to buy goods, we can dodge around that by having the robots act like people and buy the same goods in the same patterns, and then there won't need to be people again.

I have no idea how employees-buying-goods sustains our current economies (although I suspect it doesn't, and that they are inflationary, debt driven, and unsustainable).
> and going full-Amish.

Eh, they're on no high horse.
That sounds fascistic! Do you mentor them? Or are pair programming and code reviews part of your company culture?
I can only state my perception about required qualifications I saw in job postings; big companies: university, small companies: skill A, B, C.
You're conflating a companies public web presence with the size or complexity of its internal network. They are not related.
Labor Productivity measurement depends on GDP, so it suffers from classic GDP mismeasurement error. GDP only measures $, not value, so it fails to measure technological improvements in a competitive industry -- so it utterly fails to measure productivity (hence the charts showing that labor productivity growth is always tiny).
Your computer today costs $1000, but it's 1000x more useful and more complex than that $2000 computer of 30 years ago. In GDP / Labor Productivity terms, though, it's value hasn't changed at all -- in fact, it's DECREASED, since your new computer costs less than the old computer!
Important THings to Consider Before You Deliver Your Baby
> It's usually better to write single-thread code and avoid multithreading except in few carefully written places.

implies that you did have some problem with multithreaded code, which is why you ultimately chose to avoid it.

Stuff like rayon in Rust lets you sprinkle multithreading over your codebase very easily without needing to worry at all, because Rust keeps it safe.

> but its memory management model is much harder to use

IME it takes some getting used to but once you do it's pretty automatic and you don't have to think about it much. YMMV.
Why I started higher.team
I didn't see a link to any source article.

I'd like to see some safety features built into Siri. Example: iPhone knows you're on a road, traveling at highway speed. Suddenly you're no longer on the road, and your speed has decreased and you've stopped. the accelerometer picked up unusual movement. Siri could ask "Are you ok?" a few times and if there's no verbal response, it could summon help. Onstar already does this, but I think that more people have iPhones nowadays than Onstar. It could be a life saver in rural areas or less frequently traveled roads. The person that was 5 minutes behind you might not even notice that an accident has occurred and will drive right by.
Ask HN: How was the the Reddit mobile app built?
Did they use alien blue as the foundation? What technologies/frameworks were used?
A recent book that explores the loss of community when combat veterans come home, and how this may contribute to PTSD:

"Tribe: On Homecoming and Belonging"

https://www.amazon.com/Tribe-Homecoming-Belonging-Sebastian-...
How is this possible...what language/framework/tool was this in or for?
List of Some Prominent Companies That Test DNA
The original WOW was doing a 16-bit to 32-bit layer.

WOW64 (in 64-bit Windows OSes) does 32-bit to 64-bit.

The naming of System32 made sense back when they came up with it, but now it's a bit ridiculous. However, since there are so many incompetent Windows programs using hard-coded paths instead of SHGetFolderPath (including, BTW, literally every Java desktop app that doesn't include its own shim-- the JVM itself has this bug!), it's something Microsoft doesn't have the ability to fix.
A common point I've seen is that "Functional programming sees the aliasing vs mutability issue and declares that the solution is to avoid mutability altogether. Rust goes in a different direction, saying that only aliasing XOR mutability is allowed".

It's solving the same problems, and the solution ends up having many similarities with functional programming.
They're not particularly difficult. You usually take the algorithm definition and implement one, as you did in the university or in the Coursera algorithms course. Fun, you might learn a thing or two about the language you're using.

If the point of the exercise is a TRIVIA question, leave the interview. On the other hand, if the point of the exercise is not to get the right solution but see how you think and how you use basic programming blocks, then you're in the right place.

I've used the linked list question. And the goal is not for me to check if it is "not difficult" for you. Because I might not be able to teach you what a linked list is in 5 minutes while you're nervous in a technical interview. But to work on technical problems and see the following:

- Can you speak your mind so your peers know what are you doing?

- Will you ask for help?

- Will you accept help and feedback?

- Can we have a discussion about something that there are many "right answers"?

- Do you know the basic building blocks of the language you decided to use? <-- This plus javascript plus references is very funny.
Even they didn't think of it first. I heard about this application of ML about a year ago.

For every "why didn't I think of that?", there's probably a bunch of companies already doing that.
Yes, I should have quoted those bits.
To be fair, Alan "flaw in the model" Greenspan was still Chairman of the Fed in 2003.
“It is certainly something that, before legalization, we almost never saw,” Heard said. “Now we are seeing it quite frequently.”

Something doesn't seem right with that statement. Is the increase in usage because of legalization so dramatic that it resulted in a noticeable, significant number of people seeking treatment for this illness where it became "noticeable" among physicians? The article mentioned that people won't admit to usage if its illegal, but something still doesn't seem right.

And then it immediately segues to a "slacker pothead becomes ambitious again" with the quote "“Now all kinds of ambition has come back. I desire so much more in life and, at 37 years old, it’s a little late to do it, but better now than never,”"

I'm not going to dispute his experience or pot laziness in general, but the transition to that quote seems a little too opinionated to me.
I sometimes use the fork button just to get a copy I may or may not play with over the weekend.
does anyone have recommendation on a text that is mathematically heavy but also looks at modern approaches/appleications?
You just described the plot of The Time Machine by H G Wells.

I also recommend the movie (the original).
Most, not all, but most of the good developers I've known learned to code when they were teens. CS skills have been discounted endlessly compared to other engineering professions solely because it doesn't cost anything to learn. Other forms of engineering cost a lot of money to learn beyond the knowledge required for the job.

That doesn't mean software dev is any easier. And, it's great that CS has such a low barrier to entry, and hopefully open source keeps it that way. Unfortunately the same trait makes it sound like "something anyone could do". Anyone hiring in the industry knows this is not the case.

The same trait results in 80% of those calling themselves "developers" being radically incompetent. It's one thing if you're electrical engineer that works daily in Cadence doing LVS and DRC, your license alone could cost 100k a year. Contrast that with someone who's git cloned react-starter and setup a website on AWS. The barrier to entry is so low for comp sci that credentials and accomplishments mean little, and interviews are absolutely brutal as a result.

So we get to where we are now. Interviews mean everything because degrees, references, and personal accomplishments mean so little in CS. The interview is your gateway rather than a solid degree program for other engineers.

How do we fix it? Making programming less accessible is obviously not the right way. We need a solid accreditation program like longer established professions have. CS is very new relatively (the first programmers are largely still alive, which is astounding). God help you if you go to an unaccredited electrical or mechanical engineering program, but the large majority of CS programs aren't accredited at all. Employers need to know which schools are good beyond the top 20 so they can hire effectively, and engineers need to know the same to decide which program they want to attend.

It's going to be a vicious cycle until that happens. Endless "CS programs" that don't teach you anything. Borderline scam bootcamps (some are good, but who?). Shaky employers grilling the hell out of anyone that comes through the doors. It's going to suck for everyone in the space until we have some formal definition of someone thats been properly trained. Take the bar exam for instance; In most states you can take it without any schooling, but only those truly knowledgeable will pass.

Someone that passed the bar? A lawyer. Passed your boards? A doctor. Passed CS degree program at school X? Who knows.
At least in Seattle the trails mostly have a speed limit of 15 mph for ALL vehicles. It's real fun when they actually put cops on the Lake Sammamish river trail and bust (actual tickets) the spandex warriors who think 25 mph is a good idea on dead flat river trail (real hard there buddy) full of strollers and kids and dogs on leashes.
"I'd like to go on record with my own prediction: human labour will become more fashionable. Robots invading every day life will happen, and it will eventually make people appreciate human labour more. entire new industries will be created (or nascent ones expanded) around "the human touch." Hosting something, keeping people company, writing personal letters, drawing, etc., while the robots do our menial tasks."

Will these activities be more expensive? In ^The Diamond Age^, Stephenson describes how the rich purchased hand printed newspapers while the proles watched the glyphs on public feeds.
Thanks for pointing me to this reference. I have implemented the baseline model mentioned in this paper. A sharp rise of 4% in classification accuracy is clearly observable. While there would be an improvement due to theoretical reasons, the difference between improved accuracy and original accuracy might get less on introducing other factors. It is on my TODO to add new results on different models and by introducing other things in a simple CNN as well.
I was going to leave basically this same comment -- I like Go, but the fact that it doesn't have nice locking support always gets to me.

(Almost every Go program I've written uses goroutines so I end up using locks in almost every program I write)

There's no way to do this without language support or sacrificing perf with interface, so I get why nicer locks don't exist, I just wish they did.
Simonyi, I think he goes by. His example code from his dissertation where (again - I think) he first espoused the theory would have earlier examples still. Word was his first major project, though, and probably the most canonical "first exemplar", if such a thing is meaningful.
Interviewing skill is one way you get a job. After you've been doing this for long enough, and have a reputation, you tend to just get jobs by referrals.

I decided in my last change of positions to try interviewing for jobs like most people without referrals, since I had several other referral positions open.

And I was horrible. I was ridiculously bad, and couldn't get a job at jobs that paid less, and were for less skill. It was quite hilarious.

Thankfully, all of the referral jobs were begging for me, and that was fine. There was no real loss, but it was a bit concerning that if I didn't have an extensive connection network that I would be in a significantly worse role.
I'm Jason Fried, CEO of Basecamp, and This Is How I Work
According to the Boston Globe it's 34% [1]

According to that link its claim that a fully loaded A320 uses $2.50 worth of fuel from DC to NYC @ 105MPG.

Solving for $, they're claiming jet fuel $ = 1.33/g

That puts jet fuel at half the price of unleaded in many states, including California.

I didn't believe that until I checked the price online and found it's currently @ $1.50. Didn't know jet fuel is cheaper than gas.

One additional note - DC to NYC is a very short flight. Ratio of fuel cost to ticket price likely increases with flight distance.

1 - https://www.bostonglobe.com/business/2014/11/17/fuel-prices-...
He was probably the pot smoker equivalent of an alcoholic which would explain everything from physical health problems to mental problems.
A good one though.
Made a similar comment above, but that was entirely true for myself. I have worked on amazing things as we all have in life, petabyte databases, and just the most incredible setups.

But when it comes to an interview, I cannot get a job several levels below my own (without referrals).

With referrals, I am offered the moon and the stars, complete pick out of a tremendous number of amazing jobs.

But any random interview, and I totally bomb it. I wonder how many out there are like that as well. It feels rather strange from my perspective, but maybe it's fairly normal?
Of course, you can access `/proc/self/mem` safely so technically it's all possible in safe code.

But that's not something Rust can prevent.
Facebook feature helped promote a fake news story about a Bangkok explosion
> the compiler won't let me get it wrong. It's far far far too easy to screw up multithreaded code if you're using any kind of shared data, and Rust is the only language I know of that truly makes it safe without compromising on performance.

While I am, in general, a fan of Rust's focus on safety, I think this particular feature (data race prevention) may actually be somewhat problematic in terms of making code safer. I'm worried that it may be sort of analogous to "all-wheel-drive" being marketed as a winter driving safety feature that ends up (perhaps apocryphally) causing more accidents because it instills a sense of overconfidence that results in drivers neglecting more important/effective safety practices (reduced speed, snow tires, etc.). I think it's beneficial to read one of the Rust issue threads, "Rust does not guarantee thread-safety #26215"[1], about why they stopped referring to Rust as "thread safe".

Data races only occur in the context of "casually" sharing objects between asynchronous threads. That is, accessing a shared object from asynchronous threads directly, instead of through a "fail-safe" access control mechanism. Some programmers may be of the position that directly accessing shared objects is perfectly fine in some contexts. In those cases Rust's data race safety feature is a plus.

But data races are really just a subset of race conditions, and Rust doesn't prevent those other race conditions. The practice of directly accessing shared objects is prone to both (low-level) data races and (higher-level) "non-data race" race conditions. I'm worried that the larger effect of touting/marketing Rust's data race safety is to "(over-)legitimize/condone" the practice of "casually" sharing objects asynchronously, resulting in the neglect of prudent access control mechanisms (even if only by the inexperienced), and an increase in "non-data race" race condition bugs.

So, in the interest of public safety, perhaps all-wheel-drive cars should be bundled with some sort of warning/notice that prudent winter driving practices (and speeds) should render all-wheel-drive almost irrelevant as a safety feature. And perhaps an analogous one for prudent asynchronous object sharing practices and Rust's data race safety.

[1] https://github.com/rust-lang/rust/issues/26215

And a related article on safer asynchronous object sharing in C++ (shameless plug): https://www.codeproject.com/articles/1106491/sharing-objects...
I helped make this (with the google data arts team), happy to answer any questions about it.
While true, not many casual cyclists can maintain 250W for more than 10-15 minutes. And 750W is an all-out sprint for many casual cyclists. 1000W-1500W is a sprint for trained cyclists.

So, that 1000W motor is, in theory, as fast as my sprint, but for a much longer time period. And also in excess of the speed limit on a residential street.
Real-time LED strip music visualization using Python and ESP8266
Most trips during high traffic are single passenger. Self-driving taxi services will right-size the vehicles for the task, which will reduce congestion some amount, and the vehicles themselves will drive in a more uniform fashion than humans, which will alleviate traffic waves and congestion due to accidents.
Further on down the page you'll find a post called The Borderlands Gun Collector's Club (http://steve-yegge.blogspot.com/2012/03/borderlands-gun-coll...), and it turns out to be a fascinating explanation of an accidental token economy in Borderlands and is definitely worth a read.
No, the other way I could disagree. I thought the first one was the closed-off claim.
Why didn't we just stick with bread and rice? How much bread and rice could you possibly want? The point is; you can't envisage what the needs of tomorrow will be. If we truly automate all the necessities of life, then we could for example spend more time doing creative things or researching the some new technology. In a world where material things are abundant, the intangible will be worth more that is currently is.

Maybe one day, an average job might be controlling a fleet of drones mining an asteroid. Building all those Star Destroyers takes a lot of resources.
Rust-parallel _is_ fast, and there is clearly a niche here, that GNU Parallel is unlikely to fill: By design GNU Parallel will never require a compiler; this is so you can use GNU Parallel on old systems with no compilers (Think an old, dusty AIX-box that people have forgotten the root password to). This design decision limits how fast GNU Parallel can be compared to compiled alternatives.

But the main problem with rust-parallel is that it is not compatible with GNU Parallel (and according to the author, it probably never will be 100% compatible). If you use rust-parallel to walk through GNU Parallel's tutorial (man parallel_tutorial) you will see it fails very quickly.

(Full disclosure: I am the author of GNU Parallel. I fully support building other parallelizing tools, but to avoid user confusion, I would recommend calling them something other than 'parallel' if they are not actually compatible with GNU Parallel. History has shown that using the same name will lead to a lot of unnecessary grief: e.g. GNU Parallel vs. Parallel from moreutils).
> Same syntax applies.

Except that is not entirely true: For instance according to the author the '{= perl expression =}' will probably never be supported.

(Full disclosure: I am the author of GNU Parallel. I fully support building other parallelizing tools, but to avoid user confusion, I would recommend calling them something other than 'parallel' if they are not actually compatible with GNU Parallel).
The boxing there is perfectly idiomatic. Your code is likely to result in a pile of unnecessary code bloat, due to monomorphising the generic function twice, rather than just using dynamic dispatch (the overhead of which is likely trivial for IO operations).

I would say that the dense layout is more confusing/weird than the actual operations the code is doing.
FWIW that the borrow checker has nothing to do with multithreading, all the guarantees enforced are important in single threaded contexts.

http://manishearth.github.io/blog/2015/05/17/the-problem-wit...

It's a prerequisite for safe scoped multithreading, but that's about it.
The main reason we see all these relatively information-less blog posts / tutorials is because most people on HN are afraid of the math. If you're not afraid of the math (or have a relatively strong math background), then honestly you can jump into the CS 229 Stanford lecture notes and homework assignments. If that's a little too heavy for you, you can also start with the MOOC version of that course (which is a very watered down version of CS 229).
That's a problem with... "people looking for shiny things". There are many shiny things, and they loose their shine quite fast.

It is true that many managers, recruiting agencies (almost 100%), and HR, will look for the keywords of the technologies the company is using. So if they use the new Angular 4, they will look for that.

But there are companies that look for the basics: do you know javascript? Have you worked with SPAs? And these are the ones that IMHO deserve your time to apply.

Because tomorrow, today's current trends will be tomorrow's trends. Companies looking for people that can adapt say a lot about what kind of work place will you find there.
Yes, if they meet certain reasonable conditions (e.g. they're identified separately on the bill).
HexGL, a futuristic HTML5 racing game