3 ms·

I was hoping for an essay about a more user-oriented approach to formulating a project vision. Who are we building software for? Who are we helping them to help

I was hoping for an essay about a more user-oriented approach to formulating a project vision. Who are we building software for? Who are we helping them to help (the end-end-user)? This article seems to be about who to hire. Furthermore, it stands as an antithesis to meritocracy and inclusivity. I mean sure, don't hire assholes, but "surround yourself with people you truly love" is not a healthy demand.

atoav 4y ago
I think — as usual — the true advice is somewhere in the middle. If you just hire people you like, you and up with a bunch of your friends and very likely not a functional team. You will have a good time, but it might not be very successful. It might even be not a good time at all, because people you like are not necessarily people you like to work with. If you just hire people who fit the precise description of the task, you end up with people who all can technically do exactly what you thought you needed. But firstly what you thought you needed can turn out to be wrong and even if you are right what is needed can change. Secondly a big part pf working together is some sort of compatibility. People must and should not all be the same, but they should complement each other well and be able to work together effectively. If you don't look at the "who" and "with whom" at least a little bit, this is a huge risk.