I had linked to quite a few of the articles myself already, but one I hadn't seen was from David DeSandro who wrote New tech gets chatter:
You don't hear about TextMate because TextMate is old. What would I tweet? Still using TextMate. Still good.
I think that's a very good point.
It's relatively easy to write and speak about new technologies. You're excited about them, and there's probably an eager audience who can learn from what you have to say.
It's trickier to write something insightful about a tried and trusted (perhaps even boring) technology that's been around for a while. You could maybe write little tips and tricks, but I bet your inner critic would tell you that nobody's interested in hearing about that old tech. It's boring.
The result is that what's being written about is not a reflection of what's being widely used. And that's okay ...as long as you know that's the case. But I worry that theres's a perception problem. Because of the outsize weighting of new and exciting technologies, a typical developer could feel that their skills are out of date and the technologies they're using are passé ...even if those technologies are actually in wide use.
I don't know about you, but I constantly feel like I'm behind the curve because I'm not currently using TypeScript or GraphQL or React. Those are all interesting technologies, to be sure, but the time to pick any of them up is when they solve a specific problem I'm having. Learning a new technology just to mitigate a fear of missing out isn't a scalable strategy. It's reasonable to investigate a technology because you genuinely think it's exciting; it's quite another matter to feel like you must investigate a technology in order to survive. That way lies burn-out.
I find it very grounding to talk to Drew and Rachel about the people using their Perch CMS product. These are working developers, but they are far removed from the world of tools and frameworks forged in the startup world.
In a recent (excellent) article comparing the performance of Formula One websites, Jake made this observation at the end:
However, none of the teams used any of the big modern frameworks. They're mostly Wordpress & Drupal, with a lot of jQuery. It makes me feel like I've been in a bubble in terms of the technologies that make up the bulk of the web.
I think this is very astute. I also think it's completely understandable to form ideas about what matters to developers by looking at what's being discussed on Twitter, what's being starred on Github, what's being spoken about at conferences, and what's being written about on Ev's blog. But it worries me when I see browser devrel teams focusing their efforts on what appears to be the needs of typical developers based on the amount of ink spilled and breath expelled.
I have a suspicion that there's a silent majority of developers who are working with "boring" technologies on "boring" products in "boring" industries ...you know, healthcare, government, education, and other facets of everyday life that any other industry would value more highly than Uber for dogs.
Trys wrote a great blog post called City life, where he compares his experience of doing CMS-driven agency work with his experience working at a startup in Shoreditch:
I was chatting to one of the team about my previous role. “I built two websites a month in WordPress”.
They laughed… “WordPress! Who uses that anymore?!”
Nearly a third of the web as it turns out - but maybe not on the Silicon Roundabout.
I'm not necessarily suggesting that there should be more articles and talks about older, more established technologies. Conferences in particular are supposed to give audiences a taste of what's coming—they can be a great way of quickly finding out what's exciting in the world of development. But we shouldn't feel bad if those topics don't match our day-to-day reality.
Ultimately what matters is building something—a website, a web app, whatever—that best serves end users. If that requires a new and exciting technology, that's great. But if it requires an old and boring technology, that's also great. What matters here is appropriateness.
When we're evaluating technologies for appropriateness, I hope that we will do so through the lens of what's best for users, not what we feel compelled to use based on a gnawing sense of irrelevancy driven by the perceived popularity of newer technologies.
This was originally posted on my own site.