A browser aimed specifically at web developers. It’s got some nice features around mobile device emulation.
Jeremy KeithMaking websites. Writing books. Speaking at conferences. Living in Brighton. Working at Clearleft. Playing music. Taking photos. Answering email.
Journal 2325 Articles 64 Links 6060 Notes 2522
Tuesday, August 23rd, 2016
Tuesday, August 16th, 2016
Sick of being sick.
Monday, August 15th, 2016
Day four of man flu. Bored now.
My Olympics coverage choices are dressage and boxing. Neither appeals by themselves, but combined…
Sunday, August 14th, 2016
Watching WarGames and wondering if it’s the only Hollywood movie (so far) where machine learning saves the day.
Saturday, August 13th, 2016
Day two of man flu.
Thursday, August 11th, 2016
Wednesday, August 10th, 2016
There’s this really common use-case I’ve seen at Codebar and Homebrew Website Club, where someone is making a static site, but they just want a contact form that sends data via email. This looks like a handy third-party service to do just that. No registration required: it’s all done via the value of the
action attribute in the opening
Tuesday, August 9th, 2016
I’ve always loved Jeffrey’s writing.
Popped into @brightsausco, where an episode of Hardcore History was playing. Had a nice chat about Dan Carlin …and I got sausages.
Another dive into the archives of the www-talk mailing list. This time there are some gems about the origins of the
input element, triggered by the old
A great series of short videos from Marcy on web accessibility.
A talk from Harry on the whys and hows of refactoring CSS. He mentions the
all: initial declaration, which I don’t think I’ve come across before.
Monday, August 8th, 2016
Exploring web technologies
Last week, I had two really enjoyable experiences discussing completely opposite ends of the web technology stack.
Tuesday is Codebar day here in Brighton. Clearleft hosted it at 68 Middle Street last week. I really, really enjoy coaching at Codebar. I particularly like teaching the absolute basics of HTML and CSS. There’s something so rewarding about seeing the “a-ha!” moments when concepts click with people. I also love answering the inevitable questions that arise, like “why is it like that?”, or “how do I do this?”
Thursday was devoted to the opposite end of the spectrum. I ran a workshop at Clearleft with some developers from one of our clients. The whole day was dedicated to exploring and evaluating up-and-coming web technologies. Basically, it was a chance to geek out about all the stuff I’ve been linking to or writing about. During the workshop I ended up making a lot of use of my tagging system here on adactio.com:
- My thoughts on web components,
- Links to resources on web components,
- My posts on implementing service workers,
- Lots and lots of links to handy service worker resources,
- Links relating to performance,
- A whole bunch of accessibility links, and
- Everything I’ve linked to regarding progressive web apps.
Web components and service workers ended up at the top of the list of technologies to tackle, which was fortuitous, given my recent thoughts on comparing the two:
First of all, ask the question “who benefits from this technology?” In the case of service workers, it’s the end users. They get faster websites that handle network failure better. In the case of web components, there are no direct end-user benefits. Web components exist to make developers lives easier. That’s absolutely fine, but any developer convenience gained by the use of web components can’t come at the expense of the user—that price is too high.
The next question we usually ask when we’re evaluating a technology is “how well does it work?” Personally, I think it’s just as important to ask “how well does it fail?”
Those two questions turned out to be a good framework for the whole workshop. The question of how to evaluate technologies is something I’ve been thinking about a lot lately. I’m pretty sure it will be what my next conference talk is going to be all about.
You can read more about the structure of the workshop over on the Clearleft site. I’m looking forward to running it again sometime. But I’m equally looking forward to getting back to the basics at the next Codebar.
Adult training represents a way into coding for millions of women who never learnt when they were younger. Meetups such as those run by organisations such as Women Who Code and Codebar can introduce women to the collaborative, problem-solving world of programming.