HNHacker News
TopNewBestAskShowJobs

spoondan

1,301 karma · joined November 17, 2008

submissionscomments
spoondan··on Why We Still Believe in Private Offices
Have you actually worked in an environment like that? In my experience, hoteling as the only option is deeply unpleasant. People like to have a single place to go. They like to have a desk they can personalize. They like to have a place they can leave their stuff overnight.

If you only provide hoteling, I think the majority of people will just claim a desk as theirs, and you effectively have no hoteling at all.

spoondan··on Steve Wozniak remembers the early days [video]
The term, "staging area," (in the sense of a place to setup) was popular several decades before Git existed.
spoondan··on Migrations and Future Proofing
This is a really good write-up.

In consulting and mentoring on this topic, I've found a lot of engineers push back against how "dirty" it is to have multiple copies of the data around in different formats. It feels wrong to not have a single, authoritative data format at any given instant. If the idea is to change the column type, why not just `ALTER TABLE ... ALTER COLUMN` instead of `ALTER TABLE ... ADD`?

But if you think about it, excepting trivial cases, once you're migrating data, there are parallel realities at least for the duration of the migration and deployment. It's not a question of whether you create divergence by versioning/staging (in some fashion) your data. It's a question of whether you manage the divergence and convergence of the parallel realities that already exist as part of a migration. If you don't, you either incur downtime or risk data corruption.

One big win here is that, by being disciplined about your code and data changes, you can cleanly separate deployment from release. You can deploy a feature but have it disabled or only enabled for a subset of users. Releasing a feature means enabling its feature flag, not orchestrating a set of migrations, replications, and deployments.

spoondan··on Show HN: Codassium – A better way to conduct remote interviews
I've used Codassium for about two dozen phone screens starting from when you posted the prototype last year, and I think it's great. Here are a few thoughts/issues I've had using the prototype and Lite version (I've not yet tried the full version):

I can't select C/C++ from the language drop down.

About half of the time, I don't use the video chat functionality for one reason or another. I'd love in those cases if I could simply close the video conferencing panel to have the editor full screen.

Even if you don't allow me to disable video conferencing for the Codassium session, I would recommend different messaging on the right hand side panel. I've had a few candidates say that it isn't working because the right hand side just says, "Loading..." when we don't use the video conferencing.

There's a typo on the Tour page: "Schedule an interview via Codassium is easy," should be, "Scheduling an interview an interview via Codassium is easy."

I'm not a fan of the pricing plans. I'm unsure of the idea of limiting the number of uses per month in general, but the current limits are very unattractive. It's all basically oriented around each user only doing 3 interviews per month. I would prefer a limit on number of hours per day or number of uses per day over the total number of phone screens. As it is, everyone that I've turned on to Codassium would have to get a Custom Plan.

It'd be nice if the things I type versus the things they type were differentiated in some way. Maybe just a subtly different background color?

spoondan··on Judge rejects $324.5M settlement over Apple, Google hiring
the bulk of the agreement was not in fact about poaching engineers, but rather sales and product people

Do you have a better citation for this claim? The linked Business Insider article does not claim such a thing, and the court filings the article cites do not support the claim.

The article cites Google's Special Agreement Hiring Policy that divides companies into three categories: Restricted Hiring, Do Not Call, and Sensitive. Only the protocol with respect to Restricted Hiring companies is constrained to Sales, Product, and G&A. Google's protocol for the Do Not Call companies seems to prohibit actively recruiting any employee at those companies. The article does not address whether other companies limited the scope of collusion to, "sales and product people."

spoondan··on LinkedIn to pay nearly $6M in unpaid overtime wages and damages to 359 employees
I'm curious about your story. Did the employee not complain to management prior to involving DOL? If the employee did, what happened that the employee's complaint was not accurately assessed and resolved? And if the employee did not, do you have an idea of why?

I mean these as honest questions. The law is complicated, and it's easy to accidentally run afoul of some provision somewhere while acting in good faith. Outside of retribution, it's preferable to resolve these situations amicably. It's faster for the employee and less risky for the business. So when I hear these kinds of stories, I like to identify where the breakdown happened. Was it a bad hire? A broken reporting process? A failure of the lawyers to assess the claim?

spoondan··on How I ended up conducting successful tech interviews with just 1 question
People can be proud of either of those accomplishments as well.

Honestly, I doubt "most proud" versus "best" makes a difference at all. Candidates generally explain their answers to these open ended questions. If they (for some reason) don't recognize the implicit, "And why?" part of the question, you just follow up with it.

The conversation will never be just, "Foobaz, next question." One way or the other, it will be, "Foobaz because..." It saved the company $2M/year. Or users really loved it. Or it improved the engineering process and made releases faster and lower risk. Or it was a really tough problem that required a lot of creative thinking. Or it taught me a lot about 3D game programming.

spoondan··on Hachette/Amazon Business Interruption
I'm not sure the situation is that simple. You bought the book through Amazon, but (in this case), you bought the book from the other poster. Putting them closer to, say, a shopping mall. As a shopper, who's has a stronger relationship to you—the store you bought something from, or the mall you bought it in?

I cannot see how a mall is analogous. In the mall, you choose the stores you go to and then look for the product there. You are explicitly entering different stores, and you have the obvious ability to return to that store. That builds affinity with the store.

With Amazon, the typical entry point is to search for the product you want. You don't particularly care who is selling it so long as the price, delivery, and trustworthiness are there. Maybe if all other things are equal, I'll choose a vendor that I bought from before. But, to be honest, for most purchases, I've only ever thought of it as being fulfilled by Amazon or someone else.

Anecdotally, I literally can't recall the names of any vendors I've bought from in Amazon. But I do know the places I like in the mall.

spoondan··on Pencil
That's a bit like saying that someone creating a web browser means it will never be as part of the OS.
spoondan··on iWork, Pages 5: An unmitigated disaster
There's another part of Apple's announcement that may help explain. Apple touts this release as "completely rewritten". Rewriting a complex app often results in a loss of functionality for no better reason than that things are institutionally forgotten. Invisible UX features like page dragging, keyboard shortcuts, etc. seem especially prone to omission by oversight.
spoondan··on Wireshark is switching to Qt
Node.js is not a rendering engine. It is a platform for implementing server-side software in JavaScript.
spoondan··on The Government Shutdown on the Web
It’s easy to imagine how this might often be the case: if the “inessential” public-facing Web pages are hosted on the same systems you’ve got to keep up and running for other “essential” back-end purposes [...]

Does this not then constitute an information leak about what seemingly "inessential" public-facing sites are housing "essential" services (that perhaps should not be on public-facing hosts)?

spoondan··on Vagrant: Create and configure portable development environments
I'm not the OP, but:

These systems are broadly the same. If you're writing your configuration from scratch, they're all fairly pleasant, and it's mostly a matter of preference. They share most of the same concepts (although the terminology differs) and features. In my experience, their differences are primarily in feel and community.

For feel: Chef gives you Ruby pretending to be declarative. Puppet and Ansible give you something more declarative at the expense of some expressivity. Puppet has its own syntax, and Ansible shoe-horns some procedural aspects into YAML syntax. I prefer Chef here. (Chef also provides a web UI that lets you edit things, but I strongly advise against using it except for managing nodes. Everything else should be code/JSON.)

For community: With configuration management, one of the things you'll want is good community involvement. You don't want to write every cookbook/playbook/module from scratch. From what I've seen, Chef and Puppet have a large head start in this department.

That said, you should be prepared to customize the community offerings. People generally implement precisely what they need, in precisely the way they need it, and your needs will not always align. Fork all of the community offerings so you can modify them while still pulling from upstream. Managing this is decidedly difficult, but there's no better choice. It's one of the areas where git submodules would be really great, if only they were nicer to use. If you're going to use Chef, consider also using Berkshelf for managing your cookbooks.

If you do not have configuration management in place, pick one of the major ones, learn the hell out of it, and get to automating your operations. Having your infrastructure as code that you can run whenever you want, that you can review to see exactly how something is configured, is life changing. Once you get to doing it, you will never want to go back to the bad old days.

spoondan··on Vagrant: Create and configure portable development environments
How are you reloading your Python application on code changes? Are you just working inside the VM? I've tried VirtualBox shared folders and NFS, and never had any luck getting file change events to propagate from my host to the VM.
spoondan··on The Hobbit, the Uncanny Valley, and what it means for 3D
Is it possible that the uncanniness of the more mundane in The Hobbit magnifies our affinity for the more fantastical? I don't doubt The Hobbit has improved on the technology and its applications to film. However, if the mundane is relatively more uncanny than in other films, perhaps a more modest improvement is benefiting from comparison to a lower baseline. That is, maybe the lows are slightly lower, and the highs are only slightly higher.
spoondan··on Rule of Zero (C++)
Per the article, "As an example, let’s write a class that owns a HMODULE resource from the Windows API."
spoondan··on TypeScript: a language for application-scale JavaScript development
The error about ^M suggests it has DOS line endings. Try converting the line endings.
spoondan··on The White House just open sourced their first Github repo
Actually, it's about the petition software being released on GitHub. Others have made this thread about the unrelated matter of how they dislike the government's use of this software.
spoondan··on This is the mail system
You missed a crucial part of the post:

    Machines can read [these error messages] just fine, though.
    Here's an idea: machines shouldn’t slap us in the face. 
    They should help us along if they fail to do our bidding.
He's not encouraging admins to replace useful debugging output. In fact, it's the opposite: he's encouraging email client designers to actually use the debugging output to let people know what went wrong. His mockup is quite clearly of an email client showing users relevant recovery options based on an underlying error message the client has parsed.

In other words, he's proposing that email clients treat MTA error messages precisely as they already handle raw headers. Full headers contain useful debugging information, but you aren't normally debugging.

spoondan··on Joyent unveils HTTP Signature auth scheme for REST APIs
A better write-up can be found on GitHub: https://github.com/joyent/node-http-signature/blob/master/ht...

Frankly, the blog post leaves a lot of questions and is short on links to answers. It would be easy to walk away from the post thinking Joyent's HTTP Signatures to be incompetently designed. It was almost enough to have me quip, "More like HTTPS Signatures," because the design in the blog post is only sensible over TLS. However, having found the above link, I see that it is the defaults that assume TLS, but that you can specify the signature contain all headers and the request line. This makes it possible to sign requests over HTTP.

I'd rather the defaults be reasonable for insecure transports (i.e., all headers + 'request-line'), since the TLS case is easily handled with just 'headers="date"'. If that's not to happen, I'd hope that implementations actively prevent the use of the defaults over insecure transports. Unfortunately, Joyent's reference implementation doesn't seem to do this.

spoondan··on Supercolliding a PHP array (inserting 65536 elements takes 30 seconds)
Even if the real C array contained a pointer to the last element in the LL (which it does not, it only points to the first)

What version of PHP are you looking at? PHP 5.3 and up seem to have a sensible linked list implementation in zend_hash.[ch]. The buckets only have a pointer to the list head, but items are inserted at the head. The hash has a separate list for ordered traversal of all items in the "array" and that has pointers to both the head (for traversal) and tail (for insertion). In both cases, list insertion is O(1).

Of course, as you said, the search for our worst case is necessarily O(N). Depending on your perspective, we can say that's a trade-off with hashes, a fault with the hash algorithm, or a fault with the collision resolution strategy.

spoondan··on Announcing Amber.js
Link is now https://github.com/amberjs/todos/blob/master/js/app.js#L24 because of the re-branding.
spoondan··on How Carrier IQ was wrongly accused of keylogging
No. Trevor Eckhart's video showed him capturing and recording the Android event log. This only demonstrates that the CarrierIQ agent running on the phone attached an event listener to keyboard events. While that behavior is consistent with a key logger, it's also consistent with lots of totally harmless software doing totally normal things.
spoondan··on Is This the Future of Punctuation?
This reminds me of Keith Houston's wonderful blog, Shady Characters (http://www.shadycharacters.co.uk/). Keith has written at length on the pilcrow, interrobang, and sarcasm marks (all touched upon briefly in this article) amongst other punctuation marks.

I am somewhat surprised that Shady Characters was not cited by the article. There is simply no better place to learn the surprising, entertaining histories of our punctuation.

spoondan··on The three terrifying minutes that created The Gunstringer
On the other hand, I'd much rather a client pitch a great idea that's technologically infeasible than just come up with something spur of the moment that they deem possible. If you start the conversation at, "This mechanic may not be possible, but the rest of the game is great," then you can discuss how to change the mechanic or maybe an engineer will have some brilliant insight about how to do the impossible. At the very least, you're starting with your best and working towards the technological compromise rather than starting with something that's already a compromise and may not reflect your best thinking.
spoondan··on What I Learned from Watching Notch Code
At the risk of going too far off topic and without intending to be too harsh: at least in the video, that interface looks nice, but there is too much lag between when a tap/gesture is made and when the interface reflects it. This breaks the direct manipulation metaphor and is, I think, a showstopper. The pinch to zoom example was particularly off-putting: how can I know how much I'm zooming when the interface doesn't track my gesture? I cannot imagine being happy with pinching, waiting a second to see what's happened, then pinching and waiting to adjust (repeat until I get it right or am too frustrated).
spoondan··on H.R.1981, the end of online privacy as we know it.
After her efforts to substantively alter the bill (to defang it or at least add oversight) were rejected, Rep. Zoe Lofgren proposed to rename the act to, "Keep Every American's Digital Data for Submission to the Federal Government Without a Warrant Act of 2011."

See Amendment 36 at: http://judiciary.house.gov/hearings/mark_07272011.html

spoondan··on Steve Jobs Sometimes Lies to You
I have a hard time believing that Apple doesn't have an internal protocol spec for FaceTime and created the protocol willy nilly.

You can design something very intentionally without ever having compiled a spec for it. There are certainly design notes, e-mail conversations, and, of course, the code itself to document the protocol for internal purposes.

Which makes me question how hard it could possibly be to submit an open draft to a standards body.

Assuming FaceTime has an internal spec, that does not mean it is in any shape ready for public consumption. For example, the spec could leave unspecified various things that Apple's particular implementation did not have to address. It could be written very informally. It could have fallen out-of-date as the protocol evolved.

None of this would mean that FaceTime was designed "willy nilly." There are processes less than ideal but still perfectly acceptable.

spoondan··on New patent troll Kootol emerges
My understanding is that if, as the article says, Kootol has received a Notice of Allowance, this patent has been examined and will be published unless Kootol abandons it (by not paying the publication fee). Additionally, the priority date on the patent is July 22, 2005. The priority date is documented by referencing patent 878/MUM/2005[1] filed in India on that date. I believe any prior art would have to predate the priority date, not the date of filing.

This does not mean that Kootol is not a patent troll or that this is a legitimate invention. I don't know what the claims in 878/MUM/2005 are, and its title reads completely insane in American English ("connecting brains to equally like brains?"). Kootol has filed for several other, similar patents[2] that cite 878/MUM/2005. I wonder if 878/MUM/2005 really backs all of these different claims, or if it is simply a vague-enough tool for them to be using to make new claims that can be applied retroactively?

[1] http://india.bigpatents.org/apps/RvhMPZb

[2] http://ip.com/patapp/US20100030734

spoondan··on EFF: forced disclosure of encryption password violates 5th Amendment
Encryption is not just something computers can do. You can encrypt your handwritten notes. If you do so, can the government compel you to tell them what you have written? If they cannot, how is this different from having a machine act as your agent in the encryption?
← PreviousPage 3 of 7Next →