Overheard: Slack is an all-day meeting with no Agenda.
In 2016, Slack felt like the best thing to happen for business productivity.
In 2021, I'm convinced it's one of the worst.
Here are my CEO hacks to reduce Slackxiety (Slack induced anxiety)... 🧵
This is how I felt when I found out gitflow is a "legacy Git workflow" that has "fallen in popularity in favor of trunk-based workflows." Atlassian says their gitflow overview is only up for "historical purposes." Thread. https://t.co/3uu1g9CZhs #ripvanwinkle@davefarley77
Control over what's in production, or independently deployed microservices -- choose one.
"In a microservices world, you consciously trade off consistency and standardization for independence." @davefarley77
Gestern Generalprobe für #NavigateEvent am 20.04. - bin gespannt ob nächste Woche auch alles glatt läuft und freue mich das spannende Programm im Track #ZukunftsfähigeArchitektur → https://t.co/ctOOBpCWSD
Jetzt kostenlos anmelden! → https://t.co/Yxdc3Vm7m5
APIs sind die Bausteine moderner IT-Architekturen. @benklatt von @viadee_it zeigt wie eine evolutionäre API-Entwicklung mittels #ConsumerDrivenContracts möglich ist.
Jetzt kostenlos anmelden! → https://t.co/s1YG2qjiX9
#navigateevent
Software schneller bereitstellen? @nmhuber von #Reservix erklärt im Track #ZukunftsfähigeArchitektur die vier Kennzahlen der IT und wie der Prozess zur Bereitstellung optimiert werden kann.
Jetzt kostenlos anmelden! → https://t.co/s1YG2qjiX9
#navigateevent
What do Cologne Cathedral and software development have in common? When it comes to lengthy renovations, quite a bit. Check out our latest blog post on a mindset for long-living software systems: https://t.co/EDjfNXNqGn #SustainableSoftware
If you spend time in an intense meeting, you need to rest. We often call this "decompression". @paulocaroli, who started out as a diving instructor, takes this metaphor and gives us a decompression table
https://t.co/DGZcgvbnfH
Regardless of whether you prefer TDD or code-first, static or dynamic languages, formal verification or no, the most powerful design technique is to spend time thinking about the problem. Not thinking through coding, just thinking.
I'm revising the set of training programs I'm offering and just added this new one: "Moving Forward with Legacy Code".
This should give your team a big boost. I'll help you get Unstuck! https://t.co/2Qd8kD8vxw
"Meetings that you would normally schedule for an hour should be made shorter to last no longer than 50 minutes, starting at five past the hour and finishing at five minutes to ('the UCL Hour')"
https://t.co/JrzJITSvfR
Gut, dass es in Ehrenfeld ein Rundfunk-Tanzorchester gibt, das uns jede Woche daran erinnert, was Livemusik ist. @rtoehrenfeld mit "Summon the Fire". #zdfmagazin
I like to think of myself as a distinction-drawer in software
Here is a true master-distinction-drawer, in a field where it's really needed at the moment. Finding differences in terms that are "sufficiently close that prying them apart clears space for thought"
A lot of technical leaders find themselves needing to fix, or even take over the product management role. I get a lot of questions for support on this, so I've put this post together for helpful resources, "Polishing Product Management Skills"
https://t.co/6EfuXrppFP
Reminded folks again that complexity is your biggest enemy. Most transformative inventions made things simpler, not more complex: e.g. electric motor vs. steam engines / boilers / belts / shafts.
Keep this in mind when being tempted by layer-on-layer-on-cloud "architectures"