HNHacker News
TopNewBestAskShowJobs

scottyallen

513 karma · joined July 17, 2008

You can contact me at hackernews@<myusername>.com or find me on twitter at http://twitter.com/scottyallen
submissionscomments
scottyallen··on How Egypt Switched Off The Internet
I use to work on the team that maintains the webserver that serves Google websearch. google.com.eg (and any other google search domain) can be served out of many of Google's datacenters, in various places around the world. The user is sent to the "closest" data center that can serve their request, to minimize latency. Country-specific domains don't have to be served out of the local country (that would be pretty unmanageable, given the number of country specific domains Google has).
scottyallen··on Southwest Airlines pilot holds plane for murder victim’s family
This is a great example of what happens when you give your employees the freedom and authority to do what they think is right, instead of enforcing a blanket set of rules. People are naturally compassionate and willing to do extraordinary things. It often is mostly a matter of getting out of their way to let them do what comes naturally, and rewarding them when they do something amazing.

Imagine what his experience would have been like had the other people he'd encountered had felt similarly empowered.

scottyallen··on Tech co-founder sought for ambitious consumer web startup
Holy crap. I think you're right. This could explain why I've had two different strangers corner me in the past month (and seen at least two similar pitches on HN), trying to pitch me to work on their pre-funding social network. They "have the secret sauce all figured out", they "just need need a coder to build it". Unfortunately, they "can't really get into details" until I sign an NDA. Needless to say, I still am pretty fuzzy on their secret sauce:)

It all fits though - up until now, I couldn't figure out why random shmoes that don't know anything about technology were getting excited about social networking.

I suspect Facebook/Twitter/Linked In aren't the end of the road for what we call "social networking", but I'll bet it's created by someone with at least some experience in the technology space...

scottyallen··on Chrome for a Cause
The going rate for donations to plant trees is around $1/tree (see http://www.google.com/search?q=plant+a+tree). Assuming the conversion rate is constant, that would mean the conversion rate is $0.10/tab.
scottyallen··on Appointment Reminder Launches
Totally understand - I wouldn't have made it a launch blocker either:) Great to hear it's on the roadmap though.
scottyallen··on Appointment Reminder Launches
This looks great. Nice work, Patrick, and congrats on the launch. I just sent my mom an email about it, and suggested she try your demo. Hopefully she'll sign up. She's a private tutor, and very frustrated by having students not show up to appointments. This definitely solves a significant problem for her.

Any plans on integrating more tightly with Google Calendar? That's where she currently keeps her appointments, and being able to suck appointment info out of there would be really useful for her. That being said, I have no idea how structured her data in there is (probably not very), so it may not be a super easy problem in the general case.

scottyallen··on Ask HN: Best way to transition from free beta to paid?
The question I'd ask myself if I were you is, "What's the COST of allowing all existing users to continue to use the app for free, and charge new users as they signup?"

If the answer is that there's little or no incremental cost (beyond, say, hosting costs and occaisional support), then I would allow all existing users to continue using the app for free, indefinitely.

Your beta users have likely put up with a lot of crap while you and your predecesor ironed out the kinks, added necessary features, etc. It's better to continue in their good graces and have them be enthusiastic evangelists for your product than risk angering them by jacking up the price.

scottyallen··on A Google Interviewing Story
The right way to approach this is to clarify the requirements. "Should I consider unicode?" will get you points with the interviewer, and will allow you to quickly clarify the scope of the question.
scottyallen··on Ask HN: Best books, blogs, podcasts on shipping more/being more prolific?
The War of Art, by Steven Pressfield. It's short but sweet. It's a writers description of "the resistance", an invisible, ever present force that actively works against you when you're trying to ship. More generally, it works against you when you "[try to do] any act that rejects immediate gratification in favor of log-term growth, health, or integrity."

The first part is titled "Resistance: Defining the Enemy" and is a great description of what the resistance is and the ways in which it works to defeat you.

The second part is about how to conquer the resistance by "going pro". There's a lot of pieces to this, but basically, it means figuring out how to show up every day and doing the work, day in and day out, with the explicit goal of conquering the resistance.

The third part is a higher level discussion of the resistance, and at least to me, was not as relevant.

Highly recommended book if you struggle with the resistance when trying to ship.

scottyallen··on Where are the roaches in NYC - the Great Urban Hack
I wonder how much this is a measure of the diligence of various inspectors versus a measure of roaches being present. Something like this could be highly influenced by a sampling bias...
scottyallen··on Ask HN: What are you reading right now?
- Stranger in a Strange Land by Robert Heinlein

- Zodiac by Neal Stephenson (rereading for the nth time)

- The E-Myth by Michael Gerber

scottyallen··on Ask HN: How many hours of sleep do you need to have a productive day?
I need roughly nine hours a night be fully productive, coherent and happy. I can get by on eight. Less than six, and I feel physically sick to my stomach, and lose my short term memory and sense of balance (really - I tend to bump into things and have fallen off things I was sitting on).

Working alongside people who can function on 4 hours a night, I feel like my need for large amounts of sleep is a big disadvantage.

This all being said, I've started consuming caffeine again after dropping it for nearly 10 years. Consuming a small amount of caffeine in the morning after having not enough sleep does wonders for my productivity, short term memory, and happiness...

scottyallen··on If David Heinemeier Hansson Was a Tech Recruiter...
Treat potential candidates like people, rather than interchangeable pegs that you try and fit in whatever square hole you're trying to fill at the moment.

This means:

- Spend time to build real connections and relationships with the people you're trying to recruit. Find out what the look for in a job, and if you none of your clients fit the bill, say so point blank, but that you'll get back to them when you find one that does.

- Build a tribe (in the Seth Godin sense of the word). Build a group of people that look to you about finding jobs and hiring. Organize events that get lots of smart technical people together, that isn't just a recruiting event. Think about the 37 signals blog and the conferences they've organized. Think Super Happy Dev House.

- Don't cold call. Speaking personally, I'm much more likely to talk to you if you email me. Aggressive phone calls are a major turn off. If you must call, don't call before 10am in my time zone.

- Being open about the companies and positions you're trying to fill. No caginess about what the company is, and being open about any potential downsides you know of.

- Don't recruit for companies you don't believe in.

- Know what you're talking about technically. This means not recruiting people for positions that don't match the experience they list on their resume. It means not recruiting them for positions they're highly unlikely to be interested in, based on past positions.

In general, recruit people like you would want to be recruited. In the short term, this will likely be less effective than more traditional approaches. In the long run, as you start building a network and reputation for integrity, I bet it's significantly more effective.

scottyallen··on Offer HN: Will Work For Karma
Why not try an a/b test? I bet that another color will test better...
scottyallen··on Offer HN: Will Work For Karma
Yes, this would be amazing. Thank you for doing this. Speaking for myself, I'm desperate for design help, but don't really know the best way to find/work with a designer.
scottyallen··on Can I Make My Developers Write Efficient Code by Giving Them Slower Machine?
My guess is the answer is probably yes, if you give your developers slower machines, they will start optimizing things for performance.

However, I suspect they won't spend the time optimizing what you want them to. Good developers HATE being inefficient. Sitting around waiting for something to compile gets your out of the flow of writing and testing code.

So instead of spending all their time optimizing the app, I suspect they'll spend a disproportionate amount of time optimizing the build process.

Not really the outcome you want...

Now, as you suggest, if there's a way to slow down only the running of the app, and not the rest of the development process, that would be useful and probably would cause the sort of changes you're looking for.

scottyallen··on What's the best way to find testers for my new iphone app?
How about hanging out at your local Starbucks, and offer to buy people a cup of coffee if they spend 10-15 minutes checking out your app and giving you some feedback? A bit scary for the introverted hacker, I admit. But I bet you get enough people to take you up on it to make it worth your while.
scottyallen··on Why we don't schedule deployments during off-hours
You're right - I should be more clear what I mean. "Oh shit" moments caused by a change you made due to pushing a new piece of code should never last more than a minute or two, between the time you realize something went wrong and the time you run the command that reverts things back to the known good state. At Shopkick, this usually means running a command which flips a symlink that points at the current code/config to use and restarts/reloads the server in question.
scottyallen··on Why we don't schedule deployments during off-hours
Deploying new code should never be an "adventure". It should be a simple, replicable process that allows you to safely stop or rollback at any given time. It should have enough checks in place that the impact from any given mistake is minimized. There should never be any "oh shit" moments.
scottyallen··on Why we don't schedule deployments during off-hours
When I was at Google working on web search, we didn't push search infrastructure during peak hours. I think this was mostly due wanting to make sure we had spare serving capacity to failover to, in case the push was broken/had performance problems/crashed/etc. Note that "peak hours" isn't the same as "working hours". Just a few hours when we saw our highest traffic.

However, we also had a strict policy of no pushing in the middle of the night, Fridays, or weekends, for all the reasons the article listed. Most problems on a relatively mature system occur when you're changing stuff. When stuff breaks, you want to have the people involved be fresh and thinking clearly. You also want everyone who might be needed to fix something available, in the office and in front of their computers if something goes wrong. Lastly, it's not sustainable to have your engineers/operations folks regularly giving up their nights and weekends for routine operations. You should save that karma for when everything goes to hell.

This is all predicated on having pushes not negatively affect production traffic when everything goes according to plan, and minimize the impact as much as possible when something does break. One of the best ways I know to do that is to increase the amount of traffic proportional to increases in your confidence that the change is good. The idea is that any push starts off by only affecting a small part of your infrastructure/traffic, and the longer you run it without problems, the more traffic/infrastructure you push it to.

At Shopkick, we do this by pushing first to a single machine, watching it for any errors for a few minutes, then gradually pushing it to the rest of our machines. If anything goes wrong, only a portion of traffic was affected, and the portion is well correlated to the probability of having a problem.

scottyallen··on Ask HN: how to sell an early stage startup?
You might consider listing it on flippa.com. Flippa is a popular place to sell web properties, but typically focuses on smaller sales (most are in the tens of thousands of dollars, at best). I've heard anecdotally that most sellers can expect to get 1-3x yearly revenue.
scottyallen··on PG: Thank you for putting on Startup School
Yes, thank you so much for doing this. The quality of both speakers and attendees was fantastic. It's really awesome to be surrounded by that many people that are as technical and as focused on building businesses as I am. I feel very blessed to have the opportunity to attend.
scottyallen··on Gift HN: Anybody want a subdomain of ww.com?
Awesome, thanks!
scottyallen··on Gift HN: Anybody want a subdomain of ww.com?
How about scotty.ww.com -> www.scottyallen.com? Looks like scotty.ww.com is probably abandoned. Thanks - it's cool that you're doing this.
scottyallen··on Hacker Slide: HN front page over time
This is really cool, and seems like it will be even more fun once you've collected a bit more data.

One minor usability tweak: having the slider "snap" to the hour doesn't quite feel right. The end result is that the ball is never actually under my cursor, which feels broken. Might be more usable if the mall always stayed with your cursor, but snapped back to the nearest hour when you let go.

Nice stuff though - it will be cool to see how you evolve this.

scottyallen··on How to Break the Trust of Your customers in Just One Day - Lessons Learned
To paraphrase what I think are his main points:

- Our free customers are really bad for our business. They complain a lot in really visible ways, they make up a lot of our support burden, and they never end up paying us anyway.

- Once we figured this out, we decided we don't want them as customers.

- We gave all our free customers an option to start to paying. Those that aren't willing to pay we don't care about.

- OMG!!1! What a shit storm this created. All those free customers that we don't care about sure complain a lot when you screw them, way more than they used to. This really sucks, and makes us look really bad. Oh, and fuck you tech crunch for covering Square and not us, and then kicking us when we're down.

- Boy, I really wish we'd sugar coated getting rid of all those pesky free customers so they didn't complain so damn much.

I see a lot of remorse for the outcome and lack of sugar coating, but not a lot of remorse for the actual underlying action. When you build something people rely on, and then take it away from your most vocal userbase, what exactly do you expect the outcome to be?

scottyallen··on The Importance of Giving a Damn (in people and software)
Now that's throwing down the gauntlet:)
scottyallen··on Tell HN: Startup School acceptances have been emailed
Nevermind, turns out I did get accepted, but the email got eaten by my spam folder. This is the first time I've lost an important email to the spam folder - kinda scary, particularly when you realize there's 1500 threads of spam in there...
scottyallen··on I made a fake-cake generator for my 30th birthday
Very awesome. I couldn't resist: http://cakesy.com/810b350ac
scottyallen··on Soylent: A Word Processor With A Crowd Inside
This would be really useful for programming, particularly refactoring. Imagine being able to quickly apply a relatively mechanical refactoring that still required human judgement (pretty common), and have other programmers do it for you.

I imagine it would work something like this:

- Select the files/directories/blocks of code that you want the refactoring applied to.

- Describe (in english) what the refactoring work should be, and do an example on one piece of the code.

- The work gets split (by file?) and distributed via a mechanical turk-like interface (extra points if it opens tasks in your favorite editor with syntax highlighting). As workers submit their work, the code is automatically built and tests are run (could be a callback to your local development environment, so you don't have to worry about shipping all your code up to the cloud and figuring out how to build it there).

Could be pretty awesome, particularly if you could enlist an army of freshman CS majors, bored programmers, and eager overseas engineers. I wonder if intellectual property concerns would be too high for people to actually use it though.

EDIT: If I still worked at Google, this would be a fun project to try internally as 20% project. There are lots of mechanical refactoring tasks that need to be done across large portions of the codebase, good build/test infrastructure to easily verify success/failure for a given task, and lots of bored/eager engineers that feed off of reward-based systems:)

← PreviousPage 5 of 6Next →