thomasptacek
Sales is mostly about moving a process forward, so your only goal is to get to the next step.
If the VC isn't a full partner, your next step is to get to a meeting with a partner.
If the VC is a full partner, you want to ask, ``what's the process you use to decide on investments''. Usually, there's a dance of customer-validation meetings that precedes a ``partner meeting'', the outcome of which is a term sheet. So you want to chart out the state machine that terminates in a partner meeting, and then transit from state 0 towards that meeting.
(1) Reads like "case-in-point" for Norvig's argument that the GoF patterns are artifacts of less expressive languages. Most of these examples battle clearer, more effective idiomatic alternatives in Ruby.
(2) Yet another misinterpretation of what Chris Alexander meant by "A Pattern Language". The GoF book isn't a cookbook, it's a starting point.
(3) This document didn't benefit at all from being "typeset" in PDF; any Wordpress blog with syntax highlighting plugins would have presented it better.
Wouldn't it be cool to see the "real" design patterns for Ruby?
What I see work, over and over again, is companies manufacturing surveys or studies that come up with numbers and metrics about the market, like, "20,000 enterprises are deploying technology to stop the Storm worm". Some companies will do annual press releases about an official-sounding report they generate, like, "Weboopia's 5th Annual Twitter Study Concludes 4,897,489,281 Messages Delivered Over Twitter In 2007".
We didn't do much better, because we were also repped by a PR company, and playing the same pasteurized process press food strategy as the rest of them.
Which is my point. Wasting money on a jaded middleman to circulate press releases every time you make a dot release isn't something you should aspire to do when you can afford it, and PR isn't something you should avoid doing now.
My current company, a tiny startup, is in Forbes, Wired, EWeek, Network Computing, Inforworld, Baseline, not to mention Slashdot, Digg, and Reddit. Didn't spend a dime to do it. Definitely got lucky, but there's also definitely a trick to doing it.
I agree with the "survey" trick Graham talks about. I've seen that work over and over again.
The conventional wisdom is, "go to the Bay Area, it'll be much easier to find smart developers." It is, in fact, very easy to find smart developers in the Bay Area. Unfortunately, they work for Google.
Also, careful with words like "later stage". You're "later stage" as soon as you hire the first person who isn't getting a founder's stake in the company. For us, that was weeks, not months, after the birth of our company.
It's also obvious that developers are more expensive to hire anybody in San Francisco than in Des Moines or Minneapolis.
Also, please note the bias towards founders in these discussions. A tiny team of founders is a good start, but you eventually need actual employees.
Isn't this the problem Facebook is supposed to solve? =)
To restate the original point: I feel like some of the people on this forum approach starting a business the same way they approach applying to college, or to grad school. That is not how it works. Your success is not gated on the "grownups" in the admissions office, or the department, or Y Combinator, making a decision about you.
If you catch yourself thinking about it that way, stop. Even if you get your 2 month's consulting dollars out of Y Combinator, nothing else in business works that way. There's no professorship to apply to once you get funded. You actually have to engage the market and win.
Hello, Paul. I'm selection bias. We haven't met formally, but you're obviously acquainted with me.
As a serial startup founder with 2 VC backed companies behind me (one as a founder) and 2 bootstrapped companies (both as a founder, one current, thriving, and multiple years old), let me respectfully call bullshit upon you.
To support my calling down of The Bullshit upon you, let me focus your attention on two completely obvious facts of the industry:
Fact the (1)st: the Overwhelming Majority of thriving web startups are not YC-funded.
Fact the (2)st: the Overwhelming Majority of YC applicants do not collect $16,000 (one solid month of consulting dollars for a skilled developer) from Paul Graham.
If your dreams don't survive not collecting a vanity round from Paul Graham, your dreams are weak and don't belong in the industry to begin with. I leave you with that thought.
If you need a large team of very gifted engineers, start in a college town that isn't Palo Alto or Berkeley.
Second, even if that weren't true, opening things up is actually not out of character for MSFT, despite the conventional wisdom. For instance, you can download near-complete debug symbols for the underlying operating system. If you've ever read assembly with and without PDB files in IDA Pro, you know what a big deal that is.
I'm guessing you've never actually used it, because you're using the word "disassemble" to describe it. Like JVM bytecode, CIL is unambiguous, explicitly typed, and doesn't rely on aliasing; therefore, like JVM bytecode, it is easily reversed back out to a high level language. You're not reading CIL opcodes in the Reflector, you're reading C#.
I wonder if this is a valuable lesson for developers here. Bytecode VMs do not offer strong protection of your source code.
There's a strong response to this statement, and I'd love to hear it, but haven't yet: name one application whose adoption is hampered meaningfully by the current architecture of the Internet. Even BitTorrent works over NAT.
Innovation happens on top of the Internet, not inside it.