11 thoughts on “Great programming advice from 1983.

  1. I think I’ve worked with some people who learnt programming from that list.

    For example, from the top of a ~5000 line .c file:

    #include …

    int d;

    void theFirstFunction ()…

    d is then used in multiple functions in the file.

    (d is for date, obvs)

    Like

  2. Seems like today’s programmers are taught to create Rube Goldberg machines. That way they are the only ones who understand the code and have job security, or if they move on to another company charge outrageous consulting fees to fix the problems in their program they created.

    Like

  3. Paulo Lourenco Robotics and embedded programming. Writing for a microprocessor requires that you understand that everything you do has an impact. A few clock cycles on a GHz processor are fast. But if you have a 50 kHz crystal, a routine that needs to run on each interrupt, and the interrupts arrives on average each 50 ms, you need to optimize code. Not because you want to, but because you can’t honor the requirements otherwise.

    Like

  4. Malthe Høj-Sunesen I have programmed in similar fashion in university in the early 90s. I was just surprised this is still taught as recently as 2012 was all I meant. You would think those old compilers are just not available anymore, and C code is the bare minimum. Guess not.

    Like

Leave a reply to Derek Waters Cancel reply