Open Thinkering

Menu

Weeknote 25/2020

This was my last working week at Moodle. I have a few weeks of holiday to take as I ease back into full-time consultancy through We Are Open Co-op.

Quick overview of MoodleNet v1.0 beta

I repeat how proud I am of what the very talented part-time MoodleNet team achieved under often difficult circumstances. Check out my previous two weeknotes for further details:

If you’re looking for some talnted developers, I suggest you get in touch with Mayel de Borniol, Ivan Minutillo, Karen Kleinbauerů, and James Laver who may have capacity for your project. In addition, it’s worth enquiring about the availability of Alessandro Giansanti, Katerina Papadopoulou and Antonis Kalou who are equally talented, and have been working on a part-time basis for Moodle and Moodle Partners. It’s been a pleasure and privilege working with all of them, and it was great to sign off on Friday by sharing a virtual drink. We’ll all be staying in touch!

I do, of course, wish Moodle all the very best for the future and am grateful for some of the people I have met and experiences I have had over the past two and a half years.


No Drama Llama

In addition to handover documentation for Moodle, this week I’ve been doing a small amount of work through the co-op with the Greenpeace Planet 4 team, and a lot with UpRising. For the latter, I ran a couple of workshops on Google Classroom, as well as a troubleshooting session as they pivot their offline offerings to online provision.

As a co-op, we’ve been discussing how to update our website. There’s a tension between representing ourselves ‘corporately’ and representing ourselves as being made up of individual members, some of which are quite different from one another. Ultimately, 95% of our work comes through clients knowing us as people first and foremost, so really the website is a sense-check or something for our contacts to pass on to others in their organisation.

I’ve put together a couple of proposal for prospective clients this week. It’s nice to see that people are finally recognising that working online is just as valuable, and just as hard work, as doing so offline.


Last weekend I came across #100DaysToOffload which I started addressing immediately with three posts over the past few days:

I’m looking forward to writing more next week. It’s quite nice to have permission not to necessarily have to produce your ‘best’ work, but rather to bash out thoughts and just share them with the world.

For Thought Shrapnel, I put together:

You can subscribe to the weekly newsletter, which goes out every Sunday, here.


Next week, I’ll be doing more work with Greenpeace, UpRising, and the 10 charities we’re supporting with funding from the Social Mobility Commission and Catalyst. I’ll also be doing some business development for the co-op, and get back involved in the wider CoTech network.

We’ve booked a holiday in early August in a basic holiday cottage owned by friends of my in-laws in Devon. We’ve stayed there a couple of times before and it’s the perfect place to choose to switch off and spend time away from the drama and frantic pace of recent weeks. I can’t wait!

Finally, a very happy Fathers Day to my dad, Keith Belshaw. I’m delighted that he’s safe and well, and actually fitter now than before the lockdown started! It was great to see both of my parents yesterday during a socially-distanced visit to their back garden which, as ever, was blooming with flora and fauna.


Header image of my favourite tree in Bluebell Wood, near where I live in Morpeth, England.

Managing projects is about understanding context

Agile is a verb, not a noun

Ah… projects. There are some people who believe that the One True Way is Agile™. And by that they mean agile development frameworks such as SAFe and RAD and ASD and other awkward acronyms. At least for the kind of work I do with my co-op colleagues, those people are wrong.

The main thrust of the Agile Manifesto is that ‘agile’ is a verb rather than a noun. You don’t “do” agile, you work in an agile way. The difference is important.

Just as a recap, or perhaps for those who haven’t seen this before, here are the twelve principles of agile software from almost 20 years ago:

  1. Our highest priority is to satisfy the customer
    through early and continuous delivery
    of valuable software.
  2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
  3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  4. Business people and developers must work together daily throughout the project.
  5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  7. Working software is the primary measure of progress.
  8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  9. Continuous attention to technical excellence and good design enhances agility.
  10. Simplicity–the art of maximizing the amount of work not done–is essential.
  11. The best architectures, requirements, and designs emerge from self-organizing teams.
  12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

For me, the five bits that tend to leap out at me are those I’ve highlighted above. I believe agile methodologies can be applied to almost everything, so stripping out the references to software, focusing on the parts I’ve highlighted, and doing a bit of rewriting gives:

  • Simplify
  • Establish a sustainable pace
  • Build projects around motivated individuals
  • Create self-organising teams
  • Welcome changes based on feedback the audience you’re targeting

I have little time for people who try and impose a particular approach without understanding the context they’re entering into. Instead, and although it may take longer, co-creating an agile approach to the problem you’re tackling is a much better solution.

So, in summary, investing in people who work within a particular context, while being informed by what has worked elsewhere is absolutely the best approach. At least in my experience. But the best of luck to those who think that Industry Best Practices® and blunt implementations of complicated frameworks are going to save them.

I’ll be watching with my co-op colleagues, eating popcorn, getting ready for the inevitable call or email to help. And, you know what? We’ll be happy to.


This post is day three of my #100DaysToOffload challenge. Want to get involved? Find out more at 100daystooffload.com


Header image by Christopher Paul High

Practice what you preach

I spend a lot of time looking at screens and interacting with other people in a mediated way through digital technologies. That’s why it’s important to continually review the means by which I communicate with others, either synchronously (e.g. through a chat app or video conference software) or asynchronously (e.g. via email or this blog).

When I started following a bunch of people who are using the #100DaysToOffload hashtag, some of them followed me back:



@dajbelshaw you have a really beautiful site that doesn't open for me. First it's not compatible with LibreJs and then uMatrix block Cloudflare's ajax and you'll not get further than loading screen.

I know that some people are quite hardcore about not loading JavaScript for privacy reasons, but I didn’t know what ‘LibreJs’ was. Although uMatrix rang a bell, I thought it would be a good opportunity to find out more.


It turns out LibreJS is a browser extension maintained by the GNU project:

GNU LibreJS aims to address the JavaScript problem described in Richard Stallman’s article The JavaScript Trap. LibreJS is a free add-on for GNU IceCat and other Mozilla-based browsers. It blocks nonfree nontrivial JavaScript while allowing JavaScript that is free and/or trivial.

Meanwhile uMatrix seems to be another browser extension that adds a kind of ‘firewall’ to page loading:

Point & click to forbid/allow any class of requests made by your browser. Use it to block scripts, iframes, ads, facebook, etc.

Meanwhile, the extensions that I use when browsing the web to maintain some semblance of privacy, and to block annoying advertising, are:


So just running the tools I use on my own site leads to the following:

Privacy Badger found 18 potential trackers on dougbelshaw.com:

web.archive.org
ajax.cloudflare.com
assets.digitalclimatestrike.net
www.google-analytics.com
docs.google.com
play.google.com
lh3.googleusercontent.com
lh4.googleusercontent.com
lh5.googleusercontent.com
lh6.googleusercontent.com
licensebuttons.net
www.loom.com
public-api.wordpress.com
pixel.wp.com
s0.wp.com
s1.wp.com
stats.wp.com
widgets.wp.com

Disconnect produced a graph which shows the scale of the problem:

Graph produced by Disconnect showing trackers for dougbelshwa.com

This was the output from uBlock Origin:

Output from uBlock Origin for dougbelshaw.com

It’s entirely possible to make a blog that involves no JavaScript or trackers. It’s just that, to also make it look nice, you have to do some additional work.

I’m going to start the process of removing as many of these trackers as I can from my blog. It’s really is insidious how additional functionality and ease-of-use for blog owners adds to the tracking burden for those reading their output.

Recently, I embedded a Google Slides deck in a weeknote I wrote. I’m genuinely shocked at how many trackers just including that embed added to my blog: 84! Suffice to say that I’ve replaced it with an archive.org embed.

I was surprised to see the Privacy Badger was reporting tracking by Facebook and Pinterest. I’m particularly hostile to Facebook services, and don’t use any of them (including WhatsApp and Instagram). Upon further investigation, it turns out that even if you have ‘share to X’ buttons turned off, Jetpack still allows social networks to phone home. So that’s gone, too.


There’s still work to be done here, including a new theme that doesn’t include Google Fonts. I’m also a bit baffled by what’s using Google Analytics, and I’ll need to stop using Cloudflare as a CDN.

But, as ever, it’s a work in progress and, as Antoine de Saint-Exupéry famously said, “Perfection is achieved when there is nothing left to take away.”


This post is day two of my #100DaysToOffload challenge. Want to get involved? Find out more at 100daystooffload.com


Header image by Gordon Johnson

css.php