Homebrew #11: Honestatis (Mk. II)
¶ by Rob FrieselMy eleventh homebrew is a slight variation on my ninth. In that vein Honestatis (Mk. II) is the first recipe I liked enough to make a second time:
My eleventh homebrew is a slight variation on my ninth. In that vein Honestatis (Mk. II) is the first recipe I liked enough to make a second time:
I got a little braggy about this on Twitter earlier this year… 1
Our little solar project is doing pretty well. 4376.89 kW/h total yield. Thank you, @suncommon pic.twitter.com/ewezOB8LDj
— Rob Friesel (@founddrama) June 6, 2015
is.numeric()
casts those factors to numbers by casting them to the index of each factor! Which is why it looked like I was offsetting the emissions of 91.5 gasoline-powered cars each month. Which, maybe I would if I could afford that, but I can’t so I won’t.[↩]Sara Simon, Learning Fluency:
I’m writing this piece because building software is half strategy and half improvisation, and I really do think there are ways to train in both.
Given that my own background has a lot of overlap with her story, this struck a chord with me. The diverse interests, the broad learning, the liberal arts background. You can focus on computer science (or software engineering 1) early and go as deep as possible, as fast as possible. But you’ll miss things.
But something else struck me here in Sara’s essay — something that should have been obvious to me because I have small children: that our important learning comes not in these big flashes (at least not most of the time), but in the repetition of small things. My kids do this. 2 A tiny thing gets repeated over and over again 3 until it’s mastered, and then it’s just… there. 4
Java app drama
can’t find spec variable
parse output chutzpah
“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.
Jake Archibald, If we stand still, we go backwards:
Is the web platform too big? For one person, yes. Is it a problem? No. No one can be an expert in the whole web. Surgeons aren’t experts in all types of surgery, scientists aren’t experts in all of science, web developers aren’t experts in all of web development.
In The Boring Front-end Developer, Adam Silver waxes philosophical about being the kind of front-end developer who builds useful things and then takes care of them, rather than the kind that builds shiny things and then leaves them to decay.
But boring is a click-bait word, something provocative while still being on the shy side of incendiary. We’re not really talking about boring developers; we’re talking about people with the maturity to make thoughtful decisions, to care about and grow their products and their teams. But maybe it’s more incendiary to actually describe these people as mature. 1
Understanding the critical rendering path, rendering pages in 1 second is essential reading from Luis Vieira about what’s happening in the browser after those bytes start to stream in. Combine this with Ilya Grigorik’s High Performance Browser Networking and you’re going to be one knowledgeable front-end developer. 1
Maciej Cegłowski, Web Design: The First 100 Years:
We have a space station in 2014, but it’s too embarrassing to talk about. Sometimes we send Canadians up there.
Talking about where the web came from, where people like to think it’s going, and where it’s most likely actually going.
I realize this all sounds a little grandiose. You came here to hear about media selectors, not aviation and eschatology. But you all need to pick a side.
It takes a bit to get through the whole thing, but it’s worth an uninterrupted read.
Jeff VanderMeer, Redefining Utopia and Dystopia or Post-Apoc:
And, to be honest, if I could be uploaded tomorrow into some AI version of the internet or become a nascent Mars colonist, I would reject both options as morally, ethically wrong. You cannot trash an entire planet, kill billions of organisms (often for no reason at all), and then simply take up elsewhere with no change in thinking or accountability.
Mathias Meyer’s discussion of “culture fit” works with too broad of a definition (e.g., ping-pong may be an instrument or reflection of your culture, but it isn’t culture itself) but manages to make a couple of important points. First (and most important) is the idea that relying on the “culture fit” question is usually an indication of an exclusive culture – and that you’re using it to keep out people who would disrupt the status quo. Which leads to the second critical point, that an over-reliance on that question suggests a toxic environment that is too busy being insular and self-congratulatory, at the expense of questioning its assumptions.
Meyer uses a lot of examples that involve drinking and bars, but I’d say that you should closer to the office first. How does the team engage with the work itself? With each other? When something fails, does it turn into a witch hunt? Or a learning opportunity? Are you using “culture fit” to find more people that are just like you? Or are you building an inclusive team with diverse opinions and talents?