A big part of my work has to do with code. I’ve worked as system administrator – installing, patching, and configuring someone else’s code. I’ve worked as independent programmer, writing code on my own. I also programmed as part of the team. And on top of that, I worked as Team Leader and Project Manager, where I had to interact a lot with programmers. Programming world on its own is as huge as the universe. There is always something to learn. When I find something worthy or something that I understand enough to write about, I share it in this category.
A lot has been said about the wide range of Amazon Web Services (AWS). They are plenty and cover a whole lot of technologies – from low level infrastructure to artificial intelligence. It is difficult to grasp just how big and complex the AWS feature set. But I think the above periodic table of Amazon Web Services helps a lot.
“When I started writing PHP…” is a nice look at how PHP ecosystem has changed in the last 20 years. Those of us who have been using it since then, are guaranteed to drop a nostalgic tear.
The running joke “you’re not a real PHP developer until you’ve written your own CMS and discarded it” wasn’t a joke yet. It was just becoming reality, but it wasn’t old enough yet to be a joke. (Yes, I wrote my own CMS and discarded it.)
awslabs/aws-cloudformation-templates is an extensive collection of Amazon AWS CloudFormation templates for a wide range of resources and services. Some of these can be used as is for deploying production infrastructure, others are good starting points for those of us who are still learning.
“How To Speed Up The Code Review” is a collection of excellent tips and strategies on how to make your Pull Requests easier to review. These work equally well for Open Source projects and for proprietary repositories.
The gist of this article is: don’t make large pull requests, and don’t mix different types of changes within the same pull request. Read the whole thing for suggestions on how to actually do that.
“Semantic Versioning – why you should care” is a nice take on Semantic Versioning and how and why people should is. I particularly liked the practical examples of changes and which version bump they correspond to.
I frequently find myself explaining the Semantic Versioning to developers, and going over some example changes. Now I can just send the link to that article instead and safe myself some time.
Very nicely done!