We're thrilled to announce important updates to our Service Level Agreement (SLA) concerning uptime commitments.
Since we always want to increase the quality of our service, we've revisited and enhanced our SLA terms to reflect these goals more than ever before.
dyrector.io is an open-source container management platform that offers self-service Docker and Kubernetes deployment and configuration management capabilities to any cloud or on-premises infrastructure for developers with an intuitive UI.
Feature flagging is a powerful technique that allows remote teams to quickly and easily toggle features on and off in their codebase. With feature flags development, teams can deploy new code to production without immediately making it available to end users.
This can be especially useful for remote teams, as it allows them to deploy code safely and efficiently. That’s because remote teams may not have the same level of communication and coordination as they would in a co-located setting. By using feature flags, remote teams can deploy new features and updates more frequently, without the risk of disrupting the user experience.
Let’s discuss what feature flagging actually means and how to get started with it.
Software development is a really challenging endeavor. A lot of time and energy has to go into making sure that customers like what you're building for them.
Many people make the mistake of thinking that product development mainly consists of coding. Developing a product (ideally) needs specialists, managers, tactics, and various tools. A good idea can indeed go a long way, but if you want to give your product the highest possible chance to penetrate the market, then you need to allocate all possible resources that you have available to throw at it.
Developers are one of the most prone groups of people to sprout white hair before their time. This happens for a multitude of stress-related reasons, and not choosing a proper CI/CD DevOps platform surely plays a substantial role in this!
Features can sometimes reach a high-enough level of complexity that simply cramming the entire thing behind a single feature flag and calling it a day becomes widely impractical.
More modular feature control needs to be thought of and implemented beforehand. Since such scenarios happen quite often all throughout development, a more advanced form of feature flag management is needed.
While the base concept of feature flagging remains untouched (in the sense that they still toggle stuff on and off), feature flags nowadays tend to act more like an interconnected web of toggles where they may or may not be dependent on each other to run. The main benefit of all this added complexity is the ability to use flags to control certain parts of a feature in a very modular and clean way.
Sit down, relax, and let me tell you an awesome story about the little country that could. A country that's unapologetically close to my heart. In case the title hasn't already given it away by now, I'm of course talking about the wonderful nation of Iceland.
Good code is one of the most valuable commodities in technology. Code quality can affect everything from code execution time and application load times, to how easy it is to maintain, read, and debug.
It can also play a significant role in your company's competitiveness. If your competitors are spending more time fixing bugs than adding features, then they're losing ground to you.
Code Hygiene goes hand in hand with avoiding Tech Debt and these two should be THE backbone of your company’s philosophy!
When growing any product or service, it’s to constantly gather feedback from your user base. And I mean constantly, else you risk losing focus from your real clients’ needs and priorities.
To drive this point home, I figured that the best course of action was to collect some valuable insight from a third-party. Joseph Harris, who works at Eucalyptus was kind enough to take the time and offer just that.