Browse Source

Discussing hiring

master
Julio Biason 5 years ago
parent
commit
0da7ac14f4
  1. BIN
      content/thoughts/hiring-so-wrong/dev-a.png
  2. BIN
      content/thoughts/hiring-so-wrong/dev-b.png
  3. 1
      content/thoughts/hiring-so-wrong/hiring.drawio
  4. 72
      content/thoughts/hiring-so-wrong/index.md
  5. BIN
      content/thoughts/hiring-so-wrong/phenomenological.png
  6. BIN
      content/thoughts/hiring-so-wrong/requirements.png
  7. BIN
      content/thoughts/hiring-so-wrong/skills.png

BIN
content/thoughts/hiring-so-wrong/dev-a.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

BIN
content/thoughts/hiring-so-wrong/dev-b.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 19 KiB

1
content/thoughts/hiring-so-wrong/hiring.drawio

@ -0,0 +1 @@
<mxfile host="app.diagrams.net" modified="2020-04-20T16:54:02.195Z" agent="5.0 (X11)" etag="3IN96yEPUU8pcOjBG7EO" version="12.9.14" type="device" pages="3"><diagram id="3228e29e-7158-1315-38df-8450db1d8a1d" name="Page-1">1ddNb5swGAfwT8N1Atu8HZOs7XboZZ20swcOWDV+Isd526ffQzAJialUqWlEUQ7x3y+Yn4kDAV00+yfDV/UzlEIFJCz3Af0eEBIxQoL2E5aHLsmipAsqI0vX6By8yH/ChaFLN7IU64uGFkBZuboMC9BaFPYi48bA7rLZEtTlWVe8El7wUnDlp39kaWuXRkl+rvghZFW7U2ck7Sr+8uK1MrDR7nwBocvj0VU3vB/LXei65iXsBhF9COjCANjuW7NfCNXa9mxdv8c3ak/zNkLb93QgUUxdpy1XG9HP+jg3e+g9sBPSY2G+lEotQIE5VtDHMEvDGHNY8ULadrmTEItra+BV9A016LZvbRuFpagdBrQdDnM8MPfn389OGCv2g8hdz5OARlhzwCaultL8W9x1cncfDbM+2Z1XMw7dGtSDhTyF3N1B1Wn8syJ+cZBvo5IPoEZkNptPCzVKr1Gj+5vSD5iKLE4YmZQpyyZgyjzTn3qL1yRBe7h4XdaRuC2bMCxzJSuNhQK7CXSatwQSN9OZq2hkWar7uZL82hU36BHYKB+BTW/kGnuuv8QW1OYrwyZTgE082N+Gl/IruzLPNY7v7pp6rs9SScvdSCOsHuM7tAZLgY+EN9GLE28bzcf02AgeuxFe5uEtQC+VxEfTaeMxdo3HRv+EPhMv9/FqDuuJy/mb4d3l+mEGcqjDdSEmbuf/ZCn7RDssnt+ojnWD11b68B8=</diagram><diagram name="Requirements" id="_mFYKGmZYzxxgRB4uli3">rZNLc4MgEMc/Dcd2FGIeR2NMc+nBZCY9EyXKBF2HkMb00xcFfDSHTmfKeGB/u/xxHyASlc2bpHXxDhkTCHtZg8gGYezPMEbt52UPQ5b+3IBc8swGDeDAv5iFnqU3nrHrJFABCMXrKUyhqliqJoxKCfdp2BnE9Naa5uwJHFIqnukHz1RhqT9fDY4d43lhr17ihXGcaHrJJdwqex/C5Nwt4y6p07KJXguawX2ESIxIJAGU2ZVNxERbW1e2cL8/7ZMwCVabI54l8XGd7F6M2PYvR/oMJavU/0oTI/1JxY25KnS5qoerr1bRrdTG+syFiECA7BzEx2G4DjSHmqZcteMz97R5VRIuzAVWULVnC1UKbfmtDFRqJLPtlub2V5hUrPnR2l8S9/tu6ClnUDIlH/qcU1msXgOjZEfcXzpwHyYm8Gyfi9Gw9JDaKc17+aHUemOr7cxhKDrf6OWR+Bs=</diagram><diagram name="skills" id="KO3FsDjXEZ7HhlBQ8uJI">zVTRboIwFP0aHpfQooiPirotccky3Uz2snS0QmPhYq2Cfv0KFJBpsrjsYQ0PvefennLPPWA5fpzfS5JGT0CZsLBNc8uZWBijHsZW8dj0WCEecisglJyaohZY8BMzoG3QPads1ylUAELxtAsGkCQsUB2MSAlZt2wNontrSkJ2ASwCIi7RFacqMihyh23igfEwMld7eFAlPkmwCSXsE3OfhZ11uap0TGou0+guIhSyM8iZWo4vAVS1i3OfiULbWrbV6e15tkpHvpiTx+0yex1O6F1FNrvlSNOhZIn6W2qnoj4QsWe1CmWv6ljrq1n0KHUwXnMhfBAgy4QzQUMPuxqHlARcFfZxbR3ulIQNqwsTSIqzkYqFjlBBA4k6o5mVS+PmVZhULP822h8aR800tMsZxEzJoz5nWHoDM0Bj8IExRta6xa1LojOjNCAxDg0b6lZmvTFKX1c9SecfL6ctokv78L73Zj7iBzOo36mO8Gg07v9/1VGvqzry7AvZ+/YV2RvwBtl12H6HZe7sZ+dMvwA=</diagram></mxfile>

72
content/thoughts/hiring-so-wrong/index.md

@ -0,0 +1,72 @@
+++
title = "Hiring So Wrong..."
date = 2020-04-20
[taxonomies]
tags = ["work", "hiring"]
+++
Today I found this [article by Neil Sainsbury on hiring
coders](https://www.neilwithdata.com/developer-myth) and how the process is
wrong. While I agree that the whole process is nothing more than red tape, I
don't think the problem is what the article actually says.
<!-- more -->
The point Sainsbury makes is that we lack empathy when hiring. While I may
have got this wrong -- as in "We lack empathy to understand people" instead of
"We lack empathy to give people some chance" -- I believe the problem is that
hiring is done by managers, not coders.
I'm not going to bash managers here -- I worked with pretty damn good managers
but also some awful -- I believe the problem is that managers don't actually
understand what coding actually is. Heck, I don't believe _we_ understand what
coding actually is.
Here, let me show you this with Venn diagrams -- 'cause Venn diagrams are
awesome.
Imagine there is a company hiring developers. They have a set of necessities
they want to fulfil:
![The set of things a company works on and requires](requirements.png)
And then we have the developer skills:
![The set of skills a developer have](skills.png)
... which is not what a company actually wants. What they want (or should
want) is actually the size of the developer _phenomenological field_. This
field describes the experiences someone had.
Imagine two developers: Developer A spent the last 5 years working on the same
field (let's say, mobile, or web development), using the same technology (say,
Java, or React); developer B has done a bit of everything: they worked on the
backend in two different languages, played a bit with three different
JavaScript frameworks and did some play with different languages. Both have
the same time in the field, and one could claim that A is a senior developer
'cause they spent so much time in the same field, they probably know
everything about it. But the fact is, when you check their phenomenological
areas, you get something like
![not in scale](phenomenological.png)
What we actually have is that A is an _full_ worker, while B is
actually a _senior_[^1].
But nevermind, 'cause what we actually want is to fulfil the spot with someone
that matches our requirements, right?
Developer B, 'cause we experienced a lot but never got deep into anything,
would have a match like
![](dev-b.png)
But developer A actually fits like this
![](dev-a.png)
---
[^1]: I once said that what made a difference between full and seniors is the
amount of crap they had to deal with.

BIN
content/thoughts/hiring-so-wrong/phenomenological.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

BIN
content/thoughts/hiring-so-wrong/requirements.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 8.8 KiB

BIN
content/thoughts/hiring-so-wrong/skills.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 9.4 KiB

Loading…
Cancel
Save