HNHacker News
TopNewBestAskShowJobs

nknight

4,320 karma · joined June 27, 2011

I do server-side development and operations. When lacking other experienced developers, I'll step in on embedded Linux stuff, to.

Recruiters, HR, hiring managers, etc.: I've been trying to make a success out of something for several years. I intend to keep at it until it works, explodes, or I have a complete nervous breakdown. If you're trying to fill a position before 2012, I'm probably not your guy.

submissionscomments
nknight··on Miso pays disputed $10k referral bonus to ex-engineer, apologizes
Many things end up in court that are not ambiguous, which is why summary judgement[1] exists.

Although it is usually impossible to predict the outcome of a vaguely-defined case (I hit and killed you with my car, am I liable?), a case where all relevant facts are known (I hit and killed you with my car while you were legally crossing at a crosswalk, my light was red, and I was speeding) is utterly unambiguous, but will still end up in court if one side refuses to settle, no matter why they refuse.

[1] http://en.wikipedia.org/wiki/Summary_judgement

nknight··on Miso pays disputed $10k referral bonus to ex-engineer, apologizes
The "after you gave notice" part in particular is quite stupid. It will simply encourage people to wait longer to give notice, or not give notice at all.

Were I leaving a company amicably and had no other constraint on my time (say I'm planning to start my own company, or even just take a couple years off), I'd give several weeks, if not a few months' notice, to maximize flexibility for everyone. If I knew it was going to screw me out of $10,000, however, I definitely would not extend that courtesy.

nknight··on Miso pays disputed $10k referral bonus to ex-engineer, apologizes
It's not ambiguous, it's fact-specific, and a court in such a situation would look to questions of fairness and reasonableness under the circumstances. Absent an extended delay that caused meaningful harm to the company, the employee would almost certainly get his reimbursement.
nknight··on Miso pays disputed $10k referral bonus to ex-engineer, apologizes
That's exactly what he's trying to do. This isn't an apology or an admission of any wrongdoing, it's an obvious attempt to reshape perception of their original actions by pretending their motives were different than they really were. Motives that were utterly self-evident from their very first reply:

> After you lost our data and caused our entire company to scramble for 3 days, I am hesitant.

Everything since then has been trying to unring the bell.

nknight··on I'm a former Miso engineer and the founders screwed me out of 10k
You have announced to the world, entirely of your own accord, that you will flout the law and steal money from your employees. This is your doing, not mine. Is it also your habit to blame others for your own shortcomings?
nknight··on Why One of Silicon Valley’s Savviest Investors Has Shut His Wallet
Touch a piece of sandpaper, it "feels" rough. But there's no emotion.

If you must, substitute "believes" for "feels" in this scenario and you'll probably understand better.

nknight··on I'm a former Miso engineer and the founders screwed me out of 10k
Your loyalty to your employees should include respect for contracts and the law. This man satisfied the conditions for payment of the bonus before he left the company, he is entitled to the money. That you would not give it to him makes you little better than a thief.

Fortunately, we all now know that OpenDNS and anything else David Ulevitch is involved with in the future is a company to avoid.

nknight··on I'm a former Miso engineer and the founders screwed me out of 10k
Insulting him and telling him he shouldn't ask for money he is clearly owed because of a mistake we've all made. Actually, that second part is an insult, too. So, really, just being incredibly insulting.

That you wouldn't ask for the money is irrelevant. We're not required by any law, moral, or ethic to go through life as a doormat. At this point, money has been stolen from him, just as if they'd taken it from his bank account. He is owed that money, and entitled to ask for it without you attacking him for it.

nknight··on I'm a former Miso engineer and the founders screwed me out of 10k
> It's a rookie mistake.

It's a mistake I've seen people with 20 years of experience make. If you haven't done it already, you will eventually. When that day comes, I hope, but don't expect, you'll remember to apologize to this guy.

> For a community that seems to pride itself on being the best of the bunch at this stuff

How you get from "Hacker News" to "infallible operations engineers" is beyond me. Operations is a rare skill to begin with, and even those who are best at it will make these mistakes.

nknight··on Redditor: Am I a scumbag for automating my manual work and making more money?
The mindset you speak of, using words like "client" and "contact the decision maker", is associated with people who are used to having a great deal more power and influence than somebody hired to be a data entry grunt.

The mindset may be useful for climbing out of the data entry grunt "class", but probably not for "fixing" his existing employer's practices. Someone on that level in a company of any substantial size is going to be ignored, disciplined, or outright fired for rocking the boat.

nknight··on Oracle/Google jury finds Google infringed SSO but hangs on fair use
Accounting principles, tax law, and theft laws are far easier for the layman to understand than programming. They deal with accounting and taxes in their everyday lives, and they understand it's wrong to steal. The principles are taught to every child in our society and they put them to practical use throughout their lives.

None of this applies to programming, which bears only the most tenuous of relationships to anything most people will learn or use in their lives.

nknight··on Oracle/Google jury finds Google infringed SSO but hangs on fair use
They're meant to maintain control by the people over the judiciary, it has nothing to do with "common sense". In this case particularly, the problem is lack of uncommon sense. You cannot expect non-engineers to understand that rangeCheck is utterly uncreative, because they don't understand rangeCheck to begin with, nor its underpinnings. They can't even apply a generic sense of right or wrong to it.

This sort of trial should be conducted in the modern style of civil law countries, but that would require a constitutional amendment.

nknight··on Jury rules Google violated copyright law, Google moves for mistrial
You're mostly right, kind of. I'm going to try and explain this, but it's not particularly easy. The confusion comes from both the nature of the "fair use" defense and the collision of legal vocabulary and common language.

Fair use is an affirmative defense, which means that even if a violation occurred in a strict sense, that violation is excusable. It's not an "I didn't do it" argument, it's an "I shouldn't be punished because..." argument. Self-defense is a textbook example of an affirmative defense -- strictly speaking, I would violate the law by intentionally injuring or killing someone, but I can argue that I was defending myself.

The question of an affirmative defense is not even relevant until there is a prima facie case showing violation, and often the fact-finder (jury or, in a bench trial, the judge) will actually find all the facts necessary for a judgement that infringement occurred before addressing the question of fair use, partly because the answers to many questions of fact for infringement are relevant to whether "fair use" holds.

In the end, you do end up with a judgement that no infringement occurred, but along the way, you often end up with findings of fact that do spell out a "violation".

nknight··on The frequent fliers who flew too much
I am aware of all the information behind your assertions, so no, I am not "badly misinformed", thanks, I simply reach very different conclusions than you do.
nknight··on The frequent fliers who flew too much
Look very closely at what I actually said. The meme I speak of is not "insolvency" generally, but insolvency due to a specific cause.

> disclosure: non-American

Which may explain why you're not familiar with the particulars of the meme I refer to, but does not excuse randomly shuffling my words.

> with no knowledge of your welfare scheme

Social Security is not a "welfare scheme", it is a government-administered pension program. Everyone who has paid into the system, from the very poor to Bill Gates and Warren Buffet, is entitled to benefits at retirement in proportion to their contributions.

nknight··on The frequent fliers who flew too much
> Not being able to pay your outgoings is the definition of insolvency, friend.

Didn't say it wasn't. Try not randomly reshuffling the words. You'll get a much clearer picture of what I actually said.

nknight··on The frequent fliers who flew too much
The Republican-invented meme of social security insolvency because it didn't account for life expectancy increases is tired and worn out. The reality is that the architects of it were nowhere near that stupid, and they accounted for evolving life expectancies with a fairly high degree of accuracy. Had they not, the fund would have been bankrupt long ago.

Even now, the system faces not a crisis, but a need for adjustments. In the 2030s, incoming taxes are expected to be at approximately 75% of payouts. If no changes are made, once the trust fund is exhausted, people will continue receiving at least 75% of their entitlement indefinitely.

nknight··on How did Ruby and Python prevent fragmentation while ML and Lisp did not?
Mailman, the original BitTorrent client, Gentoo's Portage/emerge tools, yum, Eve Online, and a large swathe of 90s-era Red Hat Linux system configuration tools have all been written in Python, all predating Django and your "Ruby backlash" timescale by at least 2-3 years. And not one of them is web-related.

Most of the code that gets written in Python has nothing to do with web development. Web development is just high-profile.

nknight··on Linux's awesome and underused traffic control facilities
Uh, yeah, no, that's not my idea of a good user interface. If anything, you've just convinced me never to touch pf.
nknight··on Linux's awesome and underused traffic control facilities
Even were it adequately explained, it would still be underused, being a pretty crappy interface. I find it virtually the antithesis of iptables, whose syntax and meaning is fairly intuitive and easy both to remember, and derive from a few example rules.
nknight··on AT&T CEO voices regret over iPhone unlimited data model
You're not understanding what tnash said at all. Each of the utilities you list is a "dumb pipe". The utility company doesn't dictate what you do with the utility, and they don't charge you a different price for running a lightbulb vs. a washing machine. It's all about how much, not what's done with it.

The telcos want to be exactly the opposite. They want to control what you do, how you do it, and how much you pay for doing it, not based on the bandwidth used, but the nature of the use. This is the antithesis of a dumb pipe.

nknight··on Priceonomics Raises $1.5 MM, Users Unfazed
I'm still able to reliably bypass the autocompletion just hitting enter, any reasonably fast typist would. It's not even just the 25ms, it's the actual time to execute the autocompletion code.

Hitting the search button with the mouse also bypasses it entirely, no matter how long you wait, as does hitting tab then space or enter to activate the search button.

nknight··on Priceonomics Raises $1.5 MM, Users Unfazed
Just hit enter fast enough:

http://dl.dropbox.com/u/14571816/pricenomics%20car.mov

nknight··on Priceonomics Raises $1.5 MM, Users Unfazed
... What is that "car" in the picture?
nknight··on XOR Linked List
C++ is a lot stricter about a lot of things, and C++11 added some explicit GC-related language, but I have little desire to parse that particular 10MB document. Bjarne covers it in his FAQ, at least: http://www2.research.att.com/~bs/C++0xFAQ.html#gc-abi
nknight··on XOR Linked List
Actually, the behavior is a combination of undefined and implementation defined. To the extent that it's implementation defined, it may still result in nasal demons, but they have to be documented nasal demons.

Point is, it's strictly non-portable according to the standard, but when done carefully is unlikely to break on a general-purpose architecture.

This is from C99, I don't have a copy of C11:

6.3.2.3 Pointers

[...]

5) An integer may be converted to any pointer type. Except as previously specified, the result is implementation-defined, might not be correctly aligned, might not point to an entity of the referenced type, and might be a trap representation.[56])

6) Any pointer type may be converted to an integer type. Except as previously specified, the result is implementation-defined. If the result cannot be represented in the integer type, the behavior is undefined. The result need not be in the range of values of any integer type.

[...]

And footnote [56]: The mapping functions for converting a pointer to an integer or an integer to a pointer are intended to be consistent with the addressing structure of the execution environment.

nknight··on The guy who made it so difficult to open your bag of potato chips
I really don't understand the objections. It's quite easy and obvious to me, has been since I was a little kid and was first confronted with sealed bags and packets like that, and I have exceedingly poor coordination.
nknight··on XOR Linked List
It's technically undefined behavior, but in practice it will work perfectly well on almost all C implementations, and in the infinitesimal number of cases where this structure is actually useful, portability isn't a major concern.
nknight··on The guy who made it so difficult to open your bag of potato chips
Well, you're doing it wrong.

From the perspective of a right-hander: Hold the bag upright with the notch on the left, use your left hand to grasp the upper-left corner, while using your right thumb and index finger to begin tearing downward. As soon as you break into the actual cavity, begin tearing rightward.

Invert appropriately for a left-hander.

Or just do what I do and keep a pocket knife around. Shrug

nknight··on Apple rejecting applications which use Dropbox
No, Thomas, it isn't, because I'm not arguing you are wrong because it's you making the statements. On the contrary, as I said, you are largely correct. I'm arguing you're being an ass. Separate issue.
← PreviousPage 4 of 34Next →