22 ms·

> imagine a dentist who is passionate about pulling teeth out Exactly. Many times, the best code is no code. And making decisions about what code to write need

• Ekaros 4y ago
  There is really some questions that should be asked: Why are we doing this? For what reason it has to be done this way? Do we need to do this at all? What do you actually want? And so on. Meetings are useful to clear up this stuff and at best result there is simpler solution, or not need to do work at all.
  • xpe 4y ago
    Yes, some kinds of meetings can be useful. The author of the post, in my reading, laments petty meetings not productive ones.
  • ratww 4y ago
    However it is often the case that programmers "at the leaves of org charts" (to paraphrase another commenter) won't get to participate on meetings that can define if something can be replaced by "less code", let alone "no code". In small orgs with a headcount of tens that's very easy for developers to grasp the value and the need for certain things. But when you're in a 1000+ developer organization it is often the case that the reason you have to do something is because this is a requirement coming from two or three management levels above. In some orgs, a lowly developer might even be unable to even sit at the table with the big boys. They might have a say and a good perspective in micro decisions, but not in macro ones. In this case, I can definitely see TFA being written. To use the dentist example, imagine a dentist that's passionate about pulling teeth, but doesn't get a say on wether the teeth should be pulled or not.