Comments by "p11" (@porky1118) on "The Unreasonable Effectiveness Of Plain Text" video.

  1. 10:10 I'm happy how we work in our small company. Everybody knows the goal, everybody is available any time, when somebody has a problem, they immediately tell it to someone, if someone has an idea (normally the boss), they just tell it, if someone needs something from somebody else, they also just tell them.
    8
  2. 8:40 I started to hate these issues. When never managed to use them properly in the small company I'm working on. Insetad we sometimes create huge issues and add a list of hundreds of points into it. An issue like "Coding fixes", "Gameplay issues" or "Visual problems". Creating an issue is way too cumbersome for adding each little problem we found. Often it's just faster to tell the person who was responsible for it directly, or just to fix it oneself.
    4
  3. 2:44 No, that's not true. It doesn't matter too much if my data is stored in plain text or in a binary format. If the data is complicated, it's always better to use a tool. And as long as you know the structure of a file, you can write new programs to use the same binary format. I've done that. I've written a project called pns (published on gitlab), for simulating petri nets, which uses a binary format. I already had created a similar tool before, which was already more powerful. So I used the old tool to create the petri net, saved it using the binary format, and then loaded it from the binary format into the new program. If you know the binary format, it's much easier to create new tools to read and write the data. No need to write complicated parsers yourself or use serialization 4lugins. 4:22 Okay, it seems to be about text heavy data. In that I agree. These should always be stored in a non-binary format (markdown, latex, html, etc.).
    2