Since the beginning of June this year, internet connectivity in the Russian-held Ukrainian city of Kherson has been rerouted through Crimea, the peninsula in southern Ukraine that has been occupied by Russia since March 2014. As I explain in this blog post, the rerouting of internet service in Kherson appears to parallel what took place following the Russian annexation of the Crimean peninsula.
Your team has worked hard on a software product for months, and it’s finally ready to release to your users! But then the worst-case scenario happens: a wide release soon indicates that the software is plagued with bugs and performance issues, resulting in poor reviews and widespread user dissatisfaction.
In this article, I’ll provide a guide to Git for non-developers. So, if you are reading this as a full experienced Git user, you may disagree with some of my statements. Don’t bother reading on; we recognize you as the expert! If, on the other hand, you’re new to Git, this piece is for you.
Interrupts are often seen as a problem that eats away at your team’s productivity, and gets in the way of shipping important things for your customers. It’s often consciously accrued from the tech debt we accept to ship features sooner. However when a team doesn’t have a good strategy for dealing with the consequences of those decisions, the pain is felt much more acutely and much sooner.
Data disasters are practically inevitable, but a planned out backup strategy can combat their damaging effects. The Cybersecurity and Infrastructure Security Agency (CISA) of the U.S. government is a major organization that recommends sticking to a 3-2-1 backup strategy. Follow the 3-2-1 backup rule to ensure that your data is kept safe.
The demand for cloud services is rising. Databases have been popular tools for a long time. However, the landscape is changing, with cloud databases becoming increasingly popular.
