I flagged Strange behaviour in PCB when solenoid turns off answer as "inappropriate for respectful discourse" @W5VO clearly agreed. 12 hours later @Nick Alexeev unilaterally decided that it was not "inappropriate for respectful discourse" saying "In case you don't know: negative feedback is a valuable thing (especially in engineering), and sometimes it involves saying things like "bad design" or "you should learn basics". It's better to hear about problems at the drawing board, than to listen to all the cheer only to run headlong into avoidable problems." The problems I have with that is "Nick Alexeev" can unilaterally override another moderator, and that he effectively said "you can be a jerk if you are right, it is good for people". So my question is this, do we want that much power in the hands of one person?
Let me tell you a story about Professor Jacob. Professor Jacob took up electronics with the military during Vietnam to avoid being drafted and having a gun put in his hands. He worked on, and taught others to work on ICBMs. He reflected on that experience in a Pugwash talk, and how he had one chance to get it right. On the first day of every class he taught, he would say that he would teach the material the way the military taught him to teach. His courses were tough, but well worth the effort.
Moving forward, I was in a prototyping class with a different professor, and we were to design a circuit and put it on a PCB. My circuit was built around an IC from a course with Professor Jacob. I drew up a relatively sloppy schematic, and decided to go by his office and ask him to review it. He agreed, and then spent about five minutes ripping my design apart, and calling me out for my sloppy schematic. By the time he was done, the paper was half red with corrections he had drawn.
I left his office glad I had went to see him. Had I not had my schematic reviewed, my PCB would have most likely been a paperweight. More importantly, that was the day I truly learned the value of a neat, properly drawn schematic.
What does this story have to do with the answer in question? The reality is classic engineering disciplines can be harsh. Unlike software where the product can be respun multiple times in a matter of minutes until it's right, multiple iterations of hardware are expensive and time consuming. We're not just talking about the cost of the prototype, there's: certifications, tooling, rework, etc. It's important to do everything possible to get it right the first time, therefore minimizing those costs. That includes scrutinizing every single design decision. Believe me, I've seen the results of half baked design reviews, and it's not pretty.
Finally, before ripping on Olin, keep in mind, he's been a EE for over 30 years and has forgotten more than most on this Stack will ever know. We're lucky to have him here as a regular participant. In many ways, he reminds me of Professor Jacob, always willing to help, if you really tried to help yourself, else, expect to be called on it.
I don't think the original answer was all that rude. It was a bit gruff, and used a pedagogical approach that I don't often use, but the OP got the answer that fixes the problem. I wasn't all that thrilled with the comment thread, but I think you were the one that inserted bad language, IIRC, so that's on you. It was locked before I could flag your comments, and the comment thread was appropriately moved to chat between now and then, and the inflammatory comments removed from there.
You should be glad they're gone, as they didn't make you look real good. Even if you're super ticked at a user, try to maintain dialog in the manner that you would like to be spoken to. It's a much better way to get your point across.