Improving information technology efficiency with low-code

One of the most impactful shifts over the last decade in information technology has been the rise of low-code solutions. However, low-code and its potential impact often isn’t fully understood by everyone who could benefit from it.

One of the myths surrounding low-code is that these solutions will replace developers (wrong – but hopefully they help developers avoid lots of the tedious stuff). On the other side of that coin is the myth that these tools are pointless because you still end up needing to write code (yes, you still have to write code – but much less of it).

These myths both completely miss the power of these solutions. Low-code brings the responsibilities and influence of developers and non-developers closer together in the software development process. How?

Continue reading “Improving information technology efficiency with low-code”

Maximizing flexibility and minimizing rework in software development

Photo by Ivan Bandura

I recently wrote about why future-proofing as we generally think of it isn’t possible, and why the next best thing we can work towards is flexible software. I followed up by writing about how companies can successfully build a culture that aligns everybody to the software planning and development process, which improves how forward-looking your software might be.

Now in this third post, I want to talk about real-world, practical strategies that can help minimize how much time and effort is spent reworking software. Since we can’t actually “future-proof” anything we can’t completely eliminate rework, but we can do a few things to minimize it.

It’s important to understand that many of these principles require some extra up-front work. Just as you wouldn’t consider building a house without taking time to plan it first, you shouldn’t approach your software development without taking time for similar efforts.

Continue reading “Maximizing flexibility and minimizing rework in software development”