This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
The original version of this post had the tag #NoRetrospectives in the title, but I got tired of the flak and removed it. My intent was to be a bit provocative and to get people thinking about how we can do better than a biweekly retrospective.
This article titled " Die Arbeitswelt der Zukunft " appeared in German last week in the "Digitalisierung" column of Wirtschaftwoche. The workplace of the future. We already have an idea of how digitalization, and above all new technologies like machine learning, big-data analytics or IoT, will change companies' business models — and are already changing them on a wide scale.
Multi-tasking doesn’t exist. All the science tells us that we are only capable of task switching. And task switching is really bad for us. Every time we switch tasks, we add to our cognitive load making us less effective at all the tasks we are attempting to do at once. A lot has been written on this topic with the attempt to justify creating work environments where people can focus.
Have you ever needed to perform a certain action when the user tries to hit the back button or exit out of your application on Android devices? For example, what if the user was able to back out of your application and you wanted to show a dialog. Or what if you have a video application and you wanted to pause the video when they tap the back button?
I started writing “ Serverless Architectures ” in May 2016. At that point I’d recently finished up at my previous job, had just been to the first Serverlessconf , hadn’t done much writing in a while, had some time on my hands, and so decided to put a few ideas together. I thought a few folks might be interested. Of course publishing it on Martin Fowler’s site was always going to get it to a wider audience (thanks Martin!
I have been asked several times about how to get a Performance Monitor like view on Linux. There are lots of Linux tools available (top, iotop, Grafana, and SQL Sentry just scratch the surface of available options) to monitor the Linux system. Allow me to share one such example to capture and monitor a system. Performance Co-Pilot. PMCHART can be used much like you use performance monitor.
Multi-tasking doesn’t exist. All the science tells us that we are only capable of task switching. And task switching is really bad for us. Every time we switch tasks, we add to our cognitive load making us less effective at all the tasks we are attempting to do at once. A lot has been written on this topic with the attempt to justify creating work environments where people can focus.
I’ve been playing around with GraphQL for a little over a month now, just to see if it is worth all the buzz it has been getting when it comes to modern API development. I must say that the more I use it, the more I’m coming to like it. I recently wrote a few tutorials around getting started with GraphQL using Golang , but being the polyglot that I am, I wanted to see how difficult it would be to accomplish the same in something else, like Node.js.
I’ve been playing around with GraphQL for a little over a month now, just to see if it is worth all the buzz it has been getting when it comes to modern API development. I must say that the more I use it, the more I’m coming to like it. I recently wrote a few tutorials around getting started with GraphQL using Golang , but being the polyglot that I am, I wanted to see how difficult it would be to accomplish the same in something else, like Node.js.
A large part of my performance consultancy work is auditing and subsequently governing third-party scripts, dependencies, and their providers. Uncovering these third-parties isn’t always so straightforward, and discussing them with the internal teams responsible (more often than not, the Marketing Department) is usually quite sensitive and often uncomfortable: after all, approaching a third-party vendors, or your marketing team, and telling them that their entire day job is detrimental to perfor
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content