skip to main content

All Posts, page 17

  1. Deep dive CSS: font metrics, line-height and vertical-align
    iamvdo.me

    Vincent De Oliveira:

    Line-height and vertical-align are simple CSS properties. So simple that most of us are convinced to fully understand how they work and how to use them. But it’s not. They really are complex, maybe the hardest ones, as they have a major role in the creation of one of the less-known feature of CSS: inline formatting context.

    No kidding, this stuff is complex.

  2. Openness and Longevity
    garrettdimon.com

    Garrett Dimon:

    If you’ve spent any significant time on the web, you can likely feel how a website is built from the moment you open a page. Does it load quickly? Is anything broken? Does it work well with your password manager? Is it readable? You likely make a dozen judgments in a split second.

    On the other hand, you know the moment you open a site that was built well. Everything just works. The people who built it took care with their markup and CSS to take full advantage of the power and built-in features of those languages.

    These differences aren’t arbitrary. They’re the difference between a team that embraces and understands the web with all of its quirks and a team that scoffs at it and its constraints. But when constraints disappear, so does consideration. Forward progress is important, but we should take more time to consider the digital detritus that’s left behind. Bloated web pages. Sites that barely load.

  3. HTML, CSS and our vanishing industry entry points
    rachelandrew.co.uk

    Fighting words from Rachel Andrew, defending the ease of learning HTML and CSS from scratch:

    Whether front or backend, many of us without a computer science background are here because of the ease of starting to write HTML and CSS. The magic of seeing our code do stuff on a real live webpage!

    Yes! The instantaneous feedback when editing HTML or CSS on a live webpage is, to me, one of the most important characteristics of the web as a medium. Having no layers of abstraction between creative input and final output is one of the web’s miracles.

    I might be the “old guard” but if you think I’m incapable of learning React, or another framework, and am defending my way of working because of this, please get over yourself. However, 22 year old me would have looked at those things and run away. If we make it so that you have to understand programming to even start, then we take something open and enabling, and place it back in the hands of those who are already privileged. I have plenty of fight left in me to stand up against that.

    I couldn’t agree more. It really was the ease of getting started that got me into web development, and kept me away from native app development. Easy to learn, hard to master is a wonderful trait that the web should fight to keep.

  4. Fyre

    2019 film

    Watched 30 January 2019

    I try to avoid schadenfreude as much as I can, but this was too good to pass up. Not a brilliant documentary, but seemingly does a good job of talking to the right people and painting a full picture of what happened.

  5. Paddington 2

    2017 film

    Watched 27 January 2019

    Really great, improves on the original in every way.

    Hugh Grant’s character was brilliant as the antagonist. Well written, both captivating and funny. Unlike Nicole Kidman’s character in Paddington 1, he adds to the story instead of just existing in it as an archetypal, irredeemable villain.

    I like how Paddington isn’t framed as a can-do-no-wrong saint just getting caught up in bad situations. Some scenes (like the barbershop one) show him messing up and struggling to come up with excuses instead of admitting his fault. It’s subtle, but is a nice touch that makes him more sympathetic.

    The writing and editing were once again economical and effective. Art direction was even sharper. The pop-up book fantasy scene that takes place early on stands out — it’s especially memorable and affecting, doing so much emotional work with so few ingredients.

    I can see now why this has received such high praise. It’s well deserved.

  6. A Simple Favor

    2018 film

    Watched 25 January 2019

    Kind of fun, but weird. And not weird in a good way — weird in a “not sure what it wants to be” way. It tries to be a thriller, but the plot is way too messy and clichéd to be interesting. It tries to be a comedy, but there is no real intent to the humor; just a residual layer of silliness, no courage about it. I guess this tone was intentional, but it simply did not work for me. The longer it went on, the less satisfying it became.

  7. Fyre Fraud

    2019 film

    Watched 30 January 2019

    Felt rushed and incomplete. The interview with Billy McFarland did not really add much depth, and several of the more interesting people featured in the Netflix documentary were missing altogether. The poorly-edited-in internet memes and patronizing attitude detracted from the experience and eroded the point being made. Meh.

  8. The 500-Year-Long Science Experiment
    theatlantic.com

    The human factor of keeping a science project going for 500 years seems a lot more complicated than the actual science:

    Opening vials, adding water, and counting colonies that grow from rehydrated bacteria is easy. The hard part is ensuring someone will continue doing this on schedule well into the future. The team left a USB stick with instructions, which Möller realizes is far from adequate, given how quickly digital technology becomes obsolete. They also left a hard copy, on paper. “But think about 500-year-old paper,” he says, how it would yellow and crumble. “Should we carve it in stone? Do we have to carve it in a metal plate?” But what if someone who cannot read the writing comes along and decides to take the metal plate as a cool, shiny relic, as tomb raiders once did when looting ancient tombs?

  9. Paddington

    2014 film

    Watched 24 January 2019

    I expected the charm and fuzzy feelings, but not the nuanced, topical take on immigration, delivered with the utmost efficacy. Bravo!

    It’s all very wholesome and hard to criticize, though I think it could have benefited from some more Spirited Away-style bittersweetness, and a more complex antagonist. But hey, it works.

    Sidenote: the wonderful art direction somehow reminded me of Spielberg’s Tintin and, in contrast, how much of a disappointment that was.

  10. I’m a Web Designer
    andy-bell.design

    Still on the topic of web development job titles, Andy Bell hits the nail on the head. This paragraph describes my exact problem assigning a title to myself:

    I struggled with how to place myself when I went back to freelancing last year because I’m both a designer and a developer. I toyed with “Independent Designer & Developer” which worked out alright but did make me sound like a bit of a “Jack of all trades”. I’m also technically “Full Stack”, but I won’t use that as a title because in my head, a Full Stack Developer is a back-end developer who knows a bit of client-side JavaScript and CSS.

    I tried to avoid the issue altogether and go with a short description instead of a title — “design and code for the web” is what I ended up with. But when pressed for a title, I do fall back to “front-end web developer,” which feels lamer every time I say it.

    Andy suggests “web designer.” Despite the baggage, it does seem to fit the bill. I like it. I promptly added myself to Andy’s personalsit.es directory with that as my top tag.

  11. Getting Started

    It’s 2019, and I have a blog now. This party is just getting started, right?

    I managed to cheat the system and avoid kicking things off with an empty slate; I began collecting links about a year ago, and my notes go even further back. Looking at the whole feed, it’s beginning to look like something.

    I expect to continue posting small updates frequently, but I want to turn that momentum into more substantial writing. That’s the exciting (and scary) part of this endeavor — the part I’ve always put off, with the lame excuse of not having some place on the web I could call my own.

    If you wish to make an apple pie from scratch, you must first invent the universe. It took me over a year of overcomplicating it, but I now have a universe. Apple pie forthcoming.

  12. The Great Divide
    css-tricks.com

    Chris Coyier tries to make sense of what “front-end web developer” means now, and gets to the core of why I avoid calling myself one:

    When companies post job openings for “Front-End Developer,” what are they really asking for? Assuming they actually know (lolz), the title front-end developer alone isn’t doing enough. It’s likely more helpful to know which side of the divide they need the most.

    Two “front-end web developers” can be standing right next to each other and have little, if any, skill sets in common. That’s downright bizarre to me for a job title so specific and ubiquitous. I’m sure that’s already the case with a job title like designer, but front-end web developer is a niche within a niche already.

  13. How to Fix Social Media by Injecting A Chunk of the Blogosphere
    kottke.org

    Tim Carmody:

    Most of the proper publications I’ve written for, even the net-native ones, have been dense enough to hold an atmosphere.

    And guess what? So have Twitter and Facebook. Just by enduring, those places have become places for lasting connections and friendships and career opportunities, in a way the blogosphere never was, at least for me. (Maybe this is partly a function of timing, but look: I was there.) And this means that, despite their toxicity, despite their shortcomings, despite all the promises that have gone unfulfilled, Twitter and Facebook have continued to matter in a way that blogs don’t.