You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
129 lines
5.6 KiB
129 lines
5.6 KiB
11 months ago
|
<!DOCTYPE html>
|
||
|
|
<html lang="en">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="X-UA-Compatible" content="IE=edge">
|
||
|
|
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||
|
|
|
||
|
|
<!-- Enable responsiveness on mobile devices-->
|
||
|
|
<!-- viewport-fit=cover is to support iPhone X rounded corners and notch in landscape-->
|
||
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1, viewport-fit=cover">
|
||
|
|
|
||
|
|
<title>Julio Biason .Me 4.3</title>
|
||
|
|
|
||
|
|
<!-- CSS -->
|
||
|
|
<link rel="stylesheet" href="https://blog.juliobiason.me/print.css" media="print">
|
||
|
|
<link rel="stylesheet" href="https://blog.juliobiason.me/poole.css">
|
||
|
|
<link rel="stylesheet" href="https://blog.juliobiason.me/hyde.css">
|
||
|
|
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=PT+Sans:400,400italic,700|Abril+Fatface">
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<body class=" ">
|
||
|
|
|
||
|
|
<div class="sidebar">
|
||
|
|
<div class="container sidebar-sticky">
|
||
|
|
<div class="sidebar-about">
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me"><h1>Julio Biason .Me 4.3</h1></a>
|
||
|
|
|
||
|
|
<p class="lead">Old school dev living in a 2.0 dev world</p>
|
||
|
|
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<ul class="sidebar-nav">
|
||
|
|
|
||
|
|
|
||
|
|
<li class="sidebar-nav-item"><a href="/">English</a></li>
|
||
|
|
|
||
|
|
<li class="sidebar-nav-item"><a href="/pt">Português</a></li>
|
||
|
|
|
||
|
|
<li class="sidebar-nav-item"><a href="/tags">Tags (EN)</a></li>
|
||
|
|
|
||
|
|
<li class="sidebar-nav-item"><a href="/pt/tags">Tags (PT)</a></li>
|
||
|
|
|
||
|
|
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
|
||
|
|
<div class="content container">
|
||
|
|
|
||
|
|
<div class="post">
|
||
|
|
<h1 class="post-title">How to Kill Developer Productivity</h1>
|
||
|
|
<span class="post-date">
|
||
|
|
2020-07-20
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/developers/">#developers</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/productivity/">#productivity</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/programming/">#programming</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/ti/">#ti</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/onboarding/">#onboarding</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/data-flow/">#data flow</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/architecture/">#architecture</a>
|
||
|
|
|
||
|
|
</span>
|
||
|
|
<p>There are several ways to not kill developer productivity in a project.
|
||
|
|
Unfortunately, the real causes are never discussed.</p>
|
||
|
|
<span id="continue-reading"></span>
|
||
|
|
<p>Recently I read another post about "how to not kill your developer
|
||
|
|
productivity", that says exactly what every other post about it says:
|
||
|
|
Basically, "do not interrupt".</p>
|
||
|
|
<p>But can we really avoid interruptions? Isn't the "ping!" from the coffee
|
||
|
|
machine an interruption? Isn't a full bladder an interruption? Isn't the front
|
||
|
|
door bell ringing when a package and/or food delivery an interruption?</p>
|
||
|
|
<p>What's the difference between those interruptions and someone asking
|
||
|
|
something?</p>
|
||
|
|
<p>And do less meetings? Why? Is it because nobody cares enough to write a
|
||
|
|
meeting agenda to point what needs to be decided? Or maybe 'cause the frontend
|
||
|
|
developers don't care enough about the problems the backend developers are
|
||
|
|
facing and vice-versa?</p>
|
||
|
|
<p>Would a meeting scheduled a week in advance an "interruption"?</p>
|
||
|
|
<p>I can't see how interruptions can be a problem. Imagine this:</p>
|
||
|
|
<p>This developer went though an onboarding when they joined the company, and
|
||
|
|
they were shown the purpose of the company, they were shown the product the
|
||
|
|
company sells and how it works, there were shown the product architecture,
|
||
|
|
they were explained the reasons behind every solution applied, they were given
|
||
|
|
time to discuss other solutions with their pairs, they were not put on a
|
||
|
|
corner to explain every minute of their working day.</p>
|
||
|
|
<p>With that, can you imagine that someone making a question about some part of
|
||
|
|
the system while whoever is coding is in the middle of a function to
|
||
|
|
frobnicate<sup class="footnote-reference"><a href="#1">1</a></sup> foo? Maybe they will need a bit time to find where they
|
||
|
|
stopped, but as the solution was already discussed, and they know the purpose
|
||
|
|
of the solution they are working, the interruption would do very little in
|
||
|
|
their productivity.</p>
|
||
|
|
<p>Unfortunately, in IT, we are seen as "machines" and most manufacturing
|
||
|
|
techniques are applied directly without considering that we are people (or do
|
||
|
|
you think "kanban" was born in IT and not inside the Toyota manufacturing
|
||
|
|
plant?).</p>
|
||
|
|
<p>A stopped machine is wasted money. Stopping production for preventive
|
||
|
|
maintenance, without the machine being really broken, having to take it and
|
||
|
|
check every part, is wasted money.</p>
|
||
|
|
<p>And, unfortunately, when a developer is not "developing", they are seen as
|
||
|
|
wasted money. And that's why simple stuff, like explaining why a system
|
||
|
|
exists, what is the idea of the data flow inside the system and things like
|
||
|
|
that are completely ignored: 'Cause the "machine" is not producing anything.</p>
|
||
|
|
<p>And that's why, when the production is halted, productivity goes down.</p>
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
|
||
|
|
</html>
|