373 karma · joined February 10, 2011
> Think about how difficult it would be for a self-driving car to estimate this.
For sure you're right in the near term. But assuming we achieve super-intelligent AI that we manage to corral into a benevolent relationship with us, perhaps difficulty wouldn't be an issue at that point.
> Even more importantly, how would two self-driving cars cooperate in the event of an inevitable accident? Would we allow them to directly talk to each other, or are they only allowed to interpret each others' trajectories?
Yeah, this is getting good. Assuming we have those super-intelligent machines, those cars should be able to share pretty much all relevant data before a collision. So how could the car determine the greater good option? Is one life equal to another? What if one is rich and one is poor? What if one is the president? How could they even collaborate if they don't share the same basis for valuing human life? Could car companies realistically have diversity in those algorithms, or wouldn't that just lead to lawsuits against cars that were overly aggressive or passive? Nobody wants an unsafe car, so would car companies have to compete in their creation of aggressive algorithms? Or would it be a factor of cost... that you need to pay more for a car that guards its occupants more strongly... leading to more and more aggressive cars as they compete for the crown? Honestly, this line of thinking leads me to think we'll eventually need these values to be dictated and homogenized... requiring a strong central government, and aggressive detection and punishment of aberration. Or else a mad max style zero sum game.
Forgive the digression into fantasyland, I just found the ideas and questions here to be inspiringly interesting.
I can't speak for others, but the reason I find meteor interesting is because it's one of the only frameworks to address isomorphic javascript, and because it has some really interesting realtime features out of the box. The fact that it's backed by a team that has some venture funding (and therefore some runway to continue improving it) is a definite plus.
> So without the financial backing Meteor is just another open-source web framework.
I don't understand this point. Even _with_ the funding meteor is just another open source framework. Isn't it great that we have a number of open source framework options to suit different needs?
> I really don't think that my company enjoyed paying me to rebuild a platform that they already paid for because the Meteor evangelist they hired before me decided they wanted to be an overpaid consultant instead.
You haven't really explained _why_ you needed to rebuild it. Perhaps meteor didn't suit the use case for this project or perhaps you felt more comfortable/productive in another framework. You haven't really made a case against meteor or a convincing argument about why adopters would need to switch to another framework if MDG failed as a commercial business.
I went to a pretty good school (Northwestern), and while I don't regret it, I also don't think it's particularly affected my life one way or another. A state school diploma could have gotten me into my first position, and from there on out it was my performance that led me from one step to the next. It wasn't until I started to learn and build things for the love of it that I really started to create bigger and better opportunities.
I now live in a community in Austin that has some similarities to what you're describing. Super-competitive, high-achievers. But I think it's important to maintain a healthy appreciation for the artifice of it all. And while we encourage and try to feed the strengths and interests of our kids (I am helping my 6-year-old prep for an advanced math class), I think it's more important to try to raise happy, well-adjusted, non-jerk kids.
If someone asked that, I would probably consider that a red flag, that they are mistrustful of "business types" and probably difficult to work with.
Whoah, that seems a little overly pessimistic. We _do_ have alternatives, they just aren't economically competitive with fossil fuels. So I say bring on supply constraints... anything that raises the price of fossil fuels helps to make alternatives more attractive and increase investment into their research and refinement.
So I'd still be way more concerned with the CO2 problem, overfishing, pollution, mass-extinction... all that stuff.
However, if you are totally fresh and want to gain some experience, it can be worth your time. The market for developers right now is such that you may not need to take such a pay cut vs a bigger company. This is the real variable. What are you giving up. And while you may work about as hard as a founder, you aren't as likely to wind up ruining your credit and destroying relationships with family and friends due to the incredible stress.
So it may be worth it for the experience. Just don't get sold on being an early employee as a path to riches via your equity. That path is vanishingly rare.
I also totally dig meteor as a huge step-up in how to build web applications. I think they solve a big problem that most people are still working on (react also looks interesting)... not having to duplicate your business logic and rendering code. I think that's a huge benefit to getting things done quickly. Plus you get real-time rendering of data changes in your app, largely for free.
So I wouldn't call these genericX.js libraries. I think they are enabling new opportunities and are worth the interest they're generating.
http://coding.smashingmagazine.com/2012/10/09/designing-java...
I agree that you probably only want to use a small subset of jQuery (e.g., none of the UI, none of the transitions), and zeptojs is actually a really good alternative. But it really does provide some convenience.
And honestly, if you can get more focused feedback early on and avoid pointless forum rants about bootstrap, that's probably worth it even beyond the emotional benefit to avoiding assholes.
I think the other key part is that they're not just evaluating you on the bit of work that you're doing. It's largely about your communication during the project. If you just took the project and banged out a perfect feature without talking to anyone or asking questions, I'm guessing you wouldn't get an offer. In order to make an all-remote workforce work, communication is incredibly important. "Communication is oxygen" is the mantra at Automattic. And the channels we use for it are IRC and our yammer-like system. We rarely talk to each other and almost never use email. That's really non-standard, and you can't easily get a feel for that in an interview or with pair-programmed fizzbuzz.
In many ways, I think working at Automattic is somewhat similar to contributing to an open source project (to be fair, I haven't done a ton of this). And that makes sense, given its roots in and continued investment in open source. In fact when one developer asked if we could open source a particular component, Matt's response was that he was pretty much ok with open sourcing everything except our passwords. Given how open source works -- your voice in a project basically equals your investment and contribution to it -- I think the paid-project interview makes some sense in that light.
Anyway, I'm kinda responding to a few posts here, but I hope that gives a little more background into the process.