Comparing output

I recently looked at someone’s GitHub account because I saw that they had recently been sponsored by someone I follow on BlueSky.

Their GitHub account (https://github.com/shuuji3) is very impressive, and I believe that this developer is worthy of the sponsorship they receive. They have been working on documentation for several large projects, made over 1,475 commits in the past year, and contributed to Elk, the Mastodon client.

It’s all really impressive and did make me think: how do they find the time to do all this? Then I easily fall into the trap of comparing my GitHub output with theirs.

It’s easily done, especially now with GitHub being such a big part of the web industry. But does it show a true picture of how someone works or the type of work they have done? And should we really compare our output with someone else’s?

Is working from home working

Today, I came across a news story that caught my attention. It mentioned the ex-head of ASDA claiming that working from home isn’t “proper” working and is causing a decline in productivity. I have to say, I strongly disagree with this perspective.

For me, working from home has been a game-changer in terms of productivity. Let me paint you a picture: Instead of standing on a freezing cold train platform for 15 minutes (or longer if the train is delayed), I can start my day feeling fresh and ready to tackle my tasks. Train operators, who certainly don’t work from home, often fail to deliver on time, which in itself contradicts the argument that physical presence equals productivity. And the experience doesn’t get better once the train arrives. Imagine standing in a packed train, overheating from the stifling heat, only to rush onto the tube and squeeze into another packed train for another 30 minutes. By the time I would reach the office, my energy is already drained—and I haven’t even started working yet.

This isn’t just about convenience; it’s about efficiency. The time saved on commuting can be invested in meaningful work or even in personal well-being, which ultimately boosts productivity. I believe the issue here isn’t that working from home isn’t working. Rather, it’s that some people are still clinging to outdated ideas of what “work” should look like. For decades, we’ve been conditioned to believe that being productive means traveling into the same building, having endless meetings about work, and then heading home only to repeat the cycle the next day. But the world is changing, and so are the ways we work.

I’d be willing to bet that the ex-boss of ASDA never had to endure the kind of commutes I’ve described or tried to code an application while six colleagues stood nearby having an unrelated meeting. If they had, they might see the value in remote work. Working from home is new for many people, but that doesn’t mean it’s ineffective. In fact, it works remarkably well for certain types of jobs and individuals.

The key takeaway here is that we shouldn’t dismiss working from home just because it’s different from traditional office work. Instead, we should embrace this shift and recognize that productivity isn’t about where you work but how you work. Remote work isn’t a one-size-fits-all solution, but for many people and industries, it’s a powerful way to achieve better results and a healthier work-life balance. The real challenge is for leaders to adapt to this new normal and support their teams in finding what works best for them.

AI and the web developer

With AI becoming more and more prevalent in the world, as web developers we need to think about the effect it has on our work.

How the type of projects we will be working on going forward will incorporate AI, not only in the tools we use (things like CoPilot) but also the new projects we build will probably have some aspect of AI in them.

This means as front end developers we need to start understanding AI, how it works, the available APIs out there that we might need to implement within a new project.

So will AI take over all front end development roles? Probably not, but will we need to know how to work with it? Yes.

For me I’m excited about the opportunity. APIs like Googles Gemini look good and there’s plenty more out there. I’ve been lucky enough to work on a couple of projects that use AI in some capacity, and I’m looking forward to doing more projects like this.

Trying microblogging

I’ve been reading a few sites where they use Microblogging (which is short form blog posts). The main sites I’ve been checking out are https://softwarecrafts.co.uk/100-words and Andy’s 100 words a day challenge that he set himself last year, and the other site is https://dbushell.com/blog/ where David has both long form notes and also micro blogging.

I’m not sure I’ll be able to stick to writing 100 words a day like Andy, but short blog posts about Angular, web development and freelancing seems like a good idea.