57 karma · joined December 4, 2014
This may be a little far-fetched - there's likely easier ways to generate pretext - but it might be something for owners of Tor exit nodes to be aware of.
Un-informative and distracting. Probably doesn't make me a better founder. So funny.
I love Everything is Calm - probably because I'm a bad person. :-D
We built this so that teams can have real input and feel safe, while managers can get early warning on problems. What do you all think?
Remote: No
Willing to relocate: Yes, please (prefer Phoenix, AZ area)
Tech: JavaScript/Node.js (also Java, but that's ancient history)
Resume/CV: https://www.linkedin.com/in/sethstradling (full resume on request)
email:seth<at>simplelunch.co
I'm a research analyst (some competitive/market intelligence background) with experience with stats and software. It's not quite reflected in my profile/resume, but I'm the guy my teams depend on to learn new stuff and actually make things work (technical or not).
EDIT: Definitely trolling. See katm's (I'm guessing Kat Manalac's) post above.
You'll need a way to require re-tweets within 15 seconds, though, as with iPaulGraham...
Good luck!
Click through to the IBM live demo, and let me know if you think they're on to something, or if IBM just knows me too well.
If you're looking for one general type of user, go find a meetup group, class, online community, or other spot where they'll congregate, and just talk to them. Bring a laptop (or send a link) for them to test out, and maybe provide some sort of incentive or game to get them interested in giving it a shot.
If you're looking for two (or more) classes of users, do the same general thing for each separately, but either 1) try and line things up so that each group is interacting with the system at the same time (perhaps by only opening up the beta for a couple of hours) or 2) pretend to be a member of the other group during testing so that you can get feedback on at least half of your product.
OTOH, I officially let my chain of command know about my project last week (per company policy). I put it off as long as ethically possible because I do not have the same level of trust in them (also from experience). I do not know if there will be any repercussions.
If you trust (really trust) your supervisor, let them know. They'll appreciate it, and your team will thank you. If you don't, then don't. If you have IP agreements or other legal entanglements that they could use to destroy you, find someone with experience in those areas to advise you on a best path forward.
One more reason to regret him passing.
For me, I've been bouncing off the walls for 12 years in a large bureaucracy. Reading Eric Ries's Lean Startup and finding Paul's blog was like drinking water for the first time. I hope he has the same experience.
With my work, a lot of reviewers do love to hear themselves talk, but every so often they'll come back at you with really good, insightful stuff that I totally missed. I don't dare game them because I don't want to be putting out garbage.
Except for CH. We totally owe her a duck.
There's a real risk (of course) to killing the duck. Your client or your boss may hate you, and that's never healthy in the short run, but they also may come out of the interaction a wiser and better person. Or you may find yourself not working for an idiot, and be happier in the long run anyways. Keeping the duck alive is a bigger long-term risk for everyone.
Kill the duck.