arbales's comments

The Unfinished Nation by Alan Brinkley

Apps have different reasons for accessing SMS messages: confirming phone numbers via SMS, SMS bridging like previous versions of Messenger or Hangouts, etc.

The link eco posted is the right place for everything else.

There are a lot of opportunities to create great tools for designers – and you're right that QC has an uncertain future. However, QC is a really powerful tool, and shapes the way we design at Facebook. Whatever the future may bring, you can get real value out of this tool right now, and we think that's impactful.

Those lower-level patches can be integrated into your work in cool ways, they're there if you need them but don't get in the way.

A lot of individual parts of QC compositions can be replicated in the browser today, but the overall performance and rendering quality of QC for complex systems is still unmatched. As for universality, today most people designing for iOS and Android use Macs, so that's where we invest the most.

I hope you all give Origami a try :)

I think adding tiers would muddy their service model – the default answer is /always/ not to do something, adding a feature or constraint should only happen with a compelling reason.

It actually /is/ a bonus – because you're already employed, and salaried, there's no obligation for your employeer to pay you more for services rendered. I'm no lawyer either, but Google seems to think "Referral Bonus" is a common thing.

+1

"or if you leave before you file for the bonus"

my point is asking for a bonus for growing the team /after/ you've left, thereby shrinking the team, is kinda silly.

Bummer you think that, bro. Bad mouthing anyone is something we should all work to grow out of.

Oh don't get me wrong, if someone actually owed me 10k, I'd totally care /and/ be aggressive about collecting, but that's not the case here.

Startups, especially small ones, need not waste time with HR infrastructure like this – they're building products. HR should be ad-hoc and people-driven. If that's a problem, there are numerous larger companies to work for that devote their time to things like that. It's not unreasonable to expect someone to ask/remind the company about their referral bonus – and if he cared that much about it, he'd have collected before he departed.

My point is – spilt milk. Move on, build other opportunities for yourself, and don't forget again :D

He's really not owed anything. He neglected to collect his referral bonus it before leaving, bummer.

Really disappointed by this post. As a long time friend of Miso and the awesome people there – the people responsible for several awesome open source projects (Padrino, RABL, to name a few) – it makes me really bummed someone would choose to bring an issue up in this way.

I've never heard of a former employee receiving a bonus – referral or otherwise. The idea of a referral bonus is rewarding someone for /growing/ the team, and if you leave before that term is up, or if you leave before you file for the bonus, it's ridiculous to ask for it later – especially when you've already deflated your good will with a company. Moreover, I've not heard of people receiving a referral bonus after forgetting to claim it. I've forgotten to claim one! But I'd never think its anyone else's fault but mine, and my company is backed by an enterprise with a lot of resources.

Hey, I dunno, maybe I'm too busy putting my heart in the work to focus on stuff like this. People like the `jzhwu` whine, foster negative energy, and distract our community from focusing on good work.

Or maybe I'm just secure – financially and mentally. I don't need to squeeze money from former employers or vent my discontent because I'm focused on what I'm doing now, and what I'll do next, and how I'm growing as a designer and a person. I hope this guy discovers a more mature mindset before he does more damage to his career.

Finally, I'm also disappointed by the many people who can't see this for what it is – I assume they're the same crowd that's taking to badmouthing "brogrammers."

I'm not convinced this is actually a good thing to do. As noted by others, its unsuitable for dynamic content, and less direct than `$.data(...)` barring page refresh.

Just not sure what client-side workflow this kind of tool is used in.

The privacy policy, meanwhile, states…

"We will not share personal information about you with other people or nonaffiliated companies, unless we have your permission…"

If you've been using it and its comfy, just stick with it. People will just care about the code anyway.

Ah, no biggie. Go Ahead and run with Amber.js, launch your site and updates your namespaces. I doubt they'll be any toe-trampling confusion. At most there'd be one or two feathers ruffled, but we're all intelligent adults, and its totally cool to share the name. Sharing /is/ caring after all.

@jccodez the web app and iOS apps both leverage the same RESTful API. We're planning on opening the API to other consumers as soon as it reaches a ~1.0 state.

That's fairly typical though.

The Do team has been using Grove for a while now, and we're really liking it. The web app supports embedded content and gravatars, and connecting via IRC is great for those who love it.

We used Convore in the past, and Grove has definitely encapsulated the best parts of Convore along with laser-focused features and great performance. We actually can't wait to be a (or the first?) paying customer.

Designers, come one come all – we need you to make Do the best it can be. http://www.authenticjobs.com/jobs/10457/product-designer

Hmm… I've actually never heard of FieldForce.

I can also say with confidence that our strategy complements Salesforce's, and shouldn't cannibalize their offerings in the enterprise software market. Do is for small groups.