Labrador OmniMedia | Rails Developer/Devops Engineer | Sonoma County, California | Remote
Labrador creates software for the hospitality industry. Our flagship product, Slate, is an iOS app (think iPad wine lists) with a Ruby on Rails backend providing iOS client management and APIs. We've been in business since 2011 and are a sister company of Jordan Vineyard and Winery in Healdsburg California.
We're looking for an experienced Rails and devops engineer to develop and maintain our Rails portal on AWS. You'll be taking over a codebase from a top Rails contributor and interfacing daily with our support team and CEO.
Salary 140K+
The ideal candidate will have some experience with iOS, place a high premium on schedule flexibility and enjoy alcoholic beverages. Salary will scale up for unicorns that check all the boxes (Rails/AWS/iOS).
We use Github for source control and Slack for team messaging.
Agreed. The sample is very likely tainted by factors that made success much more likely than average if we believe that NFL coaches are both conservative (they forgo punts only when the odds are much in their favor) and rational (they are win maximizing).
Still, there is probably a case to be made that coaches should be a bit more aggressive, but that edge could be small enough that other factors (like perceived incompetence) dominate it.
I'd say the answer provided is so simplistic that it has very little explanatory power.
Commenters have already mentioned Uber and Groupon, but I'd go further and add YC love child Airbnb as well. They famously sold cereal to stay afloat etc. What does that have to do with tech hacking? Yet they have been lauded everywhere Zulily hasn't.
I'd be interested in how one separates a disruptive business that uses technology from Disruptive Technology? It seems to me there is a hair's breadth of difference between the two.
This is news for the simple reason that it isn't news.
Right to anonymity? Convicted felons lose their right to own a gun. Some might never use one to commit a crime, but they still lose that right.
This is no different. It is not reasonable to call this a slippery slope. These people were convicted of predatory crimes against children, and those of us who do not commit such crimes have nothing to fear as regards our anonymity until and unless we commit similar crimes.
Not all punishments end when you're let out of prison. Nor should they.
> I've got to say, I don't understand why people keep mentioning drop shadows, though. Drop shadows seem fairly uncommon. Even Google only uses them for mouseover.
Put your cursor in the search field. More shadowy goodness there. Click on your avatar in the upper right, the popover has a prominent (too prominent IMO) drop shadow. It's everywhere.
As to mouseover, I agree it's for confirmation. But if we need to confirm functionality with drop shadows and gradients - what message does that send about usability?
One thought is that perhaps we should have the drop shadows and gradients there to begin with.
I think we are splitting hairs here, but I agree that what we are talking about is affordance.
The reason why I use the term skeuomorphic in this context is because there are those who believe that what you and I believe is affordance is actually superfluous and ornamental.
What else is flatland design if not a complete rejection of the value of drop shadows and gradients as affordance?
The two most prominent buttons on the home page have subtle drop shadows and gradients. Google is actually a great example of restrained skeuomorphic design.
If I had to advocate for just one aesthetic (which is silly on its face), I suppose restrained skeuomorphism would be the one.
"According to various reports, when someone suggested to include a touch-typing tutorial in this intro as well, since many people did not know how to use a keyboard, steve Jobs simply said not to bother as those people would die out eventually."
If your audience is developers and designers, a pure flat design is great and will likely work well.
But normal people need their hand held as to what a button is. Subtle drop shadows and gradients are the best way to instantly get someone to understand that yes, this element does something. Something important is lost in flatland.
On a side note, the vault and picture frame image on the main homepage for layervault.com is the height of skeumorphism and realistic design. Beautiful, but also kinda ironic.
Agreed. There are low tech ways to achieve a similar result. But operators, servers and managers absolutely loathe anything that changes their steps of service.
The winning solution will be completely transparent to their current workflow, and will also be seamless to the customer. Until this happens I don't think we'll see widespread adoption of new pricing strategies.
For instance, a pricing increase when many/most seats are filled is probably best way to discriminate in a restaurant. Sophisticated pricing strategies like those could become commonplace with digital menus, and the staff wouldn't have to think about it - but they would see the effect in their tip total.
If this attempt at price discrimination does indeed become popular it will be via digital menus that update their pricing automatically, not via fiddly coupons. We are quite aways away from this still due to hardware costs and the sheer number of tablets that would be needed at most full service restaurants.
I have no doubt it would be a hit with consumers. Tuesday nights out would become "a thing" for the price sensitive. That's good for everyone.
Honestly one of the more impenetrable articles I've read lately. Just not very clear or well written. I'm not even entirely sure there is anything news worthy here. Just some dire need on Swisher's part to make a connection between PB and J and the famous peanut butter memo. That's not enough to justify an article.
You kinda did gloss over, well, everything that makes this letter good.
The letter is powerful because of how it said what it wanted to say. The examples and imagery are vivid; the message consistent.
What you wrote: "The real reason that most people cheat is because they don't feel loved" is right there, wonderfully articulated, in this letter.
The hard part of being married, and the hard won wisdom contained in this letter, is the realization that most of the time people fail us because we've failed them first. It's a recursive nightmare and the only escape is to forgive and continue to commit.
Easy to boil down to a tl:dr of "don't cheat" and dismiss. Knowing is not the same as doing (day after day), though.
I have talked to directors of Bay Area charities that tell me that Jobs was a generous donator personally. In fact this just happened 2 weeks ago, and the person defended him vehemently.
I use Assistly for one of our CS portals and due to sporadic downtime was interested to see what Groove had to offer after reading this post. In terms of marketing, this is exactly what you want to have happen. And after all the talk of meeting the feature set of your competition, I expected to see just that - feature for feature parity or better.
Instead what I saw was an emphasis on the social media SCRM features at the expense of having a functioning Knowledge Base, which really surprised. KBes (done well) are the real win for support since they are self serve. Moreover, this is a key feature of Assistly which they can't match.
I'd say Groove hasn't yet met the bar, which is slightly ironic given the tone of the article.
My goodness. This type of thinking is going to shackle you from ever doing something new and untried.
That's the most important lesson you don't learn in college: how to do something completely novel. And it's the most important lesson one can ever learn.
Labrador creates software for the hospitality industry. Our flagship product, Slate, is an iOS app (think iPad wine lists) with a Ruby on Rails backend providing iOS client management and APIs. We've been in business since 2011 and are a sister company of Jordan Vineyard and Winery in Healdsburg California.
You can download the demo on the App Store: https://itunes.apple.com/us/app/slate-menu/id1081898296?mt=8
We're looking for an experienced Rails and devops engineer to develop and maintain our Rails portal on AWS. You'll be taking over a codebase from a top Rails contributor and interfacing daily with our support team and CEO.
Salary 140K+
The ideal candidate will have some experience with iOS, place a high premium on schedule flexibility and enjoy alcoholic beverages. Salary will scale up for unicorns that check all the boxes (Rails/AWS/iOS).
We use Github for source control and Slack for team messaging.
Please contact me directly: [email protected]