Your Internet browsing leads to greenhouse gases (GHG) emissions

What’s the occasion for such geeky title?

Tester’s Day and Programmers Day! Best wishes to you all.

Using the celebration time, I would like to pint out the matters that bother me for some time: greenhouse gas emission, electricity consumption, ecology and the care for our planet in general.

Do you remember this old-fashioned message at the bottom of each email that we started to put in the email footer to prevent it from ruining forests? It was the time when people discovered that there is no point in using printed messages, when we can exchange them virtually.

This step pro-nature was great and changed people’s way of thinking.

A letter was no longer a hand-written piece of paper, that requires a post to be delivered, it started to be easy, quick and accessible in real-time for all internet users.

On the other hand, with the growing networks of friends, or employees in the companies we work in, the need for easy, but sometimes pointless communication, flourished and become our daily routine.

When a vintage letter was sent over to a person, it usually consisted of important news, documents or an ask for some action. Today, on our private accounts, we receive multiple email messages advertising something, informing about events we don’t need or form people we don’t know. At work, it is even worst. Sometimes I have the impression that HR departments, in their goodwill, sent multiple emails to LITERALLY everybody in the company’s mailboxes due to information about some events or actions we don’t need or don’t care about.

It wouldn’t be so bad, if it was just a matter of bothering people – we all have a SPAM folder for it.

Today though, I would like you to take a look at the completely different angle of sending out tons of spam. Electricity.

80% of the energy consumed in the world comes from fossil fuels, and CO2 accounts for the great majority of our greenhouse gas emissions. Electricity is not a magic power that runs computer – it has it’s the very concrete source in the ground – no matter if we use coal, gas or any other fuel to produce it. Where is the connection between sending emails TO ALL and electricity? Think twice.

Pointless emails are not the only sources of wasting electricity. there are web resources, such as videos, pictures, hi-tech content, that use more energy than any old website would. The more fireworks you have on your website – the more energy it consumes. The more people watch it – the more greenhouse gasses fly to the atmosphere. It is really sad, because each of us would like to be modern and hi-tech, would like to have the best websites they can and be the most influential. What we need to remember is that the price for it is high.

The same is with our modern needs – constant browsing. The more you browse – the more energy it takes. Not only at the tour end, but definitely at the end of all those poor servers, which host your favorite websites and services. I know that this is how the modern world works, but I also think that this is something that we don’t think much about. When we scroll Facebook feed – we sometimes think that it consumes (wastes) our time – not necessarily that it consumes piles of bytes and energy.

To learn more about climate change and IT impact, I encourage you to check your website’s impact on the environment, using Firefox addon – Carbonalyser. I also encourage you to write fewer emails and just in really important matters. just be kind to our Planet.

In case of any comments – go to the comment section below or stalk me on Twitter, and yes, I’ve removed my Facebook account. This is my little step.

Cheers!

Advertisements

What can you do about improving the coding when you are a test manager?

@KingaTest

The idea for this post came up recently on the quite fruitful meeting, on which it was discovered that the code quality in the project is quite good, according to tools the team is using – is impressive and looks ‘green’ 🙂

On the other hand, when we’ve analyzed the other code metrics – it turned out that the cyclomatic complexity is not so great.

If you are not familiar with the term, cyclomatic complexity is used to measure the complexity at the class or the method level. It is a quantitative measure of the number of linearly independent paths through a program’s source code. It helps to keep the code in as testable and maintainable way as possible, by indicating unnecessary complexity.

Example taken from https://craftofcoding.files.wordpress.com/2014/11/cyclo_complexity.jpg

In the project, I am thinking of, the complexity goes up, completely unnoticed. It may mean that there is no one in the project, who pays attention to the overall coding progress and its’ quality. Developers to their job, use Sonar Cube to check their recent changes and when no bugs are discovered, they are happy with the result.

https://thewarrencentre.org.au/wp-content/uploads/2017/02/must-cat-yarn-960×447.jpg

The question is – what can you do about the code quality when you are not a developer? There will be always a person, who claims that he knows better and in fact, you know nothing about the coding.

Our simple answer during the meeting was – you can check the metrics and then talk to people who can do something about the coding quality.

Is it always possible? Only in the projects where all of your code is covered by good metrics, which measure something and when your team write unit tests that test the code – not to pretend that they do 🙂

Each project is different and each is a challenge for both – developers and the testers – but every time you wish to improve the quality – it is possible.

Testing management is still quite a big unknown for me, but I still try to act like a tester but behave more like a manager.

I spend some time every day thinking of how to test differently, explore, how to x-ray the code to get more information about vulnerabilities and flaws. What helps me out? A set of tools that I use on a regular basis – they may not be always associated with testing, but I found them very useful – from a management perspective.

The first one is Jira plugin X-Ray and the second is SonarQube. I am sponsored by none of them, I just find them ok and worth to use.

X-Ray turned out to be a nitty-gritty tool when you use Jira daily. It just adds value to your work. It gives the opportunity of managing all test cases, not only the automation but the manual ones as well – all in one place, with pretty visual reports. I like it, my bosses like it, you should try it.

I’ve also discovered, that SonarQube may not necessarily be just a tool for developers, but also useful toy for the quality manager. I check Metrics and Activities tabs and look for points for improvements.

I don’t mean spotting the obvious errors or bugs – I mean rather mean hunting for vicious code in the project and implying the constant need for improvement.

If you have anything to to with the test management or quality assurance as well- I recommend this short exercise for you every day: start your working day from a short trip around different metrics – nightly builds, code coverage, cyclomatic complexity and so on. I guarantee that every day there can be a discovery that you can later address to improve the quality and stability of your product. If you tend to forget the obvious, as I do, make yourself a reminder in your calendar. It will help you structure your work and do better every day.

Managing, checking, metrics blah blah blah – “Do you fix it on your own, girl?” hahaha.

Here comes this harder part of the job – when you approach people and kindly ask for help or advice. I think that testing, managing or whatever is always about talking to people and working for the same goal – good quality. So the reports themselves or improved cyclomatic complexity won’t make your project better or worse – the point is what would you do about them and what you can achieve as a team. But this is a completely different story 🙂

If you would like to know more about tools that I use or if you have a better tool to recommend – just let me know in the comments section below or on Twitter.