100SILEX, de 0 à 100 s: perfectly
1502 Phone-Reluctant Introverts, There is Nothing Wrong With You
As I sit down to write this blog post there is the dreaded sound of a prolonged vibration as my phone skids, bouncing and sporadically across my desk. This is perfectly ideal and ironic distraction that actually befits the very thing I am thinking about and from which it is distracting meâŠ Itself!
I have always had an absolute detest for talking on the phone. And Iâll say now that it has nothing whatsoever to do with the person at the other end, I just find it a horrible tool for communicating with.
I think I probably am, and always have been worse than most people when it comes to using the phone (in the traditional sense, ie speaking to people) but if you can identify with any of this then read on. If youâre thinking, âwhat are you on about, I love the phoneâ then youâll probably just get confused, but if you also have friends who ânever answer the phoneâ then this might help you to understand them a bit better.
I canât sum it up any better than Sophia Dembling in her article, 9 Signs that You Might Be an Introvert:
767 The 5 types of programmers Â« Steven Benner's Blog
In my code journeys and programming adventures Iâve encountered many strange foes, and even stranger allies. Iâve identified at least five different kinds of code warriors, some make for wonderful comrades in arms, while others seem to foil my every plan.
However they all have their place in the pantheon of software development. Without a healthy mix of these different programming styles youâll probably find your projects either take too long to complete, are not stable enough or are too perfect for humans to look upon.
The code may not be pretty, but damnit, it works!
This guy is the foundation of your company. When something goes wrong he will fix it fast and in a way that wonât break again. Of course he doesnât care about how it looks, ease of use, or any of those other trivial concerns, but he will make it happen, without a bunch of talk or time-wasting nonsense. The best way to use this person is to point at a problem and walk away.
You want to do what to my code?
This guy doesnât care about your deadlines or budgets, those are insignificant when compared to the art form that is programming. When you do finally receive the finished product you will have no option but submit to the stunning glory and radiant beauty of perfectly formatted, no, perfectly beautiful code, that is so efficient that anything you would want to do to it would do nothing but defame a masterpiece. He is the only one qualified to work on his code.
Iâm a programmer, damnit. I donât write code.
His world has one simple truth; writing code is bad. If you have to write something then youâre doing it wrong. Someone else has already done the work so just use their code. He will tell you how much faster this development practice is, even though he takes as long or longer than the other programmers. But when you get the project it will only be 20 lines of actual code and will be very easy to read. It may not be very fast, efficient, or forward-compatible, but it will be done with the least effort required.
What do you want? It works doesnât it?
The guy who couldnât care less about quality, thatâs someone elses job. He accomplishes the tasks that heâs asked to do, quickly. You may not like his work, the other programmers hate it, but management and the clients love it. As much pain as he will cause you in the future, he is single-handedly keeping your deadlines so you canât scoff at it (no matter how much you want to).
Well, thatâs a possibility, but in practice this might be a better alternative.
This guy is more interested the options than what should be done. He will spend 80% of his time staring blankly at his computer thinking up ways to accomplish a task, 15% of his time complaining about unreasonable deadlines, 4% of his time refining the options, and 1% of his time writing code. When you receive the final work it will always be accompanied by the phrase âif I had more time I could have done this the right wayâ.
Personally, Iâd have to classify myself as the perfectionist. So, which type of programmer are you? Or perhaps you know another programming archetype that is missing from my list? Post a comment below and Iâll add it to a new updated list.
101 - 201