Knowledge work is the combination of work execution and workflow. Execution usually gets the attention in IT.

This should not be controversial. It's effectively a tautology.

The more chunks we have acquired, so to speak, the more of an "expert" we are.

Frequently, when I hear someone defending "waterfall", and dig deeper they're actually talking about small-a agile.

We tackle different strategies for communicating ideas and “How to get your way”.

If your team is surprised by their 360 review, this should be seen as a big problem.

So some of the bad KPIs, like lines of code, are easy to detect. But how do we choose a good KPI?

Oshri Cohen is a fractional CTO with a diverse background, currently working with four companies. He joins me on the show to cut through some of the confusion surrounding the Chief Technical Officer role.

Only hire after identifying your constraints, and determining that a new person is the likely solution.

Musk thought Twitter was bloated with engineers. I expect he's right, because most companies are.

CI is as CI does. If you aren't continuously integration, you don't do CI.