Aging your code isn't about resisting progress; it's about ensuring that when progress happens, it's built on a rock-solid foundation.
Codacy Pioneers Open Source Fellowship is supporting creators, maintainers, and contributors to open source software. Projects selected to participate in the program will receive a year-long monthly stipend, free access to the tools they need to work, widespread promotion, and mentorship from some of the brightest minds of today’s OSS community, including Evan You, creator of Vue.Js. Apply today!
Nitpicking in pull request reviews means offering insight that looks excessive, pedantic, and unimportant. It’s a pejorative term. I don’t question there are cases where the term applies, but many folks assimilate it to paying attention to the small stuff. By projecting all these negative connotations, this practice suddenly becomes undesirable: mind the big picture or leave the pull request alone. With that, we disagree. Small stuff when writing code matters, a lot.
Ever since I realized BASIC wasn’t the only living programming language, I thought about writing my own. Who wouldn’t? If you’re a developer, surely this idea popped into your mind at some point. No matter how much you love a particular programming language, you always have some ideas for improvement or even removal of annoying features.
The most important thing about reading this blog post is to not get scared off by the formulas. The post may look like all the crap you normally skim over, so you may be tempted to skim over this one. Don’t! None of this is hard. Just read the post top to bottom, and I promise you every individual step and the whole thing put together will make sense.
If features are pizza, feature flags are the pizza box. Imagine if you just fed pizzas right out of the oven into someone’s face… it would be messy.