hkuo
Joined 17 years ago
Joined 17 years ago
It's one thing to say that a design agency came in and designed a logo in a weekend. It's another thing to say an internal design team bared down to create a logo in a "weekend" (in quotes, because Marissa may simply be using the term to mean done in a short timespan).
I've worked on both the agency and client side, and the huge difference is that an agency comes in and has to learn very quickly about the client's business (more often than not getting it wrong the first time around) while the people working at the company live and breathe the company culture day in and out. At an agency, you're often jumping between a few clients, but unless you've been the agency of record for a number of years, it is simply not possible for you to have the depth of understanding that an internal marketing team will have. What an agency CAN bring is some fresh outsider thinking not colored by the company's history, but there's no reason the right people within the company can do so as well.
There's nothing but benefit for a designer to also pick up some coding skills or a developer gaining an appreciation of design and interaction. And I see no reason someone can't excel at both if they truly desire.
Perhaps the worst designers you've worked with did both, but don't let bad logic lead you to think that the best designers do not.
I'm often unsatisfied with the lowest brightness setting when in a dark room, and this solves that perfectly. I just downlaoded it right now and tried it out and it works perfectly. I'd recommend you do the same as it's free before making judgment on it.
Edit: I just saw your edit, and I think you have it incorrect. Try clicking the brightness app menu bar icon, and then use your keyboard brightness keys to adjust, and you'll see at the lowest setting, it goes to the halfway mark.
To your point about this not being in the book JavaScript the Good Parts, I re-downloaded my purchase from Oreilly to double check, and throughout the book, all functions are declared as variables. Here's a screenshot from the second page of the "Functions" chapter, which is the first time a function declaration is introduced in the book: https://dl.dropbox.com/u/1517499/Screen%20Shot%202013-03-26%...
Edit: Just an edit to add that I quickly perused the pdf and couldn't pick out anywhere where he explained why he recommends this way. In any case, I'm always open to any arguments one way or the other.
From the other commenter's SO link, I found this link to go more in depth into the differences of declaring functions, and it seems to come down to having stricter control on the order of events with no surprises.
http://javascriptweblog.wordpress.com/2010/07/06/function-de...
And here's an example of one of the surprises you'll run into if you don't declare your functions in this way: http://www.adequatelygood.com/JavaScript-Scoping-and-Hoistin...
var logit = function(x){$('body').append('<div id=logit></div>');$('#logit').css({'background':'#000','position':'fixed','bottom':0,'right':0,'color':'#fff','padding':5,'font-family':'arial','font-size':'9px','z-index':9999});$('#logit').append(x+'<br>');};
It could very easily be adjusted for non-jquery too.
Then just call it like: logit(whateverYouWantToDisplay);
My skillset lies at the intersection of user experience, visual design, and code for any form of digital media. I began my career writing code, transitioned into design, and adopted user experience soon after. Throughout, I’ve continued to learn and play all three roles in parallel in a symbiotic relationship of creativity, functionality, and execution.
http://www.henrykuo.com
LinkedIn: http://www.linkedin.com/in/hgkuo
Twitter: http://www.twitter.com/henrykuo1
Facebook: http://www.facebook.com/henrygkuo
Recent Work:
Just the First Frame - http://www.justthefirstframe.com (Design/UX/Code)
iPhoneception - http://www.iphoneception.com (Design/UX/Code)
TABASCO Nation - https://apps.facebook.com/tabasconation (Design/UX)
Cisco Together - http://together.cisco.com (Design/UX)