Wow, awesome! This will definitely improve our writing experience! Thanks, Neptune ^^

Great article, Sadra Yahyapour ! 👏

Had a good laugh, thank you @chriskalmar! Dark humour is always appreciated! 👏

Even though I would avoid the Greek pizza on the menu, this is a lovely and well-structured article! I have two concerns, which are out of the scope of this article of course, but I will mention them anyway. 😝 This switch statement will eventually become hard to maintain if the pizza is tasty and the business grows to add more entries to the menu. Additionally, I would consider throwing an exception in the default branch and removing the spinach from the Greek pizza as a good practice. Good job, Theodoros Karropoulos !

As a fan of uniformly typed code, and an ambassador for clean coding and following best practices, I must say this article is exquisite! Good job, Ronald Blüthl ! 💪

Hey Maxi Contieri , good article! I feel, however, that the wrong vs. right cases you provided are not comparable with each other. The "wrong" example is an if/else and the "right" one is an if/else-if/else. Implicit "else" seems fine to me when the "if" body is surrounded by curly braces, if not then I'd prefer a ternary return assuming there would only ever be two cases. From my point of view, the most important takeaway is the suggestion to give up on the if/else* block altogether and replace it with polymorphism.

Another helpful post, Shai Almog , good job! 👏

Thank you for the clarifications, Shai Almog , much clearer now!

Excellent post, Shai Almog . Congrats! 👏 It looks like a great tool and I definitely see myself trying it out but I am a bit skeptical as to production debugging for three reasons: Firstly, I think we allow our app to be vulnerable if we permit such tools to connect to a production server. Secondly, I wonder how safe an alternative a snapshot is when compared to breakpoints. Last but not least, it's unclear to me whether or not performance could be impacted while the tool is attached.

Sagarpreet Chadha , you've certainly improved my opinion towards mono-repos; pior to reading this I'd definitely say "no", but now I might consider it. On the other hand, I believe it should be approached with caution as it's purely situational on how the projects are internally structured and the size of the codebase. I've worked on a mono-repo in my youth and I can safely say that it was purely chaotic as per navigation, not to mention the horrific loading times I faced every time I needed to startup my IDE, search, etc.