It’s a curious thing how many developers - and other people in the ICT industry - have a problem with change.

Think about it.

As business software developers, if we do our jobs well, we end up making fundamental changes to the way that other people do their jobs. After all, no-one in their right mind is going to pay for a development team to spend a couple of years developing new software if the business is going to be unaffected by delivery.

If the business of software is enabling change (and it most certainly is) then surely we need to be open to change ourselves.

With a seemingly never ending flood of new frameworks, tools, techniques, languages, methodologies and security vulnerabilities, the list of things we need to learn is practically never ending.

The simple reality is that change is about the only constant in the ICT industry.

We can try to stand against the flood, continuing to do things the way we always have - and run risk of becoming both bored and obsolete - or we can embrace change, be engaged and stay current.

I know which sounds more fun to me - what about you.


blog comments powered by Disqus
Next Post
Cryptic Error Codes  04 Apr 2015
Prior Post
Beta release of the Document.Factory  01 Mar 2015
Related Posts
Browsers and WSL  31 Mar 2024
Factory methods and functions  05 Mar 2023
Using Constructors  27 Feb 2023
An Inconvenient API  18 Feb 2023
Method Archetypes  11 Sep 2022
A bash puzzle, solved  02 Jul 2022
A bash puzzle  25 Jun 2022
Improve your troubleshooting by aggregating errors  11 Jun 2022
Improve your troubleshooting by wrapping errors  28 May 2022
Keep your promises  14 May 2022
March 2015