When we decided to start working remotely back in 2013, we never thought about the health benefits. We chose to carve a remote path because it would make us more efficient, more fluid and more dynamic, not because it might stop us getting sick. But now, thousands of companies around the world are going remote for precisely that reason.
Automation and robotics in retail is rapidly changing the retail landscape – so much so that there are clearly winners and losers. I’m not talking about the war between brick and mortar stores and digital marketplaces, but rather I’m talking about the retail digital revolution where the winners are delivering greater than 4.5% comparable store/ channel sales growth compared to their brothers that have not embraced automation and robotics.
Last month we released our new dashboards feature. Now’s a good time to drive your story with a dashboard of your own. Easily create with drag-and-drop - Clearly illustrate key metrics - Securely share between teams and partners
More and more companies are shifting from a traditional enterprise sales mindset to a developer-first mindset for driving product adoption. Sales calls and demos will not work as developers do not want to be sold to. Instead, the platform needs to be adopted similar to how consumers may adopt a mobile game or e-commerce app. Yet, developers are also less receptive to facebook ads that may have worked for those games and e-commerce apps.
For this blog post, I’m going to take a step back and not go into data visualization best practices. Rather, I’m going to explore what you can do with your data before arriving at a final visualization – what I like to call “re-expressing” your data. Accordingly, we are going to look at the topic of transforming your data.
Let’s admit it – web services (SOAP) are here to stay for a few more years, and maybe for a long time in some places where there is no business incentive to rebuild them. However, with a decline in new SOAP web services and most applications moving to cloud native architectures, a common query is “how can we support legacy services while moving to microservices?”
Elixir 1.10 was recently released, and with that release came a little-known, but very interesting feature—compiler tracing. This feature means that as the Elixir compiler is compiling your code, it can emit messages whenever certain kinds of things are compiled. This ability to know what’s going on when Elixir is compiling our code might seem simple, but it actually opens up a lot of doors for opportunities to build customized compile-time tooling for Elixir applications.
If you've been on the hunt for a new developer podcast, then you understand just how difficult and fruitless that pursuit can be. You can spend hours online sifting through coding podcasts, programming podcasts, and DevOps podcasts only to realize one simple thing: none of them focus on your preferred programming language! With thousands of different developer podcasts out there, the problem is magnified exponentially. Fortunately, we at Scout APM have nothing but expertise and time on our hands.
March 10th, 2020 • By Jon de Andrés Frías In this two-part series of blog posts, we’ll explain how Kafka has helped us in removing parts of our architecture that we consider to be “legacy”. During the development of a project sometimes we need to take decisions on our architecture or software design that may not be the best decisions from a pure and perfectionist technical perspective.
It has been a week since several of our mVISE and elastic.io developers attended the Vodafone TOBi Hackathon at the Vodafone Sky Lounge in Düsseldorf. Some of them were in the 3rd place team and all contributed greatly to the future success of the TOBi Chatbot. Teams formed, ideas flowed, problems were overcome, and the air was filled with the sounds of developer’s keystrokes!
