You probably know this situation all too (painfully) well . . . A critical incident has hit. You get the alert and the race is on! First headache up on deck – coordinating all the stakeholders. You call, you email, you text – some people are available, some are not. Some might be sleeping, or just getting up in a completely different time zone.
At Skeddly we’re focused on bringing you the best in AWS help tutorials, AWS scheduler services, and AWS backup services. However, from time to time we like to reach out to other leaders in the AWS space to help you, our blog readers, stay on top of the latest developments and news within the AWS ecosystem. Today Skeddly had the opportunity to speak with a few of the bright minds behind Keyhole Software, a cutting edge technology company with an impressive amount of AWS experience.
In her CIO online post, “6 Blunders to Avoid When Dealing with End Users,” Mary Brandel discusses some of the mistakes IT professionals make when interacting with end users. In short, the article calls attention to some common limitations within IT staff when communicating with customers. This isn’t a matter of intelligence or willingness.
Tools and features introduced with the intention of benefiting and empowering an organization can sometimes end up being misused. PowerShell is a classic example.
Network devices underpin every modern infrastructure environment with the switches and routers of your environment representing the roads information needs to travel on to reach its intended destination. And if switches and routers are the roads, picture configuration files as the traffic lights, they direct, protect and support the flow of information.
The typical workday for a developer using Git involves a variety of different tasks. Between generating new SSH keys, cloning Git repositories, viewing commit diffs, creating pull requests, and on and on. But do you ever sit back and think about how much time you’re spending on each of these seemingly smaller tasks? Trust us, it adds up. The concept for the GitKraken Git GUI was born from this very frustration.
