Comments by "Lepi Doptera" (@lepidoptera9337) on "ThePrimeTime" channel.

  1. FP... write once, understand never. ;-)
    3
  2. There is a school of thought that suggests that the single best thing you can do for your software quality is to get rid of the architect. On can even find very rational reasons for that idea. The major argument is that an architect is not god. He or she can't predict the future, but by locking you into the architect's initial (and most likely false) solution for the unexplored problem you are preventing your coders to modify their approach as the really crucial elements of the task are being discovered during actual software development. Being open to change is generally better than having planned everything (the wrong way) right at the beginning. It's the same problem with socialism and capitalism. Socialism is theoretically better because it starts with a grand plan, but in reality capitalism outperforms vastly because it's not locked into the false grand plans.
    2
  3. Cool topic and I admit that I didn't think about it like that, either... but I always arrange my data in arrays if I can. That includes the way I define objects. If "some thing" has to do the same function a lot of times, I allocate arrays for the data. The main reason why I do this is memory layout. By pre-allocating a fixed memory block and checking range all kinds of nasty dynamic bugs can be avoided because the system always knows how much memory it has left.
    1
  4. No, it isn't. Objects don't solve any hard problems and the compiler treats them like comments and removes every single trace of them. You are basically writing objects to pleasure yourself. It does nothing for your software.
    1
  5. I haven't written more than a few dozen lines of JS in my life. I didn't find it a particularly advanced language. It's three steps above machine code, which is good enough, and that's all it is.
    1
  6. Uncle Bob is a great showman. And that is all he is. ;-)
    1