Tech and Code Dabbler(Open Source Supporter). Camping, Biking, Running and Hiking Enthusiast. Video Game Junkie. IT Everything As A Service! Personal Opinions.
@justintimekc @adazlian I mostly remember the megamerg prs with every file being changed and people asking why the builds seemed to take so long! Also having to remind people a hot fix is normally done in production...
@GergelyOrosz@managertools Of course, if the ship is sinking, role power telling everyone to bail water is also required or everyone drowns. High stress does lead to building trust quicker though!
@GergelyOrosz The underlying issue is changing things before building trust with the org. @managertools has a good podcast (https://t.co/QwKkZGyHsd), step one Fit In (no new initiatives)! This applies more for sr leaders, whose changes have an even greater impact and need more trust.
@sykesjs I walked up to check them out this morning and they were already switched over. I can confirm I feel asleep and woke up to the song Chiefs Kingdom! My wife keeps becoming a bigger fan and asking when we are getting back to KC.
We're thrilled to be named on @BuiltIn 2023 Best Places to Work in NYC list!
At @21co__, our priority is to build strong, innovative products as much as it is to build a connected, inclusive, and empowering culture. We're delighted to be succeeding in both. Come join us! 🚀
@andrewicarlson@heroku@awscloud@Azure@googlecloud Netlify also changed how they charge, which dramatically increased cost for teams. Many have moved to AWS Amplify and GCP AppEngine to get something out and running instead.
@5ype Example, "Let's do it, let me know when complete."
VS
"[Ticket #] is good to move ahead @ [nameofperson]. It should be complete by [date]. Let me know by COB [date] if there are any issues. If I am unavailable, follow up with [stakeholder] or [backup]"
@5ype It is difficult! There are many differences between the two and issues if they are used incorrectly. In my experience, it mostly involves context. Sync comms context can be implicit, since it is typically in the moment. When using async comms, context needs to be explicit.