Use best practices like SOLID principles when converting legacy code

Legacy Code: Use Best Practices Like SOLID When Converting

Geoffrey Blogref Modernization, Opinion, Programming Leave a Comment

This blog is about converting legacy code better—using architecture already in place, SOLID principles, and best practices.

Generally speaking, not having an architectural plan set up (or not using SOLID principles and best practices) can lead to passing the buck to the next generation of developers. We should all strive to push good code forward to get the latest and greatest out there. Starting with following the patterns in place at your job, or SOLID best practices, will make converting and upkeep way faster in the future.

This post contains a discussion of my experience in various software team environments. Throughout them all, we show that if SOLID patterns and best practices had been followed, then time spent converting code would have been less and code upkeep would have been easier down the line.

Solid: A New Web Standard Allowing People to Control Their Own Data

Rik Scarborough Development Technologies, Programming, Security Leave a Comment

This post contains a recap of my research into the subject and an exploration of Sir Tim’s so-called new Internet – a technology called Solid. We’ll start by exploring what Solid is, and then we’ll talk about its purposes and how to use it. It’s a pretty cool technology!

So, let’s dive in. What exactly has Sir Tim Berners-Lee created?