1. 8
  1.  

  2. 3

    What sucks about being a master programmer is that the feeling that you are flying is often interrupted by the realisation that your current plane does not let you maneuver the same way the birds do.

    It’s then when you realize “Oh my, this language sucks!” or “I see what you did there, Guido.” and then you try a different plane and see how it feels to fly that.

    1. 2

      In my case, it’s almost always the same plane that I go back to. I find some task that I want to complete that would be a pain in language X, and end up realizing it could be done in a 5 line bash script, or I find something I want to model and end up realizing it could either be done in Ruby, or Lisp, and in either case, the code would suffer a lack of expressiveness in one area, and display great eloquence in another. I don’t really like this - in my eyes, it feels like I get a shallow understanding of the limits of a particular language, and a deep understanding of the lack of those limits in the languages I prefer to use for certain things, but never get to see the strengths of the languages that I do not prefer.

      For this reason, lately, I’ve been trying to avoid language switching, once I’ve settled on what I’d like to build a particular project in. Occasionally, I’ll language switch if a piece of code can easily be prototyped in a particular language, then switch back once the prototype is built. I try to look at my code quality in my personal projects not as “how well can I build this thing” but rather “what can I learn from building this thing.” I think I just find learning to be the more interesting part.

    2. 1

      Pick a small number of specific skills you’re simply good but not great at, and then develop competence to an extreme, almost obsessive degree. Get to the point that you’re better at that particular tiny corner of the world than nearly anyone else you know. Once you get there, examine the pros and cons of deep but highly specific knowledge.

      Im not going to spend all this time to develop “competence to an extreme” just for so i could “examine the pros and cons of deep but highly specific knowledge”.

      but even a loose grasp on “knowing how to use the right stuff, at the right time” will take you far.

      I don’t think this is a great advice either? What is the practical use of this? To obtain a loose grasp on a subject just in case your boss asked you about the particular bit you know of this particular subject which will start a series of event that ended up with you as the CEO of the company?

      All in all I don’t find any useful advice or interesting idea. There are a lot of ‘wise oneliners’ type writings but these are not very useful practically.