Ko-fi

Showing posts with label professional. Show all posts
Showing posts with label professional. Show all posts

Wednesday, 27 March 2019

Is your code eco-friendly?

Do you realise that poorly written software is a contributor to global warming?

Although I have absolutely no data to base this on, please, read on... I assure you that you will not only conclude that this is a true statement; if you code, you may even feel compelled to write better code. If that's not enough of a hook, I will introduce to and encourage you to use, this hashtag in your code reviews:


#cowfart

Let me set the scene...


There's a lot of software out there, running on billions of devices across the globe, and sadly, a lot of that code is not optimised.

Back in the day when we wrote in assembler on tiny 8-bit computers we would count clock cycles (honestly; it wasn't just me!) and refactor, refactor, refactor... until we got the best oomph out of the CPU that we could.

As if by magic, computers started popping up everywhere and hardware started to get really fast. And cheap. Suddenly, it was not about clock cycles. It was all about time-to-market. Get the code cut fast, get it released, and if it didn't run very well, upgrade the hardware!

It really was that simple for a long time; certainly for most business software anyway. Games, well that's different because if you have lag... you suck. Well, your game does, and it won't sell. In business software, having things take a while isn't necessarily a problem... more time at the water cooler, more time to do all the admin things.

Sidenote: I would encourage every budding programmer, and even seasoned programmers, who have only worked in business application development, to do some games programming. The techniques you will learn in order to survive out there are transformational.

Technology has moved along at a rapid pace. Astonishingly fast, and astonishingly cheap. And the world, largely, depends on it being that way.

The plot thickens...


Thing is, we've got big problems out there.

With climate.

Okay, not just with climate; other big problems are available.

You don't have to just believe in it anymore either; it's fact, evidenced in the starkest possible ways.

We take a tangent...


Before we get back to my main point, I did promise you a cool hashtag to use in code reviews.


#cowfart

Why? Well, because it is believed that cows are a significant contributor to global warming because there are a lot of cows out there. And they fart. Quite a lot actually. There are many articles and research studies about it.



Okay, okay... cows fart, hardware got better, people stopped counting clock cycles, and released products faster... get to the point already!

So, here's the thing...


If you write sloppy code that does not perform as well as it could, it will take longer to execute. If it takes longer to execute, or if it requires additional processing power just to make it run, you are using more hardware, more electricity, and creating more heat. On a single PC, meh... what's the difference, right? Time to hit the water cooler.

If you scale that up to run on billions of devices across the planet, well... that's a staggering amount of electricity, time, and heat being wasted by your code.

Although your code might not get to be in the next kernel of Linux, Windows, Android, or some other place like Facebook, where it might be executed trillions of times, that's not a good reason to write sloppy code.

Always write the best code you can, and educate yourself on performance tuning.

The end is nigh...


And so, without further ado, next time you review some code or give yourself a TODO:, and see code that you know the could be better performing...

do the polar bears a solid...
keep some habitat for the bees...
think of the children...

Won't somebody please think of the children?

And, as a fun way to say "Hey, this bit of code you wrote. It sucks. It might work, it might even read like a poem. Thing is, it could perform much better. So sort it out."... just put #cowfart in there.

Because the planet's worth it.

Fin.

Tuesday, 22 January 2019

Is RPA the next Y2K?

RPA.

It's a big deal.

For the unaware, the tech industry has created another acronym (because it's our speciality), and this one means "Robotic Process Automation".

What a fabulous name! Sadly it's not as exciting as it sounds. It has nothing to do with interesting devices running around being really helpful, making things, picking things up over here and putting them back down again over there for us, bringing coffee, and generally keeping humanity amused, lazy, or unemployed... or, better still, out of actual danger, doing things we perhaps don't want to do, or shouldn't do, or just can't do safely. Such as vacuuming. That ticks enough of the boxes.

No. This RPA stuff is usually all about providing a life support system to tech that's been around an awfully long time and wrapping it in products and services, almost as a life hack. It's essentially about glueing legacy systems together or hooking them up to contemporary systems, and automating tasks such as data movement between them, simulating system usage, and, well, removing the tedium of an operator which carries the benefit or reducing human error (now you can blame the machine) and doing it much faster and more efficiently than was possible before (now when it screws up, it does it at unprecedented speeds), and generally speaking, license fees tend to be cheaper than salaries. This is not an exhaustive list of reasons businesses are looking to RPA to gain competitive advantage; just some of the key ones.

So there's a lot going for it. Really, there is. And I do advocate using RPA in the right place. What business doesn't want to do more, do it faster, and do it cheaper? Outside of public transport businesses anyway (wait, did I write that out loud?!)



Here's the thing...

It's a timebomb waiting to happen.



Wait, what!? That's a strong statement.

Yeah. Perhaps.

Remember Y2K? Remember how the world was going to end because of all the systems that didn't know how to calculate 1 + 99 = 2000? It was apocalyptic scale mass hysteria. For real. To us human types, 1 + 99 = 2000 was unbelievably obvious.

There was an awful lot of checking, patching, and subsequent testing needed to refactor lots of systems to persuade them that 1 + 99, was, in fact, 2000, and not 100. Or 0. Or 1. That would just be silly.

As a result, there were an awful lot of people coming out of retirement to hit the contract market in programming languages, operating systems, and systems, where there simply wasn't the knowledge in the contemporary workforce to deal with the situation. Why? Because the world moved on. And the systems didn't. It's pretty much that simple.

So RPA is, to all intents and purposes, an enabler for forming exactly this situation. A permission slip at least; because the root causes of the problems that your RPA projects are looking to get around likely aren't getting fixed.

Rewind a moment... I used a really important word back there - refactor. So important in fact, I rather fancied using bold italics this time around.

That's the right way of fixing whatever problem you're trying to overcome by using RPA. Most people will associate "refactoring" purely with coding; altering your code to be better and evolve it as better design patterns emerge, or a more performant way of doing a thing is figured out, or new language constructs are developed. In this context though, it's also your business processes, and beyond, that likely need refactoring.

So go ahead, use RPA. Absolutely. I give it a thumbs up.

Don't do just RPA though. If you do that you are building up your technical debt (and all debts become due sooner or later!) and also your process debt; stifling the very business you're trying to improve.

So if you're employing the use of RPA, you need to look at the core reason you're using it and refactor your business model, your business processes, the technical architecture it's all built upon, your data, your interactions... everything.

Whatever you're trying to hide away or ignore with RPA, bring it out. Look at it. Examine it. Understand it. Diligently.

Get a continuous improvement team together to own what good looks like. Empower them to pull in key stakeholders, and to go do all the right things - not just the cheap things.

Your business will thank you for it, your employees will thank you for it, and crucially, your customers will thank you for it. And so will your balance sheet.

So don't let your RPA become your BAU or you'll create your own Y2K and become RIP.

And that, frankly, is just too many acronyms.

Saturday, 19 January 2019

Why I stopped writing LinkedIn articles

Last year I started writing LinkedIn articles.

I'm not really sure why I hadn't started years ago, because I like to write. Well, I say that; really I think what I like, is sharing my thoughts with anybody that will listen. Or read.

I managed the grand total of maybe three or four articles before stopping. Which, let's face it, is not very impressive. Almost tragic even! Not almost. It is tragic.

There are a few reasons I stopped, and here they are in no particular order of importance...

  • I was hugely disappointed by the way an article got significantly less traffic than a regular post... to be fair, it could just be that nobody was interested in my articles - and that's okay. I did a little digging, and it seemed I wasn't alone - so yeah, that bugged me.


  • The fact that there are "articles" and "posts" is a little silly. I fully understand the difference, and the intended use of each. Nevertheless, just have "posts", like every other platform. Some will be one-liners or re-posts, others will be full-fledged ramblings. I don't start my car with one key to do a short journey, and another to do a long journey - that would be an absurd customer experience don't you think? What happens if I use the short journey key, and as I go down the road, realise I want to do a long journey. I've got to pull over, change keys, and go again... that's even more absurd.


  • You can spend a long time researching, writing, editing, and all that jazz, and there is no way to monetize your efforts. Being able to would be nice. Personally, it's not why I write. It would, of course, be a happy outcome though, even if it wasn't raw cash and took the form of credits towards a "Freemium" account. If monetization is a thing... well, it's well hidden, and if it is a well-hidden secret, or an opportunity open to a select few, well, that's nonsense in itself.


  • I get annoyed with the annoying number of clicks it takes to get to the article writing bits. I can write a "post" very easily, and yet getting to my draft articles is just that bit more annoying than it ought to be because it should not be annoying in any way whatsoever.


So there we have it, I no longer write LinkedIn articles.

I do however continue to digitise my thoughts and do my bit to fill the Internet with stuff and nonsense, and the occasional very professional view of the world. I just choose to do it in something else, where I will, as the fancy takes me, share on LinkedIn... as a post.