Is it crazy to think that Python could be the language managers and developers finally speak in the same meeting?

Two languages, one meeting

At a consultancy I watched the same pattern repeat for years. The manager sold a scope to the client promising features they hadn't checked with the team. The developer got the ticket without context, solved it, and then had to explain why the original estimate was impossible. Both were right. Both were speaking different languages.

What the manager couldn't see

Software management culture was built on Scrum, sprints, and velocity points. The manager was the one who negotiated scope, protected the team from last-minute changes, and translated technical work into dates for the client. The client asked for dates because they needed to know how long it would take to get to market and how much their investment would return. The manager turned that pressure into deadlines for the team. They knew how long delivery took, but didn't understand what was being built.

What the developer didn't say

The developer lived in GitHub, Stack Overflow, and the terminal. Their identity was in the code, not in slides. They measured their worth in merged PRs, sprint points cleared, how much work they delivered compared to their peers, how competitive they were. Not in promised features.

But that same bubble isolated them from the business: they could build anything except explain why it mattered. At Arkus that feeling was stronger. The developer was a resource assigned by ticket, not a partner in the decision — no matter how many times they said the usual phrases: "We're a family", "We need to work under the same culture", "Let's unite to reach the same goal".

When the tool changed, the conversation didn't

When AI tools arrived — GitHub Copilot, ChatGPT, Claude Code, and the rest — the gap didn't close, it widened. Managers started asking to "automate everything" without understanding what that meant. Developers watched their tools become accessible to anyone, but the conversation between both sides stayed the same: one asked for dates, the other made excuses. Distance is never a SKILL.md — it's shared context.

A language both can read

Python is the language where these two worlds — or rather, these worlds — can meet. Not because managers should write production code, but because they need to read what their team builds. A manager who can follow a pandas script, understand an analysis notebook, or challenge a technical estimate isn't doing the developer's job — they're doing their own better. The question was never "should managers program?" The question is "how do they speak the same language without either stopping being what they are?"

References