Bulletin report (2022)
Table of contents
This report summarises the publication of the bulletin in 2022.
An attempt to draw some insights from the publication of the weekly bulletins in 2022. See also previous years:
As usual, let's start with some general numbers to frame the rest of the report. This year I'll pull in numbers from las year as well to compare.
|Number of resources read||1101||639|
|Number of resources published||306||306|
|Number of sources||33||53|
|Number of sources not used||14||27|
This year I read substantially less than previous years likely due to changing jobs. I didn't realise I added 20 new sources to my weekly routine, I should do some pruning, it's getting wild.
The numbers per week have dropped as expected although the maximum stays quite the same.
I believe all web resources should be accessible via HTTPS so whenever I find a URL using HTTP, I manualy change it to HTTPS. It turns out that some places are either not publishing in HTTPS or doing so but neglecting it (e.g. expired or untrusted certificates). This is the split of resources by either HTTP or HTTPS.
|Number of resources read using HTTPS||1088||632|
|Number of resources published using HTTPS||305||304|
|Number of resources read using HTTP||13||7|
|Number of resources published using HTTP||1||2|
Year after year some resources persist in not offering HTTPS. Patience.
My regular sources are where I find most of my readings. These are the top 10 sources and the total resources I found thanks to them. Notice that this year “webtoolsweekly” didn't make the cut and instead “family” got in.
In contrast with the top 10 sources for resources I chose for the bulletins:
The sources mostly maintain the order from 2021. Next year this will change given that I stopped using Twitter in favour of Mastodon.
Similar to 2021, I read a few articles from “softwareleadweekly” but only a couple got into the bulletin.
Another way of thinking about sources is to look at how often domains repeat. It's a weird one though given that a single domain doesn't necessarily equate to a single publisher. Good examples of this are
medium.com. In any case, see below the list of domains I read more than 4 times:
In contrast, these are the top 10 domains from resources published in the bulletin:
GitHub stays as the dominant domain which is not a surprise, most times I share an interesting tool I use their repository which is rarely not in GitHub. The rest is mostly disjoint with last year which again is what I would expect given the diversity of domains people use to publish resources.
Once I read an article I tag it with a set of tags that I think represent the topic of the article. The top 10 tags are:
And the top 10 that where published in the bulletin:
Rust stays as my main interest, tools over other kinds of resources as well and there is a noticeable shift from API to databases, SQLite in particular. Interestingly enough, my curated list of SQLite resources, Some SQLite hasn't grown faster than in 2021.
For a second year, WebAssembly doesn't show often enough in the bulletin although it has been, with Rust, my main foucus for years.
# Link rot
Link rot is the phenomenon of URLs ceasing to point to their originally targeted resource due to that resource being relocated to a new address or becoming permanently unavailable.
unavailablemeans the domain is no longer available and I couldn't find another place with the resource.
security_issuemeans there is some sort of issue with the TLS certificate, probably it's expired.
domain_changemeans the domain is no longer available but I found the resource in a new domain.
permanent_redirectmeans the resource was no longer in the expected URL but I found a different URL with the same domain.
Out of 918 (306 resources per year), 19 have been neglected with 5 no longer working at all and 5 being in question.
Although the rot is not massive, it's evidence of how naive was the idea of URLs being permanent identifiers forever. Forever is a long time.
The good news is that I recovered 9 links which are now updated in the website version of the bulletin.
In 2020 I thought I would record more information so I could answer:
- How often do I find a resource and leave it for a while to read?
- When so, how long does it take for me from finding it to reading it?
- Is there any impact on my reading habits when I'm on leave?
For a second year in a row, I haven't managed to incorporate enough information to address them. Maybe 2023 is the year?
Changing jobs has made a big impact on the bulletin. I had less time for reading or I was too tired to do so, and the context change has influenced the kind of resources I foucus on. 2021 was orbiting around data standards, API design and alike however 2022 has been about software development, distributed systems, and databases.
My personal interests, however, have remained roughly unchanged: Rust, offline-first tooling and WebAssembly.