The idea that once our code is working, we are good to go is a very bad idea. An idea that needs to be reevaluated and analyzed. When you buy a car, it works at first, and then it begins to develop faults. Do you have to wait for the car to develop faults before you begin maintaining it? Well, the answer is obvious and the answer is NO.
But why then do we have to do the same thing to our code. Once a piece of code works or passes that test, we close that code and never ever look back. Even the car at Toyota passed the test before it was delivered to the client, but it also has to be maintained. Some people would argue that code maintenance is far more different from maintaining a car, but I would beg to differ. What is maintained in whatever form is better than what is never maintained?
Continue reading “Code Maintenance”
With nowadays virtualization technologies, low latency communications, CPU Power and The Cloud, the Infrastructure paradigm is being changed from the static old-fashion way of managing servers to a new standard automation way of deploying services.
Continue reading “Documentation as Code”
An introduction to microservices through a complete example
Today I want to talk about the demo we presented @ OpenShift Container Platform Roadshow in Milan & Rome last week.
The demo was based on JBoss team’s great work available on this repo:
Continue reading “The CoolStore Microservices Example: DevOps and OpenShift”
Your functions must be small, very small. The number of lines a function take should be small enough so the main concept of the function is understood without having to go too far. Beyond having functions that are small, they should do only one thing and one thing alone, and they should do it very well.
Continue reading “Writing Sleek Functions”
Everything around us has a name, I mean everything, otherwise, how would we be able to refer to them, particularly in programming. From our project name, directories, variables, and more, a name must be associated with every item or else we lose their meaning and use.
Continue reading “Naming Matters”
As every developer knows, debugging an application can be difficult and often enough you spend as much or more time debugging an application as originally writing it. Every programmer develops their collection of tools and techniques. Traditionally these have included full-fledged debuggers, instrumentation of the code, and tracing and logging. Each of these has their particular strengths and weaknesses.
Continue reading “Programmatic Debugging: Part 1 the challenge”