Slashdot Mirror

An anonymous reader shares a blog post: There's one thing the Academy possibly didn't consider, or forgot, for this year's winner cards: typography. First, it's legible, you can tell all the letters apart. Second, it's somewhat readable, but the visual weight of "Moonlight" and the producers are equal and blend together. Lastly, even though it is just a winner's card, it's not visually appealing. I think it's fair to say it's objectively bland. That's horrible typography. Of course, anyone could've made the same honest error! You are on television with millions of people around the world watching. You are a little nervous, and you have to read a card. You will most likely read it from top to bottom (visual hierarchy) without questioning whether the card is right. That look on Warren's face was, "This says 'Emma Stone' on it." Faye must've skipped that part and was caught up in the excitement and just blurted out, "La La Land." I don't blame Faye or Warren for this. This was the fault of two entities: whoever was in charge of the design of the winning card (Was it really a design? C'mon), and the unfortunate person who handed them the wrong envelope. A clearly designed card and envelope (don't even get me started on that gold on red envelope) would've prevented this. The blogger, Benjamin Bannister (a creative consultant for old and new media), adds that there were essentially three things wrong with the card in question: Oscars logo need not to be at the top of the card. The category, "Best Acress" was at the bottom, and in small print. And, the winner's name, the main thing that should be read, is the same size as the second line and given equal weight.

Long-time Slashdot reader Toe, The sums up what he learned from freeCodeCamp's Quincy Larson: "Before you travel internationally, wipe your phone or bring/rent/buy a clean one." Larson's article is titled "I'll never bring my phone on an international flight again. Neither should you." All the security in the world can't save you if someone has physical possession of your phone or laptop, and can intimidate you into giving up your password... Companies like Elcomsoft make 'forensic software' that can suck down all your photos, contacts -- even passwords for your email and social media accounts -- in a matter of minutes.... If we do nothing to resist, pretty soon everyone will have to unlock their phone and hand it over to a customs agent while they're getting their passport swiped... And with this single new procedure, all the hard work that Apple and Google have invested in encrypting the data on your phone -- and fighting for your privacy in court -- will be a completely moot point.
The article warns Americans that their constitutional protections don't apply because "the U.S. border isn't technically the U.S.," calling it "a sort of legal no-man's-land. You have very few rights there." Larson points out this also affects Canadians, but argues that "You can't hand over a device that you don't have."

Programmer and teacher Bill Sourour wrote a post last week called "Code I'm Still Ashamed Of," where he recounts a story in which he was hired to write code for a pharmaceutical company. Little did he know at the time, he was being "duped into helping the company skirt drug advertising laws in order to persuade young women to take a particular drug," recaps Business Insider. "He later found out the drug was known to worsen depression and at least one young woman committed suicide while taking it." Sourour was inspired to write the post after viewing a talk by Robert Martin, called "The Future of Programming," who argues that software developers need to figure out how to self-regulate themselves quickly as software becomes increasingly prevalent in many people's lives. Business Insider reports: "Let's decide what it means to be a programmer," Martin says in the video. "Civilization depends on us. Civilization doesn't understand this yet." His point is that in today's world, everything we do like buying things, making a phone call, driving cars, flying in planes, involves software. And dozens of people have already been killed by faulty software in cars, while hundreds of people have been killed from faulty software during air travel. "We are killing people," Martin says. "We did not get into this business to kill people. And this is only getting worse." Martin finished with a fire-and-brimstone call to action in which he warned that one day, some software developer will do something that will cause a disaster that kills tens of thousands of people. But Sourour points out that it's not just about accidentally killing people or deliberately polluting the air. Software has already been used by Wall Street firms to manipulate stock quotes. "This could not happen without some shady code that creates fake orders," Sourour says. We'd like to ask what your thoughts are on Sourour's post and whether or not you've ever had a similar experience. Have you ever felt ashamed of your code?

Reader mikejuk writes: Coursera has announced that 30 June is the date when it will shut down the servers hosting courses that were the first, free, offerings on its platform. The new model isn't just a revised interface, it is also a new monetization model, and presumably the decision to throw out all the original free content, by shutting the platform, is motivated by greedy commercialism. You could say that the golden age of the MOOC (a course of study made available over the Internet without charge to a very large number of people) is over with the early enthusiastic pioneers doing it because they were passionate about their subject and teaching it being replaced by a bunch of "lets teach a course because it's good for my career and ego" with subjects being selected by what will sell.
Closing down the old platform is an unnecessary destruction of irreplaceable content. Coursera needs to rethink this policy that goes against everything it originally stood for. The courses affected are from the early days of the MOOC that are likely to be important in the history of their subject. The most relevant for us, but far from the only one, is Geoffrey Hinton's Neural Networks for Machine Learning which gave a "deep" insight into the way he thinks and how neural networks work.
Something has to be done to preserve this important record -- they don't have to turn off the servers just because they have a new platform.Dhawal Shah, founder of Class Central has written about ways one can download Coursera's courses before they're gone.

theodp writes: Yes, folks, there are blind programmers. There's Ed Summers, for one, who lost his vision at age 30 and now ghostblogs for Willie the Seeing Eye Dog. And if you've ever wondered how the blind can code, Florian Beijers, who has been blind since birth, explains that all he needs is a normal Dell Inspiron 15r SE notebook and his trusty open source NVDA screen reader software, and he's good-to-go. "This is really all the adaptation a blind computer user needs," Beijers adds, but he does ask one small favor: "If you're writing the next big application, with a stunning UI and a great workflow, I humbly ask you to consider accessibility as part of the equation. In this day and age, there's really no reason not to use the UI toolkits available."