jkeisling/hacker-news-corpus-2007-2022 huggingface dataset:
My one caveat: wherever you go, there you are.

You must know that many in tech have a very different experience than you (proud of their work, like their colleagues, feel care and development from their boss.)

Similarly many in academics love their work and others hate it.

The difference probably has to do more with who you are / how you go about it / attitude than the field.

It would be valuable to reflect what makes you so miserable in your current field while others are able to thrive. I don't know your situation but some guesses: do you have enough focus on getting into the good environments (eg, Google?) and if so - what's holding you back? Skills, drive, attitude? Do you relate to people or are you a judgmental asshole? etc etc.

I don't know the answer but what I am saying is - you probably won't be happy in academia or anywhere else unless you figure out what's making you not happy where you are.
Get a better keyboard.

Switch to COLEMAK.

Do speed punching drills.
AFAIK, I remember reading something about Instagram moving into Facebook datacentres some time ago. I believe they were on AWS before the acquisition.
Paper: https://arxiv.org/abs/1903.03129

Code: https://github.com/keroro824/HashingDeepLearning

Edit: Here is the new paper referred to https://arxiv.org/abs/2103.10891

Here is the new code: https://github.com/RUSH-LAB/SLIDE

The paper I linked above was the first paper of which this is supposed to be an improvement.
It's fascinating and inspiring and exciting to watch this "hackers all the way down" ecosystem grow. What'll it be like in five years? In ten?
Here are the books I've arrived at, after some research -

1. Graph Theory - Adrian Bondy/USR Murty

2. Graph Theory - Diestel

3. Intro to Graph Theory - Douglas West

4. Introductory Graph Theory - Gary Chartrand

I guess I'll flip through a Linear Algebra course once - to see if I need to brush up there as well.
Neat, but misses the point.
I'm a little confused what you're asking for. Do you want them to run the web store as well, so you really don't have to think (such as yahoo does?), or do you just want somebody to process transactions for you, (such as PayPal, Amazon Payments, and Google Checkout do?)

For somebody willing to drop 30% (or even 3%-5%) on a payment processing solution, there are lots of them.

But, I bet we could convince Steve Jobs to create "Apple Payments", and charge you 30%, and I bet there are a lot of people who would do it.
For as much good content as Smashing Magazine has, there is an equal share of brain-dead layout going on. I understand the need to monetize a website, but at some point, content providers are going to have to learn a little bit about economics. The solution to plummeting advertising rates isn't to increase the supply of advertising space. That's exactly the opposite of what they should be doing.

As an advertiser, I wouldn't even begin to consider advertising on Smashing's blogs. There are ten items (if you include their book, twitter, and Facebook plugs) on that page competing for my attention before I get to any content. The task-focus for someone viewing that page is to find the content. It's a horrible game to foist upon your readership.

If anyone is clicking those ads, it's either by accident, or because they're thinking to themselves, "Ok, obviously Smashing is hard up here, otherwise there wouldn't be 7 ads and 3 plugs."
I'm sorry but this is a tiny fraction of CSS3. Lets see some real cool stuffs.

However, "look what I can do in CSS3" is always fun to see, because it introduces techniques not necessarily just the technology.
That poll pours a cold bucket of water on “fantastic adoption” among all the respondents, but compare adoption of Kotlin and Java releases after Kotlin’s release. 1 in 6 respondents using language versions after 2016 are using Kotlin. I don’t think that’s too shabby.
I wish. Mine just removed the SMS option. I now have to install an App that wants full telephony access. And is obviously only available in the google play store, requiring me to accept google terms.

Is it safe? I don't know. Doesn't seem to be a widely used standard. Haven't found technical details. Only a mention of "cryptography" in the marketing material. So yeah, I don't really feel much safer.
Why do you say that? With the slope and adjustable suspension I'd think it'd be easier-- you just lower the truck and brush the snow down in a few swoops.
Hunh. Does this definitely use the e911 system for tracking? If so, there’s sort of a well-poisoning thing going on here. Most people would like 911 be able to figure out where they’re calling from in an emergency, but if this is going to be abused for surveillance purposes people are going to want to disable the phone-side portion of it - which prevents it from helping in an emergency. On that note, can this even be disabled on iOS/android? I didn’t see anything obvious in iOS settings (not that I’m itching to disable it - just curious if I even can!).

In any case, I would like my device to report whenever the network does something unusual, like request my location or put in a no-ring call. I wonder if you can make a pinephone or Android do that.
Apparently it uses some native code to get the necessary permissions on Windows: https://github.com/balena-io/etcher/blob/master/src/os/win32...
I think I would consider anything 100Tb and up to be big data. There is no big data that is "easily accessible"; that's why it's "big" because it requires extremely powerful hardware and advanced techniques to work on. Otherwise its just "data".

NOTE: there are people in the world who would laugh at my definition and say that big data starts at 1Pb.
Czeslaw Milosz. "Gift" [1] and "A Song on the End of the World" [2].

Philip Larkin. Almost everything he wrote.

Robert Frost.

Ted Hughes. The Birthday Letters. Esp. "You Hated Spain" [3]

T S Elliot. Four Quartets. Preludes.

[1] http://www.washingtonpost.com/wp-dyn/articles/A17245-2004Aug...

[2] http://www.poetryfoundation.org/poem/179559

[3] https://philosopherpoet.wordpress.com/2008/04/05/you-hated-s...
Zbigniew Herbert.

http://wchambliss.tumblr.com/post/107743541105/apollo-and-ma...

http://www.poemhunter.com/best-poems/zbigniew-herbert/why-th...

https://books.google.pl/books?id=nqeWAwAAQBAJ&printsec=front...
I'd like a source on the author's assertion that combat is taking place at longer ranges. A 20" barrel is harder to wield in an urban environment than a 16" barrel, that has always been my presumption on why the military has opted for the M4 over the M16.
Somehow reminds me of this interview with Philip Rosedale (https://www.youtube.com/watch?v=jg43s9yPsaI) where he basically suggests to share your idea (even in early stages) with people around you. Because you might end up with a lot of positive insights & ways to make your idea more solid.
Most of the remarks are deserved. The exception hierarchy is not consistent currently, but the language is still evolving a lot, including on a syntax level (julia 0.4 deprecates the short dict/array syntax, just to name one).

To be honest, I hope they continue to break stuff. There are still many areas where it feels that the syntax/language itself could be improved a lot (too many to list!). Some of the changes have a significant impact on the entire system (like multiple inheritance for abstract types). Most of the proposed discussion/changes I've seen improve the language in several ways, they make it more uniform, so I'm really looking forward to them!

The base lib is very minimal, and the quality of the contributed packages varies wildly. It's a new language... you might lament most of the same issues with Rust.

Being a long time lisper, for me Julia it's a lisp in disguise with an edge on performance. The compromises/choices done so far have a great sense of direction and balance. It's a good time to jump into the development before the language is set in stone and the warts cannot be changed anymore!
Do you seriously not mind having to zoom in on every single thread, and constantly scrolling left to right to read a comment?
>Imports shouldn't have side-effects (like registering functions with flask).

Imports don't have side-effects. Using Flask's route decorators has.

>You shouldn't use globals (like the flask app).

The Flask app is just as much a global as any other class instance in any OOP language. Whether you make it a module-level object or not is your choice.

>Objects (such as the flask app) should be immutable whenever possible.

They hardly are. This is a good rule which nobody follows, and I don't think you'd gain enough advantages through this.

>You need to make sure that you import every file with a request handler, and those imports often end up unused (only imported for their side-effects), which confuses linters and other static analysis tools.

The fact that your app has import side-effects is your fault, this pattern is not at all encouraged by Flask. You probably want to use blueprints.
That actually sounds about right. The logic of fleecing those who can more afford it may not have good moral foundation. Its tempting, but can you explain how the borough gives more benefits to the rich than the poor? Possibly just the opposite.
That specific mechanism? Probably not. But I wasn't here to say the effects were linear. I was just pointing out that complaining about sample size in a theoretical experiment where you can multiply the size in your head is a nonsensical objection.
Thanks, this was very helpful getting more of an idea of what he was talking about. More I read the more I realized I didn't actually understand what it was he meant. I should have known, it happens with my own writing all the time.
This is great. I had a college course that basically taught only the simplex algorithm - we did all all of the iterations by hand using tableaus and matrices.

We are using operations research optimization techniques at my side project, StaffJoy. The greatest innovation in usability of OR has been the JuMP project - there is now a fairly universal way to express optimization problems that is lower-level than Excel and higher-level than C.

http://juliaopt.org
I think people think of the Mi4 when they talk about an Apple rip-off.
A downed power line or gas leak only "could" do bad, but that's not a reason to dismiss them.
This would mean an extra function call for _every _ use of `?` (rather than a conditional jump that the branch predictor has been well-primed for), even in the non-error path. My Rust code for some projects use `?` pretty frequently, to the point that I’d be concerned about perf. Of course, the only way to be sure is to profile. Do you have any perf measurements with this technique in zig?
This is no natural monopoly, only a broken system.
Where I live in Brazil I have at least half a dozen broadband providers to choose from, big and small, and this is not a major city.
These are not programming shops, that’s the whole point. These are basically full time employees hired on payroll, who will care about your codebase as much as any other member of the team. Programming shops in my opinion never work, there’s always the mentality of just building crap and throwing it off the fence.
Very cool. I’ve been thinking of doing the same for a .net core app and maybe a couple other common frameworks. Might be PITA to keep up to date though.
As if this couldn't get crazier:

> Goldman Sachs & Co LLC. is serving as financial adviser to both the Internet Society and PIR.

https://www.bizjournals.com/washington/news/2019/11/15/resto...
why would you buy this over a 4runner or tacoma for a large farm property? (or the new defender)

i am curious and kind of skeptical that electric vehicles will ever get the longevity of combustion engine toyotas and such, given the nascent battery technology. am i wrong? will a Model S outlast a Subaru?
Im 25 years into my career. Excerpt for a few years during the dot com bust, I’ve been loving it. I’m looking for a new job right now, have 6 onsites scheduled and 10 other companies I want to talk to if I don’t get an offer I like. I’m also lucky enough to favor jobs close to where I live.

I feel very very lucky to have chosen programming as my career.
> AFAIK neither the "wholesale" price nor the actual price from registrars is currently price controlled by ICANN.

Important point: just before this rigged bid went through, ICANN conveniently decided to remove the price cap for .org registry prices.
I don't know Zuckerberg or anyone that has close contact with him at Facebook. He's strikes me as the kind of person who is obviously smart, but doesn't realize how smart he is because he's always been surrounded by smart people. A cocksure attitude can be a weakness unless you're trying to lead and reassure people that everything is under control.
If you really want to bet on the bad guys, invest in the companies behind BP and this oil spill. Such as Halliburton. Some people are speculating that BP will fold from this disaster due to the enormous projected cost of cleanup (10-30 times the cost of Valdez).
I'm assuming most compilers don't ship nasm/masm/whatever with them. How do compilers do actual "assembly to executable" step?
In a Ponzi Scheme, one concentrates on the stock, rather than the stack, I think... ;)
The Buzzer can be heard on disc 4, track 32 of the Conet Project. The entire collection is a free download.

Wilco's Poor Places uses a sample from track 4 of disc 1, which also gave the title to the album, Yankee Hotel Foxtrot.
That actually doesn't surprise me, given the work of Dan Ariely. He's done similar experiments (but not with sex; with people doing some silly task on the computer) and found that people would do better on the task if their reward was a gift, like chocolate, then if there was a comparative dollar amount. The difference disappeared if he referred to it as "$5 worth of chocolate" versus "$5."

We think about getting paid with money differently than we think about getting paid with gifts, for some reason.
I took 14 hours of calculus in my EE undergrad. Reading posts like this remind me that I really enjoy studying math outside of school. In school, I had to learn so much, so fast, that I couldn't appreciate the beauty, nor take time to ponder the wider implications of what I was learning.

Many times, I have thought about opening my Salas and Hille's Calculus book and just starting over from the beginning. Anyone ever done anything like this? Any opinions on a better starting book for someone in my shoes?
> The sort of artist who survives at the long tail is the sort who would be happy doing nothing else, who willingly sacrifices security and comfort for the chance to communicate something meaningful, hoping to catch the attention of those few in the world who seek what they also find meaningful. It’s a somewhat solitary existence, a bit like a lighthouse keeper throwing a beam out into the darkness, in faith that this action might help someone unseen.

Robert Rich

http://robertrich.com/1000-true-fans-an-answer/
But there the device itself has accelerometers, whereas here, at least if I uderstood it correctly, the camera has to capture the markers on the hand which is much more noisy.
The blog is meaningless, you could be a nobody. If I buy a block of cheese tomorrow, and you can see a band-aid in the package, half embedded in the cheese, half hanging out, the internet will go wild. Toss a photo on Reddit with a cheesy headline, and it'll hit the frontpage, then get reposted all over the internet. Within a couple of days the company would issue an official statement, and I'd have copious amounts of free cheese.

It would be a PR nightmare, and they'd be trying to track down the location, employee, and how their scanner for foreign material didn't pick it up. Meanwhile, without the internet, I'd call, never be able to reach anyone of importance, and they'd just apologize and mail me a 50% off coupon.

The internet gives the individual a lot of power, and they can reach millions overnight thanks to social networks. It also forces the company to handle damage control ASAP, since their reputation drops a notch with every passing minute.
wonder how much time was spent to generate these addresses...
Counter-experience to 2. Not eating at the computer:

I used to take a break to eat food - I'd watch TV or read a magazine while eating. However, this context switch would be costly, and when I got back to the computer, I'd be starting to get tired from digesting the food.

By coding while eating slowly, I was able to realise massive productivity gains. This only works if, like me, you don't mind eating luke warm food.

Then, instead, I'd take the break/nap after eating, and would not have my productivity affected by the energy spent digesting the food.
There's a more important constraint here: people change out their small consumer electronics MUCH faster. They buy new phones every year or two, arguably as fast as Apple puts them out. Same was largely true for iPods. They don't replace their TVs very often.
I'll take OFFERHN.com and LIVELINKDEVELOPER.com
The mistake analysts made about the iPhone was to assume the current industry structure would be sustained after Apple’s entry. I’d be wary of making the same assumption about the TV industry.

The big idea in this post: Sometimes you can't judge the viability of a truly disruptive actor by taking into account a current industry's structure, because a truly disruptive actor will change the structure!
How often do people buy set-top boxes in the $99-$250 range?
2^16 rounds of SHA-256 might not be "ultra slow" but it's certainly not as bad as you make it seem. If you read the analysis in the article, it would take many years to crack a random password with this hash function. It's unfair to say I "ignored" that requirement.
> Functions should be atomic, re-usable, repeatable, clearly defined, and well encapsulated.

And when they're very long, it's a warning flag indicating that they may NOT be atomic, re-usable, repeatable, clearly defined nor well encapsulated.

Also bear in mind that code is not carved in stone, but subject to constant change in every project that isn't deprecated, let alone in one under active development. This is why we judge its design not only by what qualities have been achieved up to this point - but also by whether the design serves to prevent them from deteriorating.

A long function that's reusable at the moment is at much greater risk of becoming unreusable than a concise one.

Readability is of great importance, too, since code is meant to be read by humans.

Note that the author himself kindly replied to my comment and admitted that he's going to refactor - https://news.ycombinator.com/item?id=8908307

Poor readability and messiness is acknowledged as an issue at the moment, since it is (to quote https://github.com/shurcooL/Conception-go/issues/3) "hurting readability of the project for other people". What else is poor code readability if not (to quote your words now) "difficulty of understanding the purpose, intent, actions, and side-effects"??

> I don't see lines of code as a direct factor in judging a function implementation, as long as those lines are spent moving the feature forward and not violating "DRY".

Well, in this case we have to agree to disagree I guess :)
Interesting. Perhaps I need to actually read Hasegawa's work, but this piece skips over a pretty important possibility (to me): that while the atomic bombs did not, on their own, convince the Japanese to surrender, they may have been major factors in the Soviets deciding to enter the war on the side of the Allies.
Why use a loaded word like 'force'? Developing on Windows was excellent. Microsoft provides great tools and support; it was incredibly productive. The only real negative is the licensing requirements.

As of 2011 (I couldn't find more recent data publicly available) Windows was far and away the most popular development environment. http://www.cnet.com/news/coders-choosing-mac-os-over-linux-e...

It's interesting to see the culture of development differ so much from place to place. When I worked in Australia, Windows was an incredibly common development environment, while here in Silicon Valley it's all Mac/Linux.
More like a non-maintainer than a maintainer, TBH. It would be far more honest for him to write "this code is being provided in the hope that others will find it helpful, but is otherwise totally unmaintained! You should not expect replies from me to any inquiry, feature suggestion, or possible contribution. Feel free to fork the project and take up maintenance yourself." I mean, it's effectively what he's doing, so why not just say it outright?
You'd think that, but no, there are often quirky issues. I've seen some apps port easier to cygwin on windows then to IntelMac.
I got my start at Xerox working in their photocopier "QA" department. I say "QA" because it was more a factory setup than quality assurance office. Anyway we had test cases in folders with instructions on the front to configure the copier. Just the usual things like two-page scan to offset or collated with staples and a cover sheet, etc.

Every now and then a "strange" case would be sent down of a certain job type that would cause the copier to break and hit "UM" or "unscheduled maintenance" exactly like this story.

Had some interesting things pop up such as very creative ways people managed to bypass the currency detection to prevent printing (totally crap) currency copies or causing the printer to fail correctly printing the Machine Identification Code, even one scan to email job that caused a crash in the SMTP client so it would endlessly loop sending the same scan to the same email address every 5 minutes (300 second timeout) until you rebooted the machine.

Fun times! This was actually how I got started with software development. I was interested in the copiers ESS (Electronic Sub System) which was a very basic Intel system running LynxOS essentially bolted to the back of the copier. I was chatting to some of the OS devs about RTOS and how it differed from a "normal" OS so learnt C with books they gave me and answered many of my questions.

From there I managed to get a job up in the "real" QA department testing the printer drivers for Windows 9x, NT4, 2000 and the "soon to be released" Windows XP (or Whistler as it was known during development). I learnt how to use the Windows Debugger and about printer driver development which almost made me want to leave humanity and live in a cave somewhere in South America (:

Luckily I got to move into the "nicer" world of C++/MFC and then .NET (anyone remember Managed Extensions for C++ aka C++/CLI?!). Like I said, Fun Times!
My own rule of thumb of whether or not to ignore SIGPIPE is simple:

* If you only deal with file descriptors provided to you (stdin, stdout, stderr) as well as some files that you open (including special files like FIFOs), do not ignore SIGPIPE.

* If you deal with sophisticated file descriptors (socket(2) and pipe(2) count as sophisticated), you'd better ignore SIGPIPE, but also make sure to check for EPIPE in every single write.

In my view, SIGPIPE is a kludge so that programs that are too lazy to check for errors from write(2) (and fwrite(3) and related friends) will not waste resources. But if you are dealing with sophisticated file descriptors, there is a lot more happening than just open/read/write and a lot more error cases you must handle, and at that point the incremental cost of handling EPIPE isn't a significant addition.
The entire healthcare system in US is a legalized fraud.

The number 1 reason why older Americans immigrate to Thailand, Vietnam and other low COL countries is to get access to services at a reasonable price AND to not have to deal with the fraudulent system that nickels and dimes them to bankruptcy.