Like our other writing contests, we are giving out monthly prizes for the very best HackerNoon Debugging stories. A $1,000 prize pool is up every month, with $500 going to the writer of the best article.
Solved a Software Performance Issue? Share Your Story and Win $$$.
We’ve picked our winners by taking the 10 story submissions that generated the most traffic. HackerNoon’s editorial team then voted, picking the top three stories among them and deciding which order to place the winners.
We had the pleasure of voting over these 10 stories:
To make sure that any bugs in our algorithm don’t affect the outcome, editors voted for the top stories. Here are the winners:
Congratulations @mcsee! You’ve won $500!
How many times do we see lazy argument names?
TL;DR: Name your arguments according to the role and not the accidental position
In software engineering, CI/CD or CICD is the combined practices of continuous integration and continuous delivery or continuous deployment. CI/CD bridges the gaps between development and operation activities and teams by enforcing automation in building, testing and deployment of applications.
Job well done, @yuraabharian! You’ve won $300.
Code refactoring is the process of restructuring the previously written code without changing the code functionality. Refactoring does not mean adding new features or re-writing code to fix any kind of bugs.
Congratulations @alex-omeyer! You’ve won $100!!
In this article, we discussed that using
contextas initial state and ‘Destroy and Recreate’ are anti-patterns while using internal state in JSX and
propsas a dependency in useMemo are good patterns. We also learned that we should be cautious when we are using hooks without a dependency array and nesting for arranging React components.
Great job, @darshitac, and congrats on winning $100.
With that ends our quick announcement! Thank you to everyone who has sent in an article already, and another round of congratulations for our winners! Keep an eye on contests.hackernoon.com for more details. We will contact the winners shortly!
Sign in and use this writing prompt to enter the #debugging contest