513 karma · joined July 17, 2008
Imagine what his experience would have been like had the other people he'd encountered had felt similarly empowered.
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...
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.
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.
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.
- Zodiac by Neal Stephenson (rereading for the nth time)
- The E-Myth by Michael Gerber
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...
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.
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.
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.
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.
- 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?
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:)