Compendium of Wondrous Links VI


wondrous_links

  • They finally found all those buried Atari cartridges, and confirmed a beloved urban legend. Just wonderful.
  • This episode of @ExtraCreditz follows up an idea I always had about education. The key is being demanding, but allowing a lot of opportunities.
  • Amazing book introduction, showing how no one is immune to think that they are stupid. Lots of things in live are hard.
  • Readability in code is not about being literary. Is about making the code easy to understand. You don’t read code, you explore it.
  • The Great Works of Software. The premise is extremely interesting. What are the most influential pieces of software?
  • The hilarious (is funny because it’s true) Programming Sucks and a follow-up What programming is Like.
  • Is programming a dead end job? I still can’t help but feel sad each time that a (good) developer decides to move into management.
  • It’s easy to forget how much the things have changed in term of software distribution. What Writing and Selling Software Was Like in the 80’s (yep, also from The Codist. You should subscribe)
  • The computer world is very dominated by English, and even so with latin alphabet. This idea about making a computer language in Arabic is fascinating. It not only shows how difficult is to set up an environment without problems out of “the ASCII world” (the magnitude is not comparable, but trying to code in languages like French or Spanish has a lot of friction), but it also shows up how alien (yet beautiful) a different alphabet looks. I wonder how code and programming will be if the dominant language would’ve been something like Chinese or Arabic.
  • What is the “Agile mindset” anyway? The graph is very interesting. Specially the “Chaos labeled as Agile” side.
  • I don’t really like the idea of “rivalry” against Vim and Emacs. I prefer to consider them two valid options. But this article goes into explaining their different appeals and why they have been around since an extremely long time ago in computer-years.
  • 10 Most common Python mistakes. Good to check.

Minor offences


Here is a very interesting quote by Niccolò Machiavelli

“People should either be caressed or crushed. If you do them minor damage they will get their revenge; but if you cripple them there is nothing they can do. If you need to injure someone, do it in such a way that you do not have to fear their vengeance.”

When I look back about the things that had really make me angry on work places, they have been relatively minor things. Setting a firewall so I can’t easily access half of the Internet, usually the interesting parts for the work I was doing (you could still check the cache, but it was pretty inconvenient) or having to work overtime in short notice for stupid reasons…

I mean, they are not BIG deals. There are worse things to deal on a working environment, that are common. Bad salaries (and ridiculously low raises), mean coworkers, being forced to use software you don’t want to use, no support (RTFM as the universal response for everything)… The list can be very long, and I’m sure that every worked had to deal with these or other problems.

But why do you feel that bad about those minor, stupid problems? Why such a minimal inconveniences hurt you in a personal level? Probably because they are perceived somehow as an attack and lack of confidence. And that makes people very nervous and upset.

Here’s the story about management. The rule number one of management is Thou shall not demotivate. Ideally, it should be about motivation, but that’s too long down the road. The sad true is that it is extremely easy to do stupid moves that can have a relatively big impact in the morale of the team.

Yeah, If you can take no more than one coffee each morning, mmm, that'd be great.

Yeah, If you can take no more than one coffee each morning, mmm, that’d be great.

A common pattern: the Team is working reasonably well, no obvious problems on their part. And, of course, Manager SHOULD do something. You know, because Manager must leave an imprint and, well, manage. Be a Leader and so. Then, Manager finds out a small thing, probably just because of boredom. And, as it’s the only incident on sight, Manager takes it as a sign. “If I leave this be, soon all will be chaos”  So, Manager decides to have a word with Team Member (maybe even with the whole Team). And gently, but firmly, gives a cease-and-desist order. “Hey, remember that what your doing is Wrong.  I am with you, but this Company does not tolerate that kind of behaviour. It will be awesome if you stop it”. And then, when Team Member leaves the room, Manager breaths and feels like Chaos is Under Control and Everything is OK Now, probably forgetting about the whole incident.

But Team Member feels really bad. “Is that really a problem? What happens with X, Y and Z, that are Real Problems? What about Other Team Member? I think is doing something very similar, but I can’t see any effect”, and decides that this is Just a Job, and it’s not worth working really hard. And maybe the next recruiter email is looked in a different, more favourable way.

I think that’s why all those posts about sodas not free anymore rings so deeply. Because they are the way of a manager (being upper management or just middle management) to say “I’m going to cause an inconvenience to you, for no particular reason other than feel good to myself” Everyone get the problems. The things that are important. That really cost money, or time, or are a pain. And those are part of the job. But the minor, stupid offences that are just a way to remind the workers who’s on charge. That the Overlords are the ones making the decisions, and all those words of “our most valuable asset is our team” are empty.

As with any other action, I think that those kind of problems deserves a small though about if they are worth the hustle. Is it worth to bother someone with this small thing, or it is an opportunity to just set that someone angry? If it is, it’s probably best to leave it be, or work around it.

But minor damages just hurt, and makes people to be vengeful, probably at the worst moment.