You are trapped inside a hollow sphere. A fluorescent glowing white all around you. Except for dashes of color and black smudges. Not smudges. Text. Everywhere you turn, an R REPL follows you. And it vomits a never-ending cascade of commands. A convoluted combination of sapply and gsub. svd. plot. table and summary. plot, plot. smoothScatter. is.na. plot, plot, plot…
And that’s the thing: Flickr feels like a permanent home.
Pretty much how I've felt about it all along. (Via DF.)
:scope selector sugar yet though.)“Just give me a list of the URLs of all the scripts on this page, OK?”
For those times when you’re not sure of all the things getting loaded on the page, but you need to know those things, and you need some quick and convenient way to just get that damn list.
A proposal by the Prince George’s County Board of Education to copyright work created by staff and students for school could mean that a picture drawn by a first-grader, a lesson plan developed by a teacher or an app created by a teen would belong to the school system, not the individual.
Despicable.
However, I did take slight issue with this:
We teach responsibility, organization, manners, restraint, and foresight.
No. I teach those things to my kids; I expect you to expect me to do that teaching.
…events are essentially the only variable…
Of course that is a ton of material for 8 weeks and so obviously we will be covering just the very basics.
I wrapped up the first week of the course on Thursday (1/24). So far it has been a bit intense, but also fun. So far the format and lectures have been good, and I'm (re-)learning quite a bit. I have some stats background from college, so some of it has been review, but it has been fascinating to hear about statistics from other perspectives — I'd never really considered how an economist or biologist or engineer might use those tools. That has been very valuable.
evergreen Jasmine
Agile for the introvert
a cartoon whale mouth
“Search Term Haiku” is a series wherein I examine this site’s log files and construct one or more haiku poems from search terms and phrases that led visitors to the site. Where possible, I attempt to keep the search phrases intact. However, as these are haiku poems, I do need to follow the rules.
Or: an almost certainly incomplete but hopefully accurate enough (and succinct) front-end developer’s guide to charsets and character encoding.
Before we begin, I will summarize the problem with the following picture:
Do you see those funny diamonds with the question marks in them? That’s about the size of the problem, right there. 1 You have some text for your French-speaking customers, but without the right instructions the computers between you and your customers are too stupid to know that some series of numbers are going to need to display as a ç and not as… something unattractive.
Now, before we get in to any of the details, here’s the spoiler alert for the rest of this post: Just pay attention to the charset(s) that you use — those are the “rules” for how your computer (and every other computer) is going to convert “the numbers” into “the letters”. Remember to be explicit about which charset to use (the whole way down the line!) and hopefully you can save yourself a little embarrassment and frustration. Continue reading →
Content-Type header that specifies text/html; charset=UTF-8, but the file itself (an EJS template) is saved to disk as ISO-8859-1 (Latin-1). And TJ-only-knows what happens in the conversion process between when the route passes the model to the template and when the generated mark-up actually goes out as the body of the request. (And yes, I intentionally created the charset mis-match for illustrative purposes.)[↩]A developer never sets out with the goal of making a complete and total mess of things.
In some ways it's a bit of a "me too!" post about how to organize your stylesheets (e.g., somewhat more opinionated than SMACSS, a lot more opinionated than OOCSS) but still worth the read, even if you're feeling burned out on this kind of advice. Sande's proposal is to take a bottom-up/inside-out approach to engineering your (S)CSS and to organizing your directories and files. The key take-aways for me were: (1) the opinionated directory structure and (2) treating style.scss as a manifest for everything else. (Though the second item is hardly a new idea, talking about it as a "manifest" is certainly an elegant expression of that idea.)
There are still some unsolved problems here, but they're mostly social. ("How do I create the right traction for this work in a big organization? and/or reduce the friction for working within a big application?")
Who would have thought that an 850 word article about pedometers and walking could get you thinking about so many things?
She returns unexpectedly. Unannounced. She is laden with some package, something wrapped and concealed. A burden. She has been gone for years — almost as long as you have lived here — and not a word from her in all that time.
Your son, who was just a baby when you all found the caves and moved into them, is now old enough to have pointed questions about this stranger. Who is she? And where did she come from? Why has she come here? What is under her arm? He is nervous and scared and probably rightfully so. (He looks more like his mother now than when he was a toddler bumping his head on the cave walls.) Continue reading →
"We try to keep everything related to each other across our products and videos and marketing–they should all speak to each other," [Robert] Andersen says. "We hold each other accountable for designs that seem arbitrary at Square."
Engineering is done with numbers. Analysis without numbers is only an opinion.
It says "Spacecraft Design" but almost all of them are equally applicable to Software Design. Good advice, great list.
They're not here to be at the top of the ladder; they are here to learn to climb.
Accept-Language header — but there's something to be said for simply using your output phrases as your keys. (Although I wonder about how you would manage tokenized strings as your keys…)The Reactive Extensions library models each event as a collection of data rather than a series of callbacks. This is a revolutionary idea, because once you model an event as a collection you can transform events in much the same way you might transform in-memory collections.
I haven't watched the interview yet, nor worked through the interactive tutorial, but I'm very intrigued by this idea and want to give it a further, in-depth study.