§ Brilliant. Autoprefixer will parse your CSS and prefix properties based on the Can I Use database:
autoprefixer.compile(css, ["last 1 version", "> 1%", "ie 8", "ie 7"]);
§ Leif Singer:
“If you get the workflow right, the user interface will follow.” #icse13 #pixar
§ The new Google Maps has some seriously well thought out interaction design. Kodus. Also cards. Cards are the new flat.
§ Dumbsto.re, the app store for dumbphones.
§ Wikipedia has a list of common misconceptions: read, memorize, and you too can be the most obnoxious person at the party.
§ Sponsored Content Pretty Fucking Awesome:
Not only am I excited to read it, but it makes me think that—because the editorial content on my website of choice appeals to me—I would probably really enjoy the brand trying to associate itself with it. I mean, they’re working together, after all!
§ Nobody expects the OOM! Google I/O 2013 – A Trip Down Memory Lane with Gmail and DevTools.
§ Promises are coming to the DOM. Except they’ll be disguised as Futures so you won’t confuse them with Deferred. Read all about it.
§ Fetch: a living standard describing how browsers fetch resources over HTTP.
§ Sweating the little details: 53 on how they designed the zoom interactions for Paper.
§ The Silver Pill:
There are two outputs of everything we write: some code, and a new version of ourselves. If we stop thinking of our product as the code, and focus also on improving ourselves with everything we write, then we increase our own productivity in all future code. Then our abilities grow with compound interest.
§ Ben Bleikamp:
The easiest way to vertically center something in CSS is to close your laptop and go to the bar.
§ Fish shell goes 2.0.
§ Source Code Typography:
This sort of “code formatting” isn’t about correctness, it’s about aesthetics, all in aid of making the code easier to read. Typography doesn’t address what should be written but rather how it should be presented to make what was written as readable as possible.
§ How We Built eBay’s First Node.js Application.
§ What’s the shrewdest, smartest maneuver you’ve ever seen in business?.
§ Typographic Design Patterns And Current Practices (2013 Edition).
§ Using Node.js for OS X services.
§ Not dead yet. Email as an Interface, or as Gmail calls it, “actions in the inbox”.
§ I Don’t Want Your Fucking App.
§ AWS Redshift: How Amazon Changed The Game.
Having vanilla SQL along with a familiar data model, and the added speed of a system built for these types of queries is probably justification enough to pick this over Hadoop+Hive if BI is what you’re after. The hosted/as-a-service aspect is just frosting on the cake at that point.
§ Free coffee, next exit:
No, your solution doesn’t have to be simple or obvious. But the story about what it accomplishes does.
§ Here’s Why I Don’t Read Your Resume:
What matters is the public persona that you have full control over. No disappointing job or office politics or bad manager is preventing you from contributing out in the world.
§ Looks like Web components are the new single-page app MVC frameworks. Here’s Polymer is a new type of library for the web, built on top of Web Components.
§ An interesting option for debugging Node.js and Chrome applications, from Adobe. Yes, I did just say that.
OH: “there are no side effects from knowing haskell”
§ Yes, you can send server-side events to Google Analytics.
§ The real issue is not skeuomorphism: Tail wagging:
The reality is that skeuomorphism enshrines and validates a failure of vision, and even worse, a failure to capitalise on the medium. That’s a betrayal of a designer’s implicit duty of trust to make something that is the best, and to treat all other goals as secondary. I think that’s a responsibility that Ive feels very strongly. I doubt that anyone has ever had to remind him of it.
§ Everyone needs to have this at the top of their backlog — Dan Williams:
As a user, I would like to use the back button in my browser
§ Two Models of Computation: or, Why I’m Switching Trains:
I used to say at interviews that my best skill was holding the whole system in my head. Now I recognize that this was a crappy way to reason. It doesn’t scale, and I can’t pass that understanding on to others as a whole. The wiser goal is to eliminate a need to load everything into one head.
§ Insights from Hosain Rahman, Josh Reich, Heather Payne, & More at the 2013 99U Conference:
Don’t structure your team in a certain way just because everyone else does. At Simple, there are no designers, “just a bunch of people who make shit.”
§ Introduction to SEO and Content Indexing: beyond the meta keywords.
§ Peter Richardson:
These machine learning jokes write themselves. Eventually.
§ Froont — an interesting approach to responsive Web design.
§ CAP has a FAQ:
16. Have I ‘got around’ or ‘beaten’ the CAP theorem?
§ Interesting study of small vs large, open vs closed source projects:
In other words, if you’re looking for bug-free apps, look for a small open source project or a large proprietary piece of software, because those have the best chance of having few defects and high overall code quality.
§ Track Server-Side Events from Rails in Google Analytics.
§ Dale Emery:
Costs move to where they will not be borne by the people who made the decisions that created them.
§ Coding, Fast and Slow: Developers and the Psychology of Overconfidence:
But here’s where it gets interesting. Every programmer who’s been working in the real world for more than a few months has run into the problems I’m describing above.
And yet… we keep on making these just spectacularly bad estimates.
§ Using checklists for code review:
One of the ways that I avoid the pitfall of giving superficial reviews is with checklists. I have a bunch of different sets of checklists that I’ve developed and tweaked over the past few years, and for any given change, I’ll select the sections which apply.
§ VimSpeak lets you control Vim with your voice using speech recognition, so you can say “select three words” to type v3w or “change surrounding brackets to parens” to type cs.
- Write new JS in CoffeeScript.
- Use soft-tabs with a two space indent.
- Always use camelCase, never underscores.
- Use implicit parentheses when possible.
§ Case study: How effective are CDNs for mobile visitors?.
§ The Onion is a GitHubber.
§ Ode to a shipping label.
§ Common Misconceptions About Touch.
§ A Responsible Programmer:
Above anything else a responsible programmer values clarity. Not only does she value clear code, but also clear documentation, clear communication and a clear vision of where she and her project is going.
§ What you need to know about Big O and paging:
What good is an O(log2(n)) algorithm if those operations cause page faults and slow disk operations? For most relevant datasets an O(n) or even an O(n^2) algorithm, which avoids page faults, will run circles around it.
Related, the Big O cheatsheet.
§ Lisa Williams:
A scientific attitude toward one’s pursuits is a great comfort: “It doesn’t work” is a perfectly good experimental result.
§ Alastair Coote:
The new http://m.nytimes.com runs on Node, uses Coffeescript, LESS, and Redis for caching. How many hipster hacker points do we get?
§ Tools for debugging and profiling Node.js apps.
§ How to foster creativity by suggesting the worst possible idea: McDonald’s Theory:
I use a trick with co-workers when we’re trying to decide where to eat for lunch and no one has any ideas. I recommend McDonald’s.
An interesting thing happens. Everyone unanimously agrees that we can’t possibly go to McDonald’s, and better lunch suggestions emerge. Magic!
§ How to stop lying with charts.
§ Sixth Form:
Of course my password’s insecure. So would you be if people replaced you every six months.
§ Jorge Ortiz:
Conspiracy theory: Facebook open-sourced Cassandra to sabotage competing tech companies (see: Twitter, Digg, Reddit).