Not likely. Speaking for myself, at least, this is exactly the right
type of job post for this list---both informative and personable with
no obvious lawyer influence. I hope you get a positive response.
We just graduated from Portland Incubator Experiment
You received this message because you are subscribed to the Google Groups "pdxruby" group.
To post to this group, send email to pdx...@googlegroups.com.
To unsubscribe from this group, send email to pdxruby+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pdxruby?hl=en.
This is, as the others said, a model for a job posting.
It is succint. It describes the technical areas of concern. It orients
the reader as to what the service or company does and as to what kind of hiring
arrangement/commitment is desired.
Recruiters should study/model this.
* original Apple machines vs. typewriters
* Internal Google Mail (gmail, eventually)
* Balsamiq Mockups, I believe
* Amazon's developer offerings
Perhaps a stretch for the off-topic topic:
* GNU userland and most (all?) modern *nix kernels
* self-hosting language compilers
> Is this a secret to startup success; be your own customer? Use your product
> to build your business?
A bullet, surely, if not the silver one, for all the reason Brad
outlined. A dog-food eating culture succeeds by exploiting the human
tendency to in-group bias: if we _are_ the user, we offer preferential
treatment to other users, identifying more readily with any distress
they might suffer. Self-consumption can subtly degenerate and, in
doing so, suffer from extensive Not Invented Here syndrome. Countering
that is a matter of explicitly defining core focus and the
establishing the primacy of the pursuit thereof, if you're getting a
chance to bootstrap your own culture. Self-sustaining, off-grid
cults--religious and secular-ish--do this really well by ritualized
recitation of core beliefs: they can exploit connections to the world
at large without eroding their essential identity. Status quo bias can
also be a problem: as a user you have incentive to not make radical,
disruptive changes to a product which you might have made, with less
difficulty, from a more removed position.
Hmm, that paragraph took a strange turn somewhere. I'm, uh, not at all
advocating that start-ups should be organized along the lines of cult
Brian L. Troutwine
Actually no. We were looking in to how people collaborate, and
specifically how young women use SMS. We also were looking in to how
to use group text messaging to organize protests. There were ideas
from how bike messengers communicate also thrown in, and a bit of how
people used .plan files and the finger command on old university unix
servers. Then a bunch of prototypes were built in a hackathon. Some
with IVR, some with voice, some with flash web recording, some with
pictures, some with text messages. The twitter one seemed compelling.
After about a month, there were only 100 users, but a 100,000 messages
It was not a tool for ourselves nor for internal use. It was an
intentional effort to develop a communication product in a space we
thought was interesting. That is, mobile, casual, semi-private, blog
like, limited feature, fluid communication.
The company was Odeo.com, a podcasting company. I should know, i was
the 1st contractor, then 1st hire, then lead developer.