06b91 No.1402
i stumbled upon this cool tip from david grizzanti at infoq dev summit boston: to understand an org's engineering vibe, look for what leave behind. kinda like a cultural anthropologist! he said start by observing behaviors and decision-making patterns before proposing new norms with patience & persistence.
grizzati suggested building allies first then using your influence wisely - basically leading through example i wonder how many companies actually follow this approach? have you tried it in any projects or teams?
any thoughts on shifting company culture without a big overhaul
article:
https://www.infoq.com/news/2026/03/engineering-culture-software/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global