About Spotted posts
No further images are included. No opinion is given. Not even a punny title. These are just… spotted. Best available link to learn more about the change (or the company) provided in the link above. Poll and comments are open.
Skip Lievsay is one of the best sound designers in the business, having won an Oscar for his work on Gravity and worked on such films as Goodfellas, Silence of the Lambs, Do The Right Thing, and all of the Coen brothers' movies. Jordan Kisner recently profiled Lievsay for The Guardian.
Tags: audio Jordan Kisner movies Skip LievsayIt is a central principle of sound editing that people hear what they are conditioned to hear, not what they are actually hearing. The sound of rain in movies? Frying bacon. Car engines revving in a chase scene? It's partly engines, but what gives it that visceral, gut-level grist is lion roars mixed in. To be excellent, a sound editor needs not just a sharp, trained ear, but also a gift for imagining what a sound could do, what someone else might hear.
Welcome to our Wednesday edition of the YUIConf 2013 video series releases. Today we feature a talk from Markandey Singh on Moonwalking with JavaScript. It’s a great talk if you are looking for tips to get your website to load and render faster. As always, you can catch up with the previous video or visit the full playlist on YouTube.
Slides and other information about this talk available on GitHub.
Don't worry about people stealing an idea. If it's original, you will have to ram it down their throats. -- Howard Aiken, as quoted in Portraits in Silicon by Robert Slater, 1987, p. 88.
Machines will do what we ask them to do and not what what we ought to ask them to do. -- Norbert Wiener, 1949, published in John Markoff, NYTimes May 21, 2013
The shortcut that's sure to work, every time: Take the long way. Do the hard work, consistently and with generosity and transparency. And then you won't waste time doing it over. -- Seth Godin, Seth's Blog, May 13, 2013.
Most people doubt online meetings can work but they somehow overlook that most in-person meetings don't work either. - Scott Berkun, The Year Without Pants, p. 42, September 2013.
It's total chaos. But out of that chaos will come some really amazing things. And right now there are amazing opportunities for young people coming into the industry to say, ‘Hey, I think I'm going to do this and there's nobody to stop me.' It's because all the gatekeepers have been killed! -- George Lucas, The Verge, June 13, 2013.
If the NSA released their heaps of prying spycode as open-source code, Silicon Valley would be all over that, instantly. They’d put a kid-friendly graphic front-end on it. They’d port it right into the cloud. -- Bruce Sterling, The Ecuadorian Library, August 3, 2013.
I believe that the purpose of death is the release of love. -- Laurie Anderson, Farewell to Lou Reed, Rolling Stone, November 21, 2013
The question [in Hollywood] used to be: How do we top ourselves? The new one seems to be: How do we stop ourselves? -- Damon Lindelof, The New Rules of Blockbuster Screenwriting, Vulture, August 14, 2013
If you take someone to lunch you just get each other's stories, but if you set up folding chairs together, you find out what people are really like. -- Anne Herbert, The Whole Earth Jamboree Wasn't Worth It Once, CoEvolution Quarterly, Winter 1978.
People are bad at looking at seeds and guessing what size tree will grow out of them. The way you'll get big ideas in, say, health care is by starting out with small ideas. If you try to do some big thing, you don't just need it to be big; you need it to be good. And it's really hard to do big and good simultaneously. So, what that means is you can either do something small and good and then gradually make it bigger, or do something big and bad and gradually make it better. And you know what? Empirically, starting big just does not work. That's the way the government does things. They do something really big that's really bad, and they think, Well, we'll make it better, and then it never gets better. -- Paul Graham, Building Fast Companies for Growth, Inc. September 2013
Simple answers from xkcd
I get all kinds of questions from readers and I love them, some of them are very challenging and some make for great blog posts. So recently I got a question from a reader looking for advice about onboarding a fairly large department to Salesforce. And while I’ve been through many deployments of Salesforce each one presents a new and different challenge. But as with each challenge- planning and communication is key. For the sake of brevity I’m going to assume that you have already met with the department, gathered requirements, built the app, and finished with user acceptance testing- meaning it’s time to train and onboard them. The goal with any deployment is a high adoption rate so let’s build our plan with that goal in mind. Build your Communication Plan The key to any deployment and onboarding project is communication. To get our roll-out on the success track
The post Salesforce Onboarding Done Right! appeared first on ButtonClick Admin.
I can’t recall the last time I did a post like the one you are about to read, in fact I may never have written a post like this before. But after hosting a couple fantastic posts about Visual Workflow I think it’s time we address the 800lb. gorilla in the room- namely Salesforce Workflow Rules and Approval processes. No doubt they were forward thinking when they were released in Salesforce, I mean functionality like this usually only comes with code. But since their release they have been left out to pasture. With the direction of Salesforce clearly pointed in a mobile direction I’m losing hope that these fabulous ButtonClick Admin friendly features will be left in the pasture- relics of an era that has been forgotten. So in one last attempt to raise awareness I’m putting together my list of improvements that I believe will help ButtonClick Admins take
The post Salesforce Workflow Rules- My Wishlist appeared first on ButtonClick Admin.
When people say “you know you are important to me” the best answer is “I don’t know.” Think about it before you answer. There’s great social pressure to say “yes, of course I know that” when asked by a parent, spouse, boss or old friend, but that pressure confuses your abstract feelings about a person with an evaluation of how they behave towards you. Feelings and actions are different things, and the fact someone feels you are important to them doesn’t guarantee they treat you well, or that they should be important to you.
Feelings and actions are different things. As important as feelings are, if they don’t influence behavior feelings have little meaning for anyone but the person having them. If I love you, but treat you horribly, or ignore you, or behave selfishly and never consider your needs in any of my actions, I’m betraying those feelings (whether I realize it or not). It’s therefore not about whether I love you or care about you, but how my behavior towards you reflects those feelings. That’s the basis for healthy relationships: a connection between feelings and behavior, or emotions and actions. All too often our actions and emotions are disconnected from each other. Either through fear, disfunction, or ignorance, our emotions never make it out of our hearts and into actions that have meaning for the people we care about most. Integrity is the proximity of your beliefs to your actions, and we need more integrity in this world.
There are similar truths in the workplace. To be told a project is important, but not to get the resources you need to do it well is a kind of lie. It’s a disconnect between the word “important” and any action that would embody importance. The person with the disconnect might not realize they are betraying themselves, but they are. Either you’re not important enough to deserve the resources and they’re deceiving you by using that word, or they are incompetent in not giving you the resources your importance merits.
It’s a low bar to ask “you know you’re important to me, right?” The better question is “does my behavior express to you how important you are?”
They say the devil is in the details, but the angels are in there too. That is, if you have a clue about what you’re doing. People who want to design things have large egos and presume that they’re skilled enough to work on large, grand ideas. But so rarely do designs in this world get the small things right, and if the small things, the little pieces that get used the most, are broken, what is the point of being large?
Dan Saffer’s book Microinteractions is the best book I’ve read about design in ages. I’ve been working in design for 20 years and often have younger designers ask me for advice, or how to achieve their grand design dreams. Most books about design are similarly grand and presume that everyone knows the basics well enough to do the little things well. The world proves this not to be true. Spend an afternoon strolling around town with a gaggle of caffeinated interaction designers and you’ll hear an endless commentary on the details the designers of the world have gotten wrong.
The book itself is a wonderfully self-consistent: it’s short, concise, well designed and brilliant. The fun and salient examples nail Saffer’s points, and his writing is sharp, incisive and with just enough comedic curmudgeonry to keep you smiling most of the way through. The book’s ambitions, like any good design project, are clear. Saffer’s focus is on the small sequences of interactions he calls, surprise, microinteractions. Ever been frustrated by entering your password? Leaving a comment on a blog? You’ve been let down by a microinteraction design. Perhaps the majority of design frustrations in the technological world are micro, not macro.
This is the book many designers will begrudgingly pick up, thinking it’s beneath them, but by the time they get to page 25 they’ll be thinking “oh, this is fun” and then by page 50 they’ll realize “oh dear, I make that mistake, or have peers that do” and when they’re finished they’ll know “I now have a language to describe these important problems that have bothered people for ages but were hard to describe, and I have the knowledge now to fix them properly”. What more can you ask for from a book about designing things?
We live in a world where the clueless have disturbing amounts of influence. There are no licenses required to use words like design, simplicity and quality, and it should be no surprise we’re often victimized by the engineered junk companies pass off as products. If we want that to change we have to start in the small. Until a designer, or an organization, can consistently get the details right, what hope is there to get the grand things right either?
Please buy this book. I say that selfishly as I want better design in the world. But I also say it generously: so many design books are fluffy affairs, lost in abstraction and ego. Saffer has hit the bullseye of problems the design world desperately needs to solve, and written a book every designer needs to read.
A free chapter is here (PDF) and the book has its own website.
In the moral realm there may be 7 deadly sins, but scalability maven Sean Hull has come up Five More Things Deadly to Scalability that when added to his earlier 5 Things That are Toxic to Scalability, make for a numerologically satisfying 10 sins again scalability:
Jake Archibald put together an interesting and informative quiz about when browsers actually make requests. I learned a bunch. Some of it might seem like quirky academic knowledge but we all know how often unpredictably weird situations come up in day to day dev work.
Jake wished me to point out that it is unfinished (only works on desktop Chrome) and might hurt your feelings if you can't take browser insult jokes.
Direct Link to Article — Permalink
Request Quest is a post from CSS-Tricks
