Location: SF Bay Area
Remote: No
Willing to relocate: No
Technologies: JavaScript, Angular, Node, MySQL, MongoDB, Meteor, React, ES6, Socket.IO, D3, Mocha/Chai, Grunt/Gulp
Resume: https://www.linkedin.com/in/yaliceme
Email: <my HN handle> + <gmail>
367 karma · joined January 12, 2012
Location: SF Bay Area
Remote: No
Willing to relocate: No
Technologies: JavaScript, Angular, Node, MySQL, MongoDB, Meteor, React, ES6, Socket.IO, D3, Mocha/Chai, Grunt/Gulp
Resume: https://www.linkedin.com/in/yaliceme
Email: <my HN handle> + <gmail>
We actually never upvote our own stories or ask others to. It's hard not be curious about the comments, though, and we make a point to identify ourselves in our replies.
We picked GH stars because it's a transparent public number. Also because it's a relatively lightweight ask that still means a little more than a retweet or FB like. This campaign is about the existing Meteor community reaching out and encouraging new people into our community, and raising money for CodeNow is in the same spirit of accessibility and sharing.
Like Bahamut's comment shows, people do hesitate to star something they aren't actually interested in, and that's good; we want people to actually make an effort to tell their friends why they should check out Meteor. And then, if they succeed, it only takes 1-2 clicks for the friend to register their interest and get counted as part of the campaign.
I'd say you should only star the project if you genuinely like Meteor enough to star it.
If you're still on the fence about Meteor but like the cause, I'd encourage you to donate directly to CodeNow at codenow.org.
Basically, she'd listed some furniture for sale. A guy contacted her with praise for the item and said he was a purchaser for a regional furniture reseller -- he finds nice used furniture for them and gets a cut of what they pay to the original owner (e.g. my mom). The two of them agreed on a price (including his commission), then he mailed her a check from "his company" and asked her to wire him his cut. At the point I found out about this (it came up in passing completely by accident), she'd deposited the check and was planning to wire the money the next day.
I told her it was a classic scam and to please not wire the money. She didn't believe me; she'd successfully sold furniture on craigslist before, the guy's e-mails sounded legit, and the bank seemed to have accepted the check just fine. I told her it takes a few days for the check to fail. She still thought it was fine, but for my sake, agreed to at least wait a few days.
Sure enough, the check bounced. My mom described how masterfully the scammer worked upon her feelings in the meantime, asking where the money was, sounding hurt and angry that she was withholding his "cut" on purpose and trying to cheat him, saying he'd trusted her with the check because she seemed nice. Even with my dire warnings, she felt bad about waiting for the check to clear, but luckily she did.
This seems to me like a classic case of designers thinking of visual "prettiness" first and actual utility second.
Facebook did this for a while with Timeline, until they fixed it with the newer Timeline which keeps the posts to one column. It really looks like Google+ is just ape-ing Facebook design, even when the design has implicitly been admitted to have been a bad idea.
I am willing to be persuaded otherwise, though, if someone wants to make the case.
- Dror Matalon figured out how to use MySQL with Meteor. Blog http://www.fastcolabs.com/3007015/how-use-mysql-meteor Github https://github.com/drorm/meteor-sql & Talk http://www.youtube.com/watch?v=dToSn_FOISI&utm_source=bu...
- LShift wrote a blog post on how to achieve live updates to Meteor from Postgres http://www.lshift.net/blog/2013/02/25/live-updates-to-meteor...
- Cory Simmons has some useful notes here: https://github.com/CorySimmons/meteorwin
Related Meteor-talk thread here: https://groups.google.com/forum/?fromgroups=#!searchin/meteo...
- Stephen Darnell made an MSI installer for 0.6.1/0.6.2 https://groups.google.com/forum/?fromgroups=#!searchin/meteo...
Hacker Fortress and Chez JJ are both lovely. Chez JJ has been around a little longer, so they are more organized and hold great events; Hacker Fortress is a bit newer and more chaotic, but is more competitive on price. Both have great people.
Of the three, StartupHouse seems to be "trying" hardest in that the startup-ness is very in-your-face when you walk in. Key articles by Paul Graham and similar are hung up on clipboards, everybody is hacking away on keyboards, and the whole place has a sort of dark, moody, intense feel to it. I only visited once, so take my impressions with a grain of salt, but it didn't feel as friendly as HF and ChezJJ - most people didn't look up or seem to notice there were new people (maybe partly because there are so many people there), and the guy who showed us around was "on duty" and looked it. Whereas HF and ChezJJ felt like actual homes and not just places to hack.
In terms of physical building, HF literally feels like a fortress on a hill (huge mansion, isolated from surrounding houses, great view). ChezJJ is a cozy, comfy normal house on a street where the houses are close to each other, with fruit trees in the backyard (yum!). StartupHouse is a retrofitted warehouse and feels like it.
Whatever place you choose, I highly recommend staying in some kind of hacker house/hostel. The community you get from this living environment cannot be approximated elsewhere.
'I'm working at a small startup. Our business model is "Taking free drinks from industry events and reselling them." Oh, hey, I should get going.'
I am more interested in the meta-question: what are the implications of this question? I.E. if we knew for certain that the answer is "yes," how would this change our behavior (and likewise if the answer is "no").
I would think: if we knew for certain that some people can program and some people just can't, we would focus more energy on sorting people early on, to avoid wasting everyone's time trying to teach the unteachable. By contrast, if we knew for certain that everyone could program given the right circumstances, we would focus more energy on devising better teaching methods, etc.
Because of this, I am inclined to maintain a deliberate bias toward "no" (I.e. I am inclined to behave as if anyone could learn to program). Even if the answer really is yes, there are sure to be some cases where a "programming-capable" individual struggles at first for some reason, and an "anyone can program" general attitude is more likely to save them from mis-categorization as a non-programming "goat."
I worked on this startup for about 7 months with 3 other grad students (at the time) and thus have spent way too much time learning about this problem, the challenges involved in addressing it, and prior/existing attempts to do so. We directly interviewed over 100 potential customers for it, managed to track down and talk to other founders in this space, wrote a full business plan, etc. Here are some of my insights:
- Far and away the #1 most commonly asked question we got was: "But won't people have sex in it?" The #2 most common (arguably a corollary) was “How will you keep them clean?” But that’s not the interesting part... the fascinating thing is that you ONLY get these questions when people are envisioning something similar to the Sleepbox (frequently mocked as “Sexbox” or “Sleazebox” in online comment sections and the like). Neither Metronaps (i.e. high-tech recliner) nor Yotel (i.e. super-compact hotel room) seem to inspire this “ick” factor. Why? My hypothesis: Imagine a spectrum from “chair-like” (zero enclosure, zero privacy) to “room-like” (total enclosure, total privacy). On the “chair” end, it doesn’t really occur to us that some stranger might have sexed on it, even if it’s totally possible. On the “room” end, we know full well that strangers probably HAVE sexed there, but it doesn’t bother us because we consider a private room to be an acceptable, non-sketchy place to do such things. It’s only at some point in the middle that the perceived “wholesomeness” of the design plummets dramatically... we are squicked by the thought that some stranger may have sexed somewhere they are not SUPPOSED to. This effect was so predictable that I started calling it the “Unwholesome Valley” (like the “Uncanny Valley,” but with a different x-axis) For NapTime, I had some ideas for how to get safely to the left, “chair” end of the Unwholesome Valley while still providing a sense of security (highly important to most people we interviewed) and making access restriction a possibility (essential if you want to make any money.)
- People often think of airline travelers as the most lucrative market for a sleep pod business, because they’re always tired, they’re a captive market, and travelers are often willing to spend more money. However, there are a few major hurdles that make airports a difficult place to make money (most of these I learned from talking with a founder who had tried to do an airport version of their napping business, without success). Perhaps the most non-obvious is this: airports are empty most of the time. Most airports have four “spikes” per day when it is crowded; the rest of the time, it is almost totally deserted. Most of us perceive airports as being busy all the time; this is because we, as travelers, are only there during those spikes. Businesses who sell to airline travelers know otherwise. The “spiky” nature of airport occupancy is a particular problem for a napping pod business because 1) Most of the time, there are no customers around and 2) When you are suddenly surrounded by customers during a spike, you have limited ability to take advantage of it, because each pod only holds one person (unlike an airport coffee stand which is limited only by how quickly they can perform each transaction). However, I do believe success is possible if you account for the challenges while designing the business model and the pod itself.
- Despite the technical challenges, I believe that it is better to have a “vending” model where each pod is independent and self-service, rather than a “sleep salon” model where the pods are grouped together in a lounge with an attendant. The primary reason (again, according to founder interview) is that tired people are extremely reluctant to walk ANY distance to get their nap, so you need to locate the pod exactly where the demand is (demand is spread out within the building, and so too must your pods). I would also hypothesize that tired people would prefer not to interact with a human attendant and deal with the self-consciousness of sleeping in his/her presence.
Long post, I know, but this was practically my whole life for the better part of a year, so I have lots to babble about. My cofounders ended up ditching the project upon graduation despite seeming very gung-ho about founding up until that point. I put the project on ice, but I would love to pick it up again someday under the right circumstances and with the right people. Who knows... if you’re interested, contact me. I live near Mountain View.
>"we obviously don't mind being made fun of for our incompetence at things we don't want to do in the first place."
This reminds me of the "protective incompetence" that paul graham talks about in "How to Start a Startup" (http://www.paulgraham.com/start.html):
People who don't want to get dragged into some kind of work often develop a protective incompetence at it. Paul Erdos was particularly good at this. By seeming unable even to cut a grapefruit in half (let alone go to the store and buy one), he forced other people to do such things for him, leaving all his time free for math. Erdos was an extreme case, but most husbands use the same trick to some degree.