Programming on The Techno Scholar Chronicles

Book Review: Git: Project Management for Developers and DevOps Teams

Sat, 13 Jan 2024 00:00:00 -0600

I very much enjoyed reading this book as it has helped teach me the skills I need to use Git in my professional work. The authors, in my opinion, were very thorough on the topic. They explored not just Git, but how Git can be used by developers in teams. They covered the Git commands, low-level details of how Git internally works (up to a point for basic understanding), using Git with platforms such as GitHub and GitLab (and other alternative platforms), workflows using Git in teams, using Git in real life, Git problems and solutions, etc.

Book Review: Python Microservices Development: Build, test, deploy, and scale microservices in Python

Fri, 05 May 2023 00:00:00 -0500

This book was a good read for me. It covered many aspects of developing microservices in Python that are relevant to my engineering job. Some of these aspects include developing a REST API with a web server such as Flask; writing, testing, and documenting code; interacting with other services via synchronous vs. asynchronous calls; using task or topic queues (e.g., RabbitMQ); monitoring services; securing services; packaging services; containerizing services; and deploying on AWS. The aim of the book is to provide insight and examples of how to develop a microservice by focusing on a toy application called Runnerly.

Book Review: The Legacy Code Programmer's Toolbox: Practical Skills for Developers Working with Legacy Code

Tue, 31 Jan 2023 00:00:00 -0600

I had this book sitting on my desk for a few years, recommended by a coworker. Life got busy. I decided to pick it back up and finish it! Here’s some of the insight I’ve learned from it.

The author begins by defining legacy code as code that is hard to understand, uncomfortable to change, and causes concern. Attitude plays a significant role in how we approach legacy code. There’s the natural mindset, often negative, versus the effective mindset, which is more constructive. We can choose to understand legacy code as a solution to past problems accumulated over time and recognize it as a reason we have jobs.