This is an idea worth spreading. Suggesting not to implement config files seems a bit extreme, but I chose to read that as a way to really emphasize the need to consider trade offs. Using that example makes it clear that it’s not about espousing one right way of doing things applicable to all problems, but about encouraging one to carefully weigh the options (pun intended).
Yes! "No config file" is extreme, but it's an extreme case that highlights how much choice we have. It's about weighing our options, considering more options, and perhaps leaning more toward fewer features when possible.
This is an idea worth spreading. Suggesting not to implement config files seems a bit extreme, but I chose to read that as a way to really emphasize the need to consider trade offs. Using that example makes it clear that it’s not about espousing one right way of doing things applicable to all problems, but about encouraging one to carefully weigh the options (pun intended).
https://www.linkedin.com/feed/update/urn:li:activity:7129839037216874496?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7129839037216874496%2C7129887118809522176%29&replyUrn=urn%3Ali%3Acomment%3A%28activity%3A7129839037216874496%2C7130347754098192384%29&dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287129887118809522176%2Curn%3Ali%3Aactivity%3A7129839037216874496%29&dashReplyUrn=urn%3Ali%3Afsd_comment%3A%287130347754098192384%2Curn%3Ali%3Aactivity%3A7129839037216874496%29
Yes! "No config file" is extreme, but it's an extreme case that highlights how much choice we have. It's about weighing our options, considering more options, and perhaps leaning more toward fewer features when possible.