Twitter | Search | |
Stefan Büringer
687
Tweets
190
Following
85
Followers
Tweets
Stefan Büringer Feb 25
“Introducing Dispatch” von Netflix Technology Blog
Reply Retweet Like
Stefan Büringer retweeted
Allen Holub Feb 22
"Working ahead" is usually serious waste. Consider a UI/UX person who doesn't know how to code insisting on working in a silo. (Not to pick on UI/UX—they're far from the only transgressors—but I've seen this many times.) They spend the first few days of the Sprint designing. 1/6
Reply Retweet Like
Stefan Büringer Feb 22
Go Language Mechanics On Stacks And Pointers
Reply Retweet Like
Stefan Büringer retweeted
Alexis Richardson Feb 21
Really excited to see Google finally embrace GitOps after several years of flip flopping GitOps is primarily about the ideal of automated operations. But, for enterprise, mediated by policy We need a new open source stack for this
Reply Retweet Like
Stefan Büringer retweeted
Claire Lew Feb 19
I wrote a brand new piece today about how to leverage your 1-on-1 meetings to coach your team... Focus on (1) their perception of current state (2) what success is for both of you (3) what they want most (4) what is holding them back. Full piece here:
Reply Retweet Like
Stefan Büringer Feb 19
Very useful overview of Go tooling:
Reply Retweet Like
Stefan Büringer retweeted
Claire Lew Feb 18
Root cause of why leaders micromanage? They’re grasping for a semblance of control. The story they've told themselves is: The more they push, check-in, keep tabs... the more they're in control. Truth is: Control is a construct. You do not *nor* can you “control” your team.
Reply Retweet Like
Stefan Büringer retweeted
Fernand Galiana Feb 13
K9s code-name `OpenFeZ` aka Function made eZ has been released! K9s now offers preliminary support for ! Does this FeZ look... familiar? Happy FezThursday yall! (sorry couldn't help it too much AustinPowers last we)
Reply Retweet Like
Stefan Büringer Feb 16
EKS vs GKE vs AKS - Evaluating Kubernetes in the Cloud
Reply Retweet Like
Stefan Büringer Feb 15
Intel Engineer: Much Left to Solve Before Cloud and Edge Can Become One
Reply Retweet Like
Stefan Büringer Feb 15
Explaining Knative, the Project to Liberate Serverless from Cloud Giants
Reply Retweet Like
Stefan Büringer Feb 15
Kubernetes Operators: 4 facts to know via by
Reply Retweet Like
Stefan Büringer Feb 14
Continuous Profiling of Go programs by
Reply Retweet Like
Stefan Büringer retweeted
Dmitry Vyukov Feb 13
We open sourced tcmalloc! Includes per-CPU caching mode indispensable for highly-threaded servers&extensive huge page support. Lots of worthy things for low-level hackers. I contributed to it a bit incl cache capacity balancing 1/2
Reply Retweet Like
Stefan Büringer retweeted
Matt Barcomb Feb 13
Crazy thought: what if we abolish the title "manager"? And replace it with two new ones: - work environment designer - professional development coach
Reply Retweet Like
Stefan Büringer retweeted
Peter Mueller Feb 12
Reply Retweet Like
Stefan Büringer retweeted
Go News Feb 12
The GitHub CLI (written in Go)
Reply Retweet Like
Stefan Büringer retweeted
Jaana Dogan 🌳 Feb 10
This is 100% true! Hard work is not the actual issue. If I can work hard, I see it as a privilege. But trying to sustain your hard work with obstacles and continuous blockers... It sucks up all of your energy and make you question everything.
Reply Retweet Like
Stefan Büringer retweeted
Cindy Sridharan Feb 9
Meaningful Availability, NSDI 2020 Fantastic paper from Google that points out why common availability metrics like MTTR/MTTF (time based) or success ratio (count based) are misleading, and introduces a new user-centric meaningful availability metric "windowed user-uptime".
Reply Retweet Like
Stefan Büringer retweeted
Allen Holub Feb 8
The idea of specifying a piece of work in great detail up front, accurately predicting dev time, and then "failing" if you don't meet that prediction, is an extreme form of irrational thinking that simply does not, and never has, reflected the way software dev works.
Reply Retweet Like