skysight-inc/HackerNews huggingface dataset:
I've had the same experience. I had coffee all through my college years. Had a few scattered experiences with anxiety attacks, but I always attributed them to test stress.

After I started working and the responsibility and the need for creativity grew, I found the anxious episodes start to grow and become quite debilitating. I started to experiment with different parts of my lifestyle: sleep, caffeine, exercise, relaxation.

In the end I narrowed it down to caffeine. The anxiety went away. I felt more awake throughout the day and sleep cycles easier to maintain.

I don't want to claim too much on creativity, but I do feel the ability to relax and let my mind wander has eased the creative process. Instead of the laser focus I'd get when on caffeine my mind could calmly move to less pressing tasks and make those subliminal connections I would have missed if I was too set on an issue.

That said I do miss the taste of coffee. I'll occasionally sip a decaf or latte and feel some of those symptoms return slightly, but knowing its cause has helped a lot.
Will it work with <ol> with the `start` attribute?
By providing 101k of value?

Do people know enough about what you do and how you do it to give this answer at interview stage?
Coming soon: OTA updates for Boeing aircraft. What could possibly go wrong?
If I was interviewing now here are things I'd be on the lookout for:

Team dynamics:
How do they interview (individually or as a team), do they undermine each other during the process, do they not play well together, is there obvious clique behavior, is it a fraternity, have they all worked together for awhile, is it a new team, what's the team lead like, has the team lead/mgr done the role before etc. Does the lead/mgr seem to respect his team, does he defer to them during the process at times or always take the lead?

Software:
Are they chasing the latest trends, behind the times, or a mix of using new tech but keeping things stable. Look for their thought processes, questions they ask are generally tailored more then they even realize to their environment. Are they more worried about getting a smart person that can figure things out or trying to find the guy who has esoteric answers to questions.

Company:
Does anyone outside the tech team interview you. For SMB's and/or startups, do they discuss the financial condition of the company? Do they avoid answering any questions you ask about the company from a financial aspect or team aspect etc. Is their culture open or closed? What are the working conditions like. When you tour is everyone heads down and no one is talking etc? Do you see any team members having some fun, laughing etc.

These are just ways I like to start evaluating companies. I don't really interview anymore as I run my own firm, but when we are engaging from a consulting perspective these are similar things that I do to gauge who the company is and who the team is we would have to work with. It tells me if we will have trouble with the team, if we should even take the job etc.

No matter what, good luck.
"You never told me you'd delete my files!"
This is just standard MRA garbage.
I am not familiar with his posts, but it is very often these days that uneducated liberal arts majors who attempt passing as serious journalists, have no clue what they are writing about (usually rephrasing blogger and forum posts as their own), trying their best to make as much sensational article titles at best, in an attempt to lure casual readers in. But instead of enriching the casual readers with information, like journalism used to, now they are subjected to substance-free jibber jabber.
Hm? How so? I think we have plenty of control with the history API, no?
That's what I was really trying to get across—the difference between "imperfect" in other engineering, and "imperfect" in software. In other engineering, "imperfect" means "will randomly fail 0.00000001% of the time."

In software, though, "imperfect" means "will work perfectly, 100% of the time, even after a quadrillion tests, within a well-specified subset of all possible inputs; will fail in arbitrary unknown ways outside of that subset."

It's a difference to being "within tolerance"—even within tolerance of a physical system, stresses are still going on. Physical systems have a lifetime, and repair procedures, for a reason.

But in software, you don't have to worry about "stress within tolerance." In fact, even if someone else builds an "imperfect" software system that accepts inputs with undefined results, you can just wrap it with an input validator, and suddenly it's a well-defined-100%-of-the-time system!

(Of course, in implementation, software has to run on hardware, which is the other kind of imperfect system. But, surprisingly, you can write software to compensate even for that, with failover and quorum-agreement &c.)
>Google funded the crap out of it invested in datacenters and putting Youtube "pods" in bunches of Colocation facilities around the world etc for a property that doesn't make any money.

When Google says YouTube doesn't make any money, they mean net of funding the crap out of it.
According to 'cloc' this file contains 8866 lines of code, 10281 lines of comments and 1844 blank lines.
There's really no reason to feel stupid just because you don't know what the terminology means, if that is indeed the problem. Would you feel stupid if you were to walk into a Scientology meeting and you didn't know what SP, Xenu, or fair game meant? I wouldn't. It's just a bunch of jargon that I would have to pick up if I were really interested in knowing the underlying concepts being discussed (and I'm not, which makes me feel even less stupid for not wanting to learn this).

And even if you know what all the words mean, it can take some time and effort to put them together, even for practitioners.
I don't have enough information to give much advice.

- Is the programmer Jr or Sr level?
- Are they new to the language?
- Are they new to the architecture/style?

Obviously spaghetti is not acceptable. But if they are a beginner, then you have an opportunity to be generous in your review and help teach them (as you should for beginners). If they are senior level and they should know the language then it may be a sign that it was not a good hire.
I've been on the receiving end of several code reviews that could be summarized as "You didn't write this exactly the same way as if I had written it." This was at places that did not have uniform written standards uniformly applied. It was just the boss swinging his dick.
The obtuse answers on that thread are also the typical types of answers I see from the Android community as well. It's like the people heavily involved in Android are unaware that there is a whole other world of nicer and more efficient SDKs out there.
As if any of the content on Youtube at that time was licensed? They owe all of their early success to "bulk copyright infringement."
True, but then you have the server duplicating logic from the client. This is very similar to the custom endpoint solution, which breaks down when you have multiple clients needing different data. You end up either under or over fetching.
Isn't there a company doing this called Pied Piper...
Huh, why not? Because paths must have the real numbers as their domain?
This cleared up that question for me. Noether showed that every physical symmetry implies a conservation law and vice versa, the symmetry of time flow and the conservation of energy are one such pair. Due to the fact that time is not flowing uniformly (Relativity) energy is not conserved.
I took one semester of French in college after 4 years of Spanish in high school.

The most intriguing parts for me were around numbers and counting. For example, the number 80 is "quatre-vingts", which literally means 4 x 20.

I thought maybe this gave French youth an edge with arithmetic, and this slight edge might translate to strong mathematics foundations later in life. I have heard there is a strong emphasis on mathematics in their school curriculums, so maybe there is some correlation there.
This is why pair programming is so great, especially when the duo is somebody seasoned and a new hire. Pairing is continuous code review so you address problems like 400LOC methods before they start. It also reduces the newbie's sensitivity/fear/hostility to feedback when the code is your shared work product. "How could we make this better?" feels a million times better than "You should have done it this other better way".

I'd definitely give it a try, at least for onboarding new people. There's no better way to transmit knowledge about the code and expectations for how to work with it.
LinkedIn Founder's Take on Employee Retention
You gotta find a way to figure out if this person is CAPABLE of delivering better code. That's gonna hinge on their talent, and their willingness to learn. At some point, some folks make it clear, one way or another, that they can't/won't get much better, at which point you unload them.

Until then, you need to be friendly and patient, for a number of reasons. Don't betray shock, and don't betray disbelief in their incompetence, but do firmly require them to sit through a lengthy code refactoring with you or someone you trust, so that they can see what is required AND how far their code is from what is required. They need to feel your pain, but not by you being testy or edgy or frustrated.

Or, as the good writers say: show them, don't tell them.
You can be honest with them without bringing up things that aren't relevant. There's a reason you don't like the PR: it's too big, it has a lot of conditional logic, etc etc. There's a bit of personal dislike with it, but that dislike is also founded. There's increased complexity, which makes it harder for others to understand, and most likely harder to test. It comes out as a personal feeling of "ughhh" when you look at the code, but there's an objective component to it that, if you take the time to, you should be able to get across.

Everyone is different, and I certainly don't know all of the right words to say, so I'll simply say what I think should be mentioned no matter what: point out the problems with the code, not the person. "What if we broke this apart in two right here? It looks like it'll be hard to test this in isolation otherwise." "What are your thoughts on some sort of pattern matching / switch statement here instead of using if/else blocks? Any downsides? Might end up being a little cleaner."

You're trying to make the case the code can be better, but not that it's horribly bad. I mean, if it works, but it's ugly, you have a base. They got the job done. Now it's time for you to help them make it better.
This is pretty much the same thing that Ember ListView does. http://emberjs.com/list-view/
wow, that article is amazingly pointless. I don't have much in the way of expectations for Engadget but I can't even imagine what they were going for there.
An internet soapbox for anyone with a camera is hardly comparable to the concentration of written knowledge, skill and talent that is any library ever.
Of course, every bee wants credit for their own find. So there needs to be a countervailing costly mechanism to prevent bees from simply over-promoting any pollen source they know.

Two problems with this. Most importantly, if bees have the same genetic interests (it's a bit complicated but see The Selfish Gene for Dawkin's explanation of why bees are genetically programmed not to have different interests than their hives) then there is no reason for a bee to want credit. Second, has any reward for the scouts ever been observed?
It's not laggy at all using Mac OSX Chrome with a trackpad.
Challenge HN: Make it travel in a perfect circle. Comment with your strats.
I got the same response when I informed /r/science that "No, no one in the OPERA Experiment actually believes that neutrinos are actually going faster than light and breaking special relativity, they're asking for input on what went wrong with their observations"

I got a tirade of responses just like yours informing me that I'm a biggot, childish, close minded, backwards thinking, co-dependent on authority, cretin who will be the responsible for the downfall of humanity. ect. ect. ect.

I believe I got down to -45 karma on that post, my lowest score ever, and I wasn't being aggressive or hauty or anything. I was just saying "they're just looking for explanations on their observations, there's no way it's actually happening."

I never got an apology for that, strangely enough.
"linear combination of pre-existing socioeconomic resources and inflated self-image"

What do you mean here by linear combination? If you wrote the same thing and said nonlinear combination would we have come away with a different interpretation? Is this just injecting random math terms to raise the status and credibility of the speaker?

It's a problem I see in a certain non-MBA culture (and am guilty of myself all the time too).

Or maybe I'm just missing something about what you meant.
Wow! Good idea!
I totally forgot about OL's start attribute. Give me a moment, I'll impelement this too.
I've worked on this problem before (unfortunately in closed source corporate america).

You can just stop the scroll event from propagating in the case that there's more rows to scroll through.
Best New Tools for Founders, Hackers and Hustlers
We have started making a list each Saturday of the best new tools for startups and founders from the past week. It was created out of the idea that we were only featuring consumer goods based startups and not really any that would help out a fellow founder.

We also are looking to expand it into more featured categories like tools for marketers, programmers, etc. in the next few weeks.

Check it out here: http://www.content-base.co/upstarted/?p=2521
Automate deeplinking scheme url testing in android with zoster
"Hard mode" is raising outside money. Easier (and often better!) mode, is to delay raising outside money.

Your current employer is usually a far better investor to (unknowingly) fund your projects anyway.
One of the best and most concise plugin pages I've seen. It's very considerate having a "how does it work" as one of the first things explained on the page.

Kudos for that!
Yeah seems that this problem appears only at OSX 10. I don't have a Mac but I'll fix it once I get one.
Even after my interview, people couldn't really give me a straight answer. The best anyone could say (which is how I answered too) is that it depends, on a case-by-case basis. Talk to people off-pole. Make sure everybody is safe / aware of what's going on.
Your choice of words is telling: "mercenary" and "shark" are overwhelmingly negative. By characterising people who disagree with your assessment of equity that way, you risk being perceived as a confidence man. Con men sell hope to the greedy at a steep markup; they are perfectly willing to use guilt if that's what it takes to reel in the mark. Anything to get someone to buy into their schemes for their own profit; in this case, by accepting worthless scrip in lieu of proper compensation. If you don't want to be perceived as unscrupulous, you should reconsider how you characterise people with different values.

I didn't get burned in 2001. I watched a bunch of people who thought they were rich suddenly realise that not only were they not rich, they were also out of a job with no prospects, through no fault of their own. I wasn't personally harmed; I rather enjoyed paying 40% less rent and spending half as much time commuting. Nevertheless, it was a magnificent learning opportunity for a young engineer, just as the bursting of this bubble will be for others. For anyone who prefers to learn the easy way, the takeaways were:

1. The market price of your equity is determined by almost every conceivable factor except the merits of your own work.

2. So few companies succeed in a way that makes your equity of life-altering market value that you should approximate the probability as zero.

3. You will not live long enough to accumulate enough wisdom to beat the market; that is, you are not better than average at identifying early-stage companies that are much more likely than average to be successful as in (2).

4. More generally, humans don't live long enough for buying variance to be a good strategy unless you are desperately poor. Otherwise, sell variance any time you can do so ev-neutrally. If you simply must buy variance, pay as little ev as possible for it. Flips and roulette are good; the lottery and buying stock on margin are bad.

"Life-changing upside" changes very few lives, even fewer deservedly so. If we lived 100,000 years, it might make sense to take a few thousand gambles on early-stage startups; the variance would mostly work itself out, and after a while you might even be able to tell who's likely to succeed so that your choice of employers would be +ev. In one 40-year career, forget it. The path to true wealth consists first of an inexpensive lifestyle and second of salary maximisation. Higher ev, lower variance.

(first paragraph edited for tone)
Yes. Reformulate the systems transfer function into a state space representation, and then solve the algebraic ricatti equation to find an optimal gain matrix. This is know and the LQR problem.

http://en.m.wikipedia.org/wiki/Linear-quadratic_regulator

Switching the output from 100% to -100% is another viable approach, known as bang-bang control, but it is not necessarily optimal
But then what defines a unemployed have been games to hell and back...
I like to follow 3 simple rules.

- Don't phrase your feedback in such a way that you wouldn't feel comfortable saying to this person's face, or have read out in court. In other words, be professional.

- Mark each piece of feedback as "Blocker/Not-a-Blocker", to cover issues which (in your opinion), need addressed before using or are simply opinion points which are at the author's discretion on whether to use.

- If you know of a better way to write it, include a snippet or some pseudocode if possible. If it's more complex than a snippet and it's a work situation, then write your point succinctly and then approach in person and offer your assistance in pairing if they would like.
I don't know, actually. That seems more invasive that taking wisdom teeth out. I can ask around if you want.
If you really want to expand your linguistic horizons, study sign language. Sign language is fundamentally different than spoken or written languages. It doesn't just substitute gestures for phonemes or written tokens. Its grammar (and it does have one) is three-dimensional. It also opens you up to the fascinating world of deaf culture, since teaching sign is one of the most popular ways for deaf people to earn extra money.
On the contrary, the cost of expressing an opinion on social media can be very high. Sometimes rightly of course, but sometimes not.
Look very great and seems pretty efficient :o
As I've said in previous discussions about #talkpay, it only hurts your negotiating power as an employee. Even if you are a better at negotiating than your co-worker, they aren't going to care, which will hurt morale.

All Tax records and salaries are public information in Sweden and Denmark and it doesn't mean you, as an individual will get paid more. It means you get paid at exactly your market rate, which tends to be less. It's great for the person that doesn't want to work on their negotiating skills, but bad for the person that does. Some people are also worth more as an employee (IE: better skillset, more experience, etc), but the person making less will most likely not see this.

Privacy is one of the only things as an individual that gives you power over a big company during negotiations. Why in the world would you ever just give this up?

I never talk about my pay. I run a business now and won't divulge this information to anyone. Many people are jealous by by nature and when they know for sure you are doing better than them, will bad mouth you, spread rumors, and do anything in their power to hurt you. I've seen it in my personal life and I see it every day on Twitter.
Keep doing what you are doing in refactoring and fixing it. Spend hours on it. Tell the person you spent hours on it. Tell them you expect them it will take them longer, but these are the standards you expect of yourself.

Ask your boss / their boss if they also expect those standards or if you are wasting your time or if this was a good use of your time to spend hours/minutes rewriting this employees work. Ask if that employee should be spending 2x/3x/4x the amount of time on their code to get to that level.

edit: What I mean is, it doesn't sound scathing if it's helpful. Scathing does not have to be in the vocab. Just be helpful to everyone, coworkers and superiors. Everyone wants to do the right thing.
Writes should be durable by whatever means the platform deems durable. Durable should be the default. It should take work to have non-durable io.
For a complete Python PID loop implementation and (console) demo:

git clone https://github.com/pjkundert/ownercredit.git
PYTHONPATH=$PWD python ./ownercredit/pid.py
For some definition of "optimal". I expect you can reach the "5% deviation from target" region much faster if you allow a bit of overshoot.
One wonder if telecom should be handled like roads. Have one set of cables/fibers put in place by a government entity and then rent it out to all comers that want to deliver a service over it.
Ok, but one thing is to say that there are bad scientists in the field of psychology, and another one is to say psychology is not a science at all. It's not (and it can't be) an "exact" science, but it's science all the same.
Code that I've seen like that is usually an organic method that grew to meet additional requirements and edge cases.

This seems like a great teaching moment on how to break up 400 LOC into smaller, more understandable modules. I would encourage you to block out some time with the dev to pair program and refactor it. If you refactor it yourself and then show them, they'll never learn how to do a better job in the future.
Eh, as the article points out it's pretty unlikely you encountered that last layer of copy protection from a ROM.
Not to mention he missed by a mile on the valuation estimate.

YouTube isn't worth anywhere near $100b-$150b.

Netflix has a better business model, a track-record of profitability, more revenue and nearly 60 million paying subscribers. It's worth $33 billion by comparison (and is itself carrying a hyper valuation at 100-200 times earnings typically). Netflix is the general ceiling on YouTube's valuation.
Sure. I don't really know much about CSP.
There's a way to make an argument without calling your counterparty a "con man". I'm more on your side than the parent's side (though the idea of valuing equity at zero is illogical). I think your comment would be stronger without its first paragraph.
Stupid question to those who work in the aviation industry:

This seems like a candidate for an automated script that reboots the server every n days or hours. Would such script be considered a potential risk? If so, why?
Amons.co – Where AirBnb Meets Angie's List
Will you be able to pay for your server costs with those tiny ads? I guess if you need to run 12 servers, you're probably seeing a huge number of ad impressions.

Either way, I think it would be cool to let people donate something like $2 to remove ads and make your cell move a bit faster.

Also, please get in touch if you want some help porting this to iOS.
Pair programming pretty much eliminates this issue
I think refactor and show them could help them learn.

No need to be that pessimistic is all I mean.

Pairing would be better.

If the employee does not have time to pair, I would still do the refactor and ask the boss how much time they will be given to review the changes (I would assume/expect they would be given many hours to do that, if it took many hours to refactor) ....
There is a claim out there that the US gov have been pushing for homeownership because "homeowners don't riot".

Or to put it in other words, when someone is saddled with a property and a family they are more likely to go "yes masta, right away masta".