> All programming teams are constructed by and of crazy people
This job is crazy AF but like 6% is the devs around us.
The whole org structure above us has no idea what we "monks" do & are up to, as a HN'er replied to me today.
The random shit we get left with seems chaotic & absurd, but if the dev predecessors were around to provide some rationalization/explanation, it'd make sense. But there's little practice of devs leaving enduring artifacts to explain what quest they set out on, what they expected, what changed, what happened, and how they feel about what ended up running in prod. This is like 10% devs fault, and far more about what signals the org sends, whether it bothers to care. Orgs with actual engineering genetics should make a real practice, but so often we use trobal/oral knowledge to convey trust, but this never endures, never lets the org grow; instead loss reigns, defines the org, as people come & go. Context is so very rarely kept.
This job is crazy AF but like 6% is the devs around us.
The whole org structure above us has no idea what we "monks" do & are up to, as a HN'er replied to me today.
The random shit we get left with seems chaotic & absurd, but if the dev predecessors were around to provide some rationalization/explanation, it'd make sense. But there's little practice of devs leaving enduring artifacts to explain what quest they set out on, what they expected, what changed, what happened, and how they feel about what ended up running in prod. This is like 10% devs fault, and far more about what signals the org sends, whether it bothers to care. Orgs with actual engineering genetics should make a real practice, but so often we use trobal/oral knowledge to convey trust, but this never endures, never lets the org grow; instead loss reigns, defines the org, as people come & go. Context is so very rarely kept.