I genuinely look forward to tech-specific leadership opinions, but the author lost me with the ham-handed attempt at humor in the opening paragraph.
"Don’t worry, leading engineers is just like writing code. Just like apples and oranges..."
and:
"You can’t write tests. An occasional survey is ok."
Seriously? If I can't show my new engineers how I expect tests to be written - who will? IMO being a technical lead is all about leading from the front, and by example - and that means everything from documentation to unit tests to architecture.
3 comments
[ 3.4 ms ] story [ 8.8 ms ] thread"Don’t worry, leading engineers is just like writing code. Just like apples and oranges..."
and:
"You can’t write tests. An occasional survey is ok."
Seriously? If I can't show my new engineers how I expect tests to be written - who will? IMO being a technical lead is all about leading from the front, and by example - and that means everything from documentation to unit tests to architecture.
This is how I interpreted it: We can't write test cases against a flesh and blood human being which tie into
"Then there is the latency. It takes weeks to discover if what you tried actually worked"