skysight-inc/HackerNews huggingface dataset:
This is exactly what happened to me as a kid, but in my case it wasn't curse of the "gifted" but curse of the pushed. In my younger years growing up in Ukraine my parents and granparents pushed us hard to learn math, and so did my school. Endless repetition, hours of homework, Saturday classes, etc. I didn't have any sort of gift for math, this is just how children were taught there.

Moving to the US and going into 5th grade, the first several years were just repetition of things I'd already learned in Ukraine. They were so easy. My grandmother wasn't there anymore and to my parents it looked like I was doing _great_ so they also loosened up and didn't really push me further.

When we finally got to substantially new material I started to struggle. I got too used to everything being so easy and built on concepts I'd already had drilled into me. I failed a math test once - even my teacher was surprised. I ended up falling from perfect score As to Cs, then scraping back up to Bs by the end of high school.

Now I regret not taking math as seriously as I should have after leaving Ukraine, and am now taking time at home to learn on my own. Thankfully I'm used to self-learning in other areas, so I think it's going pretty OK.
Really, the article is filled with claim that are just wrong on their face.

> "Create a Need"
Ridiculous. Only in moron anti-drug adds do drug dealers "push" on users. While there's a bit of innovation like all businesses, most of drug dealing is fulfilling a need others won't fill.

> "Embrace Risk"
Another ridiculous claim. Drug dealing starts out extremely dangerous and almost all the dealers' strategies are about reducing risk - high security, disposable underlings, etc. A few dealers might "embrace risk" but once they've done all the "hard work" of reducing risk by being ordinary paranoid drug-dealers.

Moreover, it fails to mention important bullet points.

-- Establish a patron.
Most drug dealers operate by corrupt authorities on one level or another turning a blind eye. With so much money involved, the temptation is constant.

-- Eliminate the competition.
This is a well known and important tactic.

And with these two points added, we see dealers operate with the tactics of other monopolistic businesses - Hollywood or Microsoft in the 90s. Within that framework, they are businesses and make ordinary business decisions as well as decisions about who they need to kill to keep the racket going (and the degree of need to kill varies from area to area).
More likely the well capitalized one's with sound business plans aren't. About twenty years ago, I heard someone describe the difference in the drug trade then and in the 1970's as the difference between some hippies with a boat and the green shipping container every Tuesday.

Forty-seven pounds is not even hippies with a boat. They moved tonnes in fifty pound bails.
From where I stand, it looks like they're trading one of their big advantages for a massively reduced maintenance burden which will unquestionably allow them to compete better on every other front. It may or may not pan out, but I think we can all agree that some change of trajectory from the past few years is needed if Firefox hopes to stay relevant. You're free to think that Mozilla leadership is incompetent, but in this particular instance I think their stance is grounded in sound reasoning, as inconvenient as it is undoubtedly is for some power users.
At my organization, everyone's code gets reviewed before deploy, everyone (especially leads and managers) is learning and getting mentored, and everyone gets guidance (new projects and major changes have a design doc that goes out to the whole engineering org for comments).

Tech leads are expected to do more architecture but having direct reports and writing code are usually mutually exclusive.

So, everyone is junior?
Lydia Fairchild, woman with two sets of DNA
Plus one for this option, I've been teaching the same curriculum for nearly 4 years now, it keeps getting better and better in terms of the resources available as a teacher.
computers are addictive. Every noticed how top coders look like they've never seen daylight?
Recently i have started working with NightmareJs to scrape few sites. There also you have to mention the flow as in click here , grab this data n all. Wondering how is it different from that . Also can we use it to scrape data from a site and save to database?
Hi, if you don't mind sharing, what sort of development work do you do? Do you do much local development or is the heavy stuff offloaded to other computers? I like the form factor but I worry about lack of performance.
Check out the book Make It Stick. It's the recent research, summarized.
Ah! Thank you, I stand corrected. I didn't realize they actually have those now. Still hard to find, but at least they exist.
Exactly, that's why they should direct their (still huge) funds to create more awareness.
Why is it better? just the two links I'm going to give should be enough to give you pause :

http://www.cvedetails.com/product/3264/Mozilla-Firefox.html?...

http://www.cvedetails.com/product/15031/Google-Chrome.html?v...

During 2016, Firefox had 53 code execution CVE reports.

Chrome had 2.

Firefox only has around 8% of the browser marketshare. Chrome sits between 44% and 60% depending on the source.
So it's not a case of Firefox being more popular and attracting more people to target it for hacks. It's just worse software.

And then there's just user inconveniences like how Firefox becomes extremely slow if you open multiple heavy tabs. e10s has yet to fix it, currently, if you enable it, it only opens 2 processes, one for the UI, and one for the rendering engine. So the UI itself might not slow to a crawl but all your tabs will still feel slow if you open heavy stuff.

Firefox also has a slower rendering engine. My eyesight isn't great and I browse web pages with zoom active in between 120% and 150% depending on pages. That makes Firefox behave extremely slow on some pages. It's particularly unbearable, on, say, slashdot pages with lots of comments.

For the same reason smooth scrolling is the first thing Firefox users disable in Firefox. Smooth scrolling works fine on Chrome. FF has never managed to implement smooth scrolling in a way that doesn't slow things to a crawl and makes the scrolling look like stuttering or low framerate.

People often rely on Javascript benchmarks to say "Hey firefox is as fast as chrome!!!11!!" but JS is only one part of what makes a browser fast or slow. What about the parts that actually render the page to something your screen can display?

> Firefox 57 should be at least equivalent to Chromium.

Chrome would have had to stop all development years ago for that sentence to be true.
Which magazines have the most knowledgeable film critics? Introducing a metric
Interleaving has served me very well during my second year of Engineering. I hadn't attended that much and had a grade of 3/20. There were the final exams where the materials of the whole year was fair game.

I buckled down for a month with a friend at my sister's house which was empty. I eliminated the modules with diminishing returns that I had passed or where I was close (easier to go from 0/20 to 12/20 than it is to go from 8/20 to 20/20 for the same amount of points).

I was left with five modules I hadn't attended: Numerical Analysis (ANAI), Rational Mechanics(MECA), Strength of Materials(RDM), Vibrations-Waves-and-Propagation(VOP), and Atomic and Nuclear Physics(PAN).

I drew a pentagon and organized the modules. Starting at the top, going counter-clockwise: VOP, ANAI, PAN, MECA, RDM.

Each day, I'd do two modules:

Day1: VOP-ANAI

Day2: PAN-MECA

Day3: RDM-VOP

Day4: ANAI-PAN

Day5: MECA-RDM

Day6: Restart cycle.

Many benefits:

- You only do a module for half a day. Intensely. Then switch to another module and you sort of hustle your brain for a fresh start. It's not tired because you're doing something else now. "It's not like you've been studying all day" is the impression.

- Mixing modules gives new insights. Especially in second year, there's a bootstrapping phenomenon: to understand a module of Physics, you had to understand a module in Maths.

- You study a module hard. You don't see it the next day, but the day after. Not too soon to be sick of it and burn out, but not too far in the future not to remember any of it.

The problem with the methods most other students followed was that it violated their brains and common sense: they'd do one module exclusively for a week (all chapters, all exercises). Then go on to the next one and do the same. By the time the exam comes: they're sick of the modules, and they remember nothing for the most part because it's been 3 weeks since they've last done the first module they started with.

I, on the other hand, have seen any given module at most 3 days before.

This allowed me to study 13 hours per day during a month without burnout (reading the course material for the first time, going over the exercises and exams, etc). The key was keeping a schedule.

Up at 0500.

0500 - 0700: Study.

0700 - 0800: Breakfast.

0800 - 1200: Study.

1200 - 1300: Lunch and nap.

1300 - 1700: Study.

1700 - 1800: Afternoon snack and chill.

1800 - 2100: Study.

2100 - 2200: Dinner.

2200 lights out, going to sleep.
Even if you don't want to let (paid?) users access their previous revisions, it's an easy way to have basic undo functionality. You'll get "Help, I deleted my whole work history and don't want to enter it again!" support requests or disappointed users ("I can just hit Ctrl-Z in Word, why do I bother with this?"). Take care of stuff like this in the beginning and it will save you some headache later.

Images as blobs for webapps are generally a bad idea. You can't do a lot with them in databases (browse, analyse, join etc.). There's some overhead if you fetch them from the DB for each request, so they'll end up in some file-based cache anyway. Save that step and just put the path or filename in the DB. Or if you've got one image anyway, just ditch the column and have /img/users/<db_pk>.png.
This reads like the _exact_ opposite problem to what the parent described, to me.
I'm not sure why "pro business" always seems to mean pro-big corporate.

They already have huge advantages, having laws that even the field and allow smaller businesses seems much more pro-business to me.
Great Literature Is Surprisingly Arithmetic
This is reaching quite a bit. I'm the stereotype mentioned, but I only exhibit ~30% of the traits treated as universal. The author's self-conception, and conception of the groups they partake in, isn't enough to support anything after the first couple sentences.
The Secrets of Nested Coroutines
> you're already in the business of trusting the creator of the extension

Those were my thoughts exactly.

And tangentially related to your point, I am wondering why the addon developer, who I have explicitly trusted by intentionally installing their software, is not at least on the same or even higher level of trust as an unknown 3rd party web developer whose arbitrary Javascript application the browser automatically installs and runs when I visit a desired 1st party website?

There are no built-in protections that Firefox (or any browser) provides for running arbitrary 3rd party code that happened to be included by an unsuspected website that features 3rd party fingerprinting, tracking user actions, access to DOM, whether for "benign" or malicious purposes. In my mind that is just as, if not more, important for both security and privacy.

It looks like it is yet to be seen whether Mozilla's extended WebExtensions API will provide enough for existing add-ons that use current low-level access that to some level restrict 3rd party web applications.
I assume you mean "it's long but a commonly chosen long password"

Do you have evidence that is a commonly used password? I'm genuinely curious. The people geeky enough to know that meme might be slightly more likely to understand why it's a poor choice of password.
> Big trauma centers also means lots of resident docs, more or less supervised.

Yep, that was my thought as well. That sounds a lot like a resident who started heading down the wrong path before the attending pointed them back in the right direction. A 'teachable moment' of the sort that occurs hundreds of times a day at teaching hospitals across the continent.
> I'm not sure how to help kids not to go down this path

Now that I'm no longer in school I've found way more progress in learning things by learning through curiosity. My best guess for a teacher to successfully facilitate a curiosity-based approach would require using the soctratic method and more importantly encouraging students to use that technique and give them opportunities to come up with their own good questions they seek answers to. None of my teachers or professors ever did this and usually just overloaded everyone with an extreme amount of busy work. It would also require a professor to let go of their own ego in support of a better teaching method. I actually learned about the soctratic method from a good therapist. I've been using it to prepare for coding interviews and it's been working really well so far
There is an update to this: https://www.ubuntu.com/usn/usn-3199-2/
I agree with what you said even though it seems a bit outdated. I made a general statement looking at the evolution from 2005 until today. I switched employers many times, worked for small, medium and large companies. I got to interview a lot of candidates for the last 10 years collaborating with other colleagues to make hiring decisions. I'm aware there are exceptions out there, totally agree with you! Though, it changed since 2005. It seems that most of the tech companies are now following the google model by putting CS principles at the center of the technical screening. It doesn't matter if you applied for a Web, Mobile, Backend position, if you're a junior, senior, staff, etc. You'll have to go through it and it's usually a 30 minute question within a 45 min to 1h interview. So I call it the main technical evaluation for engineers. Versus a 2 minute question going over the technology you used and how you tackled some of your challenges. I personally dig into those questions but most of the interviewers don't want to hear about anything else rather than their own voices. They need to make a "valid" decision at the end of the day so they better get a solid justification. Like I said, it's easier for them to ask YES/NO type of questions rather than engaging in a design discussion for 30 minutes. Some do but most don't.

Right now the market is saturated by people applying everywhere at the same time. Some recruiters get handed multiple choice questions and get involved in the filtering right up front. If you use a referral these days you still have to go through the standard hiring process, again, there are exceptions. I got hired by an ex-collegue from another company a few years back, where he got promoted to manager. We worked together, coded together and were both engineers at our previous employer. He had an open req in his team and contacted me personally. I still had to go through the standard hiring process and crack a few algorithm questions with other engineers. He bumped up my rank though to the max when he hired me, which is where the referral boost came into place. Not during the hiring process, I was just a regular candidate for other engineers.

Anyway, back to your points, algorithm questions are the main topic of conversation during tech interviews in 2017, minus the exceptions. It all comes down to writing code on a whiteboard or in a notepad. When I say code I mean palindrome, dykstra, doubly linked list and all this crap. I say that because it's the hardest problem you can ask to a candidate with or without experience. People know you'd feel comfortable talking about app optimization, scaling an infrastructure, common problems in a multi threaded system, etc. They use it for architect positions where they know the person won't write a line of code. There's just a big misunderstanding because interviewers aren't trained to evaluate candidates. They'd rather go for the generalist route and hire the "smartest" algorithm guru over someone who has a deeper knowledge of the field.
They are doing quite well with submarines, which seems hard, and drones, which may be off-the-shelf.

https://www.google.co.nz/amp/www.mirror.co.uk/news/world-new...

https://www.google.co.nz/amp/www.ibtimes.com/mexico-drug-tra...
Google's Broken Promise: The End of “Don't Be Evil”
Seeing as how the line drawing function in X doesn't do any anti-aliasing, the result would likely be very consistent across different environments even for fat lines. The problems to some extent are differences of opinion about how to make lines look pretty.
This part in the original comment resonated with my experience: "When I was a kid, I could grasp concepts easily and I understood maths very quickly so I didn't really bother doing things like homework or actually studying."

This was exactly the case for me after moving from Ukraine. Concepts were easy because I'd already known them, or they were just starting to be built on top of stuff I'd already drilled and knew before. So I did not put any effort into homework or studying. When entirely new concepts came along they crept up on me and my bad habits and I failed hard.
Many developers self identifies as autistic, i am sure you will encounter them on your interviews if you keep looking. They will understand. Stay calm and confident being angry, frustrated or nervous is most common reason i see people failing interviews.
> I can't help but hope that it'll get hacked and that a thriving homebrew community will sprout up.

I'm hoping for the same! Set up a wiki to track everything we know about the device, and we also have a Discord chat set up to discuss the process and work on things together. By default the secret parts of the wiki and chat (where we'll be discussing the details of specific findings, exploitation, etc) are hidden; if you want to be involved directly, message me on the Discord and I'll get you set up.

Wiki: http://reswitched.tech/ Chat: https://discord.gg/hSMpnuG
And Firefox is less secure and slower because (drumroll, please...) the major architectural changes required to improve on those fronts is completely stymied by the desire to maintain backwards compatibility for addons. Firefox is at last forced to decide between being a bad but very extensible browser or a (hopefully) good but less extensible browser. IMO, the choice is pretty obvious.
The problem with this line of argumentation is atheism does not explain or give reasons for the most basic questions we have as human beings. Who am I? Why am I here? Where am I going?

Also, in the realm of morality, everything atheism purports to be true is completely optional. We can all agree that murder is wrong, but what's to stop an independent person from asking the logical question "who says?". Objectively, why is murder wrong? Societies are very delicate things, and it does not take much to spin them out of control. When chaos rises, people will trade their freedoms for order, and there will be guns in the street. Just look at the rise and fall of the Roman Empire.

Have a look at the series "How Should We Then Live?" by the late Dr. Francis Schaeffer. His insights into art, music, and architecture being a reflector and record of history is fascinating. https://www.youtube.com/watch?v=Z0Hr0RLHxnI&list=PLl7doUcMOr...

So people may very well give up their beliefs, for a time, but then the pendulum will swing back the other way hard, and societies will be grasping at some other explanation to answer those basic questions: who am I? why am I here? where am I going?

This is all very well trodden territory. People chase their tails their entire lives trying to live without God, and end up being right back where they started at the end of their lives, just like Bertrand Russell did.
There's a joke in here analogous to the "How do you get to Carnegie Hall?" classic.
Apple to Fight 'Right to Repair' Bill on March 9 in Lincoln Nebraska
Hey! Glad you brought this up. We've gotten quite a few requests from students enrolled in Udacity courses and have been helping get them set up & run their class projects on Floyd.

Here's our instructions for the Self Driving Car Engineer nanodegree program: https://github.com/floydhub/CarND-Term1-Starter-Kit. Happy to do the same for your class as well! How can I reach you? Feel free to to mail us directly: founders@floydhub.com.

We've also reached out to folks at Udacity to see if we can offer any official support for the courses.
Musk tweeted last night that there was a potential leak issue that might cause a scrub during the launch. They added an automatic check for the problem, and it appears that's what caused the scrub.

Since this is a launch to the ISS, the launch window was tiny- miss it by a second, you've missed it completely.

They'll fix the issue and probably try again tomorrow.

Edit: my mistake, Musk has tweeted that there was another probably-unrelated-maybe-issue, and they called it off just to be safe. Still, provided the minor issue doesn't turn out to be something more major, tune in tomorrow at 9:30 am EST.
There was a distinctly unsettling paper[1] a couple of years ago which found evidence that ants could recognize themselves in a mirror, which is really not a result you'd expect from something (ab)used as a "sentience test". I've seen very little followup on this; does anyone know how it's been received?

[1] http://www.journalofscience.net/File_Folder/521-532(jos).pdf
1. DNA is transcribed into RNA. Structurally, RNA is very similar to DNA. RNA has some different bases and its key characteristic is that it has an additional 2' OH group, making it less stable (more reactive) than DNA. Multiple copies of an RNA transcript can be created from a single transcription frame--eg gene(s), making it easier to produce more protein in parallel.

2. RNA is translated into protein. Amino acids are very different from the DNA and RNA base pairs, and one of the consequences is that the structures are subject to folding and adopting secondary and tertiary conformations.

Another poster said to think of protein as the "machine". While this is largely true, the biochemical reality is more subtle. Both DNA and RNA also assume mechanical behaviors--that's a bit beyond this discussion though.

While we can map polypeptides (protein) back to RNA and DNA, we lose some of the DNA: promoter regions that signal to transcription factors, spliced out code, non-coding regions (introns), etc. All of these are extremely important to biology.

DNA has a relatively short half life (521 years), which is why we haven't found any from dinosaurs.

These finds are great for comparative studies on protein evolution, but will be grossly insufficient to ever clone dinosaurs. We're missing billions of base pairs of data, and I'm not sure where we'd ever find them. I think inventing a time machine would be more likely than getting the data from fossils, unfortunately.
We use Slack's "/remind" functionality for recurring reminders. For us having your proposed software as a slack bot would be awesome
The number of people killed by medical errors thing is a little controversial. People who are about to die anyway get a lot of medical interventions (which is more opportunity for errors, big small). If a patient accidentally gets an extra dose of their antacid 48 hours before they die, is it really likely that error led to their death? Because it would be counted in that 250k/yr number...
Not quite, I think the title should contain the word "machine".
I switched to Pale Moon and I've been happy with it.