In Soviet Russia, you power battery?
(this almost seems like a setup!)
It's more of a list view/ grid view. I'm curious in particular what do you think is bad UX ?
You can disable Google Now (I think) and just use the search. Check the setting in Google Now, and/or try disabling the Google Now app itself from your device's main settings > apps.
Isn't that the point of these seeds though? They are designed to work with Roundup, thus he was using the product as intended? Except Monsato doesnt allow that.
Monsanto has a policy to protect its investment in seed development that prohibits farmers from saving or reusing the seeds once the crop is grown. Farmers must buy new seeds every year.
Also, I dont think you are correct. This is exactly what the court said was wrong. I also dont think it helped his case that he already had first purchased Monsato seeds, then went and bought cheaper mixed seeds in the hope of getting similarly resistant seeds (unclear from TFA how many, if any, were Monsato).
[ Justice Elena Kagan said ]
"Bowman planted Monsanto's patented soybeans solely to make and market replicas of them, thus depriving the company of the reward patent law provides for the sale of each article," she said. "Patent exhaustion provides no haven for such conduct."
Well, there are a few "interesting" gems there. Though it's mostly business fluff. From TFA:
Such companies as Facebook (FB) and Google also have special teams that review the lines of code written by developers. It’s these people who get to decide when a new feature is ready to make its way to their websites. Not LinkedIn. It has one, huge stash of code that everyone works on, and algorithms do the code reviewing. “Humans have largely been removed from the process,” Scott says. “Humans slow you down.”
Uh, Okay. Automated code review? Um, where to begin? I think there an obvious misunderstanding on the part of the author of the article. Surely Google, FB, et. al., do CI and all sorts of automated testing. They just *also* use humans.
Incidentally, Google clearly has more products, thus more specialties and codebases. FB also, to a lesser extent. I dont think the Google Search team is the same as the Google Maps team or the Android team.
LinkedIn is a website, they have an API, messaging, maybe some mobile apps? It's not trivial, but it's probably not very close to the technical complexity of FB, and no where near the technical complexity of Google.
LinkedIn initiated Project Inversion to fix its issues and has since evolved into one of the poster children for continuous development
I think TFA misses the point in a very "PHB way" sadly. They took the time to make the devs happy and give ownership of features to devs. The result was the devs created an environment that was productive and could be continuously updated with less fuss.
To me, this is the poster child for creating a dev focused culture, and taking the time to do things the right way. Which, sadly, is the exact opposite of the conclusion of TFA and the LinkedIn PHB.
For anyone else who hasn't heard that term before: http://en.wikipedia.org/wiki/Vitality_curve
Luckily the Barns & Noble case revealed some of what MS has been hiding. I dont have the info top of mind, but IIRC it was a lot of nonsense related to calendar syncing.
LED's do not emit a sense of humor.
LED's don't emit a 'whooshing' sound (unless you catapult them or use a trebuchet)
I'd rather see someone side-step Verizon. They seem to have the LTE network to beat. Good for HTC though, every little bit to weaken carrier grip is welcome, be it from HTC, Apple, Google, or whoever.
Link to Original Source
why is SD card access a boolean decision? And why are all permissions granted permanently to apps?
Fair questions, but how would you have designed it? Think carefully about the edge cases and user experience for both questions. I think it also helps to keep in mind lessons learned from incessant dialogs. Users are now desensitized and trained to click OK, despite not having read the message.