At a going away party from a job I was leaving a few years back, my VP of engineering told a story I didn’t even remember but that I know subconsciously shaped how I viewed my role on that team: Toward the end of my very first day at the company, there was some internal system issue, and with pretty much zero context, I pulled out my laptop, figured out what was going on, and helped fix the issue.
This article was originally published in The New Stack. Given how volatile Bitcoin price is, an automated alerting system can be valuable for preserving our attention and sanity. We can pay attention to Bitcoin only when the price action is interesting. Momentum, that is buying an asset that has done well in the past, has been one of the most persistently effective trading strategies — see Clif Asness: “Value and Momentum Everywhere” and Tzouvanas (2019).
Cloud 66 offers a range of deployment options for Rails applications, each offering different benefits and trade-offs.
Most people in the world are familiar with legal tender paper money — also known as fiat currency — and how to access it online through a bank website, ATM, or mobile app. The idea of “digital money” or cryptocurrency — such as Bitcoin — remains a relatively new concept.
Our team has been working hard on building exciting new features like our DataMap, advanced Tracing UI, and more that will give you even greater power to monitor and visualize your data. Get caught up on everything that’s new and improved in the Coralogix platform!
In a world where executive and buyer attention spans are declining, how do sales and marketing professionals create the most relevant and timely experiences for customers and prospects to learn about your company’s solutions? By designing account-specific experiences that ensure the right message is delivered to the right executive at the right time.
From a single on-call engineer hopping online to resolve a problem, to a massive cross-team effort that brings in even the most senior technical leadership (CTO, CISO, or CIO), incident response teams are lucky when they’re able to resolve issues before a customer is aware. But in the cases where there is customer impact, other stakeholders like sales and customer service need to be informed and updated as well.
I work on the Solutions Architects team here at Puppet. We are sometimes the first line of defense in solving some of our customers' most challenging or unique problems, and every so often, we see trends in problems that we'd previously considered to be edge cases. For example, cCustomers often ask us two questions: How can we connect external configuration data to Puppet? How can we speed up changing their own configuration for service owners without onboarding them to Git approval processes?
