The image above might be rocket science, but changing how you develop programs for the public cloud isn’t!
There are many ways to successfully write code that works in Microsoft Azure, Amazon Web Services, Google Cloud Platform, or IBM Cloud. I’m not here to promote one platform over the other —so please don’t ask which one is better.
In this piece, I’ll refer to scaling vertically and horizontally. Here is a quick definition of each in case you don’t know.
At different points in your software development career, you will experience at least one, if not all, of the problems listed here. My goal is to inform you of things that could discourage you from becoming a developer, before you reach them. This will prepare you to handle them, using a plan you’ve devised with a clear mind.
Why? Because development is hard and it will take persistence to get better.
The first truth of programming is that you will fail. I do all the time. The compiler (or interpreter) is good at reminding me of my failure rate.
What it is not so good at is telling me “Good job!” when I fix those pesky bugs — I have to do that myself. Learn to appreciate the failures, small and large. Look at failed compiles and program crashes as learning experiences that make you better at what you do. If you want to be the sharpest tool in the shed, you have to find and remove the burrs! …
This article assumes you already know at least one programming language; however, the concepts here will help you get started with programming.
When I was in school, a teacher told me something I share with new developers: The hardest programming language you’ll ever learn will be your second.
Don’t let this be disheartening — it means that when you first learn how to program, you have all of these preconceived ideas about programming. …