This is a tumblelog, kinda like a blog but with short-form, mixed-media posts with stuff I like. Scroll down a bit to start reading, or a bit more to read more about me.
Nicholas Zakas has a new (and short!) book out on Leanpub called Principles of Object-Oriented Programming in JavaScript. Remember the OOP coverage from his Professional JavaScript for Web Developers? It’s like a deep-dive version of that. Recommended.
I had the privilege of getting some early looks at this book and am glad he pulled the wraps off of it to share with everyone.
Nicholas Zakas this time. He makes it sound more like TypeScript : JavaScript :: Sass : CSS. His take is a good one, and I’m particularly keep on the point he makes when he’s talking about his “bias” — that the solution to our JavaScript problem is better education about the language, and not just more/different meta-languages on top of it.
Nicholas Zakas with a thorough run-down of the up-coming ECMAScript quasi-literals template strings.
Nicholas Zakas on some of the new/proposed ES6 syntax. Some good points all around; and I’m particularly head-nodding to his remarks re: “fat arrow” syntax.
Nicholas Zakas chases down an elusive problem with :hover selectors and unintentional double-taps on iOS.
Nicholas Zakas:
To understand the problem, consider the job of building a house. Someone has decided they want to build a house on a specific plot of land. The house is to be two stories and have a garage. There’s even a rough sketch of the front of the house scribbled down on a napkin. That person comes to you with this information and the napkin and says, “this is enough for you to start building, right?” Are you able to start building?
A bit long, and a little ranty, but a lot of excellent points in there. One bit that I did not agree with:
True priorities aren’t transient, they are static.
Priorities can and do change all the time, whether we like it or not. It’s how we manage the changing priorities that’s critical. You aren’t going to mind switching from one task to another if you understand why the switch is important, as long as you’re able to convey that the switch is a disruption and comes with a cost. (And usually that cost is “you can’t have both”.)
Nicholas C. Zakas:
Make sure your title reflects what you do. I’d like to see less “Web developer” positions and more “front-end engineer” and “UI engineer” positions. […] Titles are often negotiable because, to some, they’re meaningless. But they do have meaning insofar as it communicates your value to the company.
The slides from Nicholas Zakas’ 5/30/2012 presentation at FluentConf. In a nutshell? It’s like a companion piece to his new book, Maintainable JavaScript. And by the way, I just wrote a review of that book on my other blog.
Nicholas Zakas provides a brief overview of ECMAScript 5’s “strict mode”, and asserts that we should all be using it.
My take on strict mode remains the same: “It’s like a seat belt for your JavaScript.”
