About the Author
Avatar photo

Geoffrey Blogref

I grew up in Wichita, Kansas, so been in Kansas all my life. I grew up on Mac, the Apple 2si was my first computer. I didn't know I wanted to do computer engineering till I was a Sophomore in high school. I was in computer apps 1 and shared a classroom with a programming class. I would fly through Excel and Word stuff and then go sit with programmers. When I saw that you could make the computer do whatever you told it... That was it, I knew that is what I wanted to do. I have a BS in Math from Wichita State, a BS in Computer Science from Emporia State, and an MS in Software Engineering from Pennsylvania State University.I have done lots of job traveling in my work experience, back and forth between contract and full-time. From being the Oracle database guy, learning Rest API, junior software architect at 2 places (I used SOLID and best practices to set up coding patterns in both places), and a team lead over 5 devs and a QA. Most of my work has been C# .NET with SQL server backend. I have been with Keyhole since February 2021Outside of work, I live my life. I have 3 kids (4, 2, and 6 months) so I have little alone time at home to code. Also, I have season tickets to the Royals and Chiefs. Yes, some years are better than others. Sitting front row in the club level for both World Series was fantastic. As well as second row, lower level at the Chiefs games. I also play on a competitive traveling softball team. We have played in Florida, Vegas, Dallas, and Minnesota.

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.