In today’s fast-paced working environment, employees tend to rely less and less on IT departments. The use of workplace technology has never before been this accessible and essential and employees are increasingly confident that they can work independently from IT to decide on their own external tools and solutions.
In my world, customer-driven is beating data-driven’s ass.
The majority of the public has a decent general knowledge of technology, especially as younger generations grow up surrounded by phones, tablets, and virtual reality simulations. However, with technology as an industry spanning across many categories and developers creating new specialisms each year, there are still those who distinguish themselves and emerge into the industry with revolutionary ideas.
Major incidents are inevitable, and fixing them is the top priority for any ops or DevOps team. But what happens after service is restored? Do teams take the time to fully understand what went wrong, then follow up to prevent it happening again?
RapidSpike would like to make a statement about how one of our developers assisted the City of York Council with a potential data breach on their One Planet York mobile app in early November.
A changelog is a chronological list of important changes users can reference as an application or service expands. Logs explain what features are added, which are changed or adjusted and what those changes do. They sometimes provide explanation or instruction. Logs are useful for preparing your user base for scheduled downtime, and giving your most loyal users something to look forward to.
Since Amazon released Lambda in late 2014, the notion of serverless applications and function-as-a-service has steadily gained steam. Being able to focus on application code and simplifying infrastructure management is alluring, but traditional monitoring methods are no longer applicable. With less visibility, it becomes even more important to take advantage of the available monitoring methods. In this post, we discuss those monitoring methods, CloudWatch Metrics and CloudWatch Logs.
As a product manager in a high-growth environment, I have come to accept that at any given time, something is on fire. Or, at the very least, smoldering. Five or so years ago, the team at Raygun, was just five people. Now, we’re building software products for businesses like Nordstrom. With this growth also comes many learning opportunities for a product manager like myself.
