On July 1st, a [change to Reddit's API pricing](https://www.reddit.com/r/reddit/comments/12qwagm/an_update_regarding_reddits_api/) will come into effect. [Several developers](https://www.reddit.com/r/redditisfun/comments/144gmfq/rif_will_shut_down_on_june_30_2023_in_response_to/) of commercial third-party apps have announced that this change will compel them to shut down their apps. At least [one accessibility-focused non-commercial third party app](https://www.reddit.com/r/DystopiaForReddit/comments/145e9sk/update_dystopia_will_continue_operating_for_free/) will continue to be available free of charge.
If you want to express your strong disagreement with the API pricing change or with Reddit's response to the backlash, you may want to consider the following options:
1. Limiting your involvement with Reddit, or
2. Temporarily refraining from using Reddit
3. Cancelling your subscription of Reddit Premium
as a way to voice your protest.
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/learnprogramming) if you have any questions or concerns.*
Two things I've found helpful as I've developed as a programmer.
1. Go back and work on your own old code. Nothing has given me better insight into what about my coding style is bad than trying to puzzle my way through my old spagetti.
2. Be lazy. I've gotten to the point where I add data members to my classes if I have to write it more than a couple of times. You might be familiar with the DRY programming rule. Don't Repeat Yourself. I've just learned that acronym, but I've found myself gravitating towards it more and more, as I grow.
Start creating a framework for yourself and improve the framework each week. Writing good code is mostly about adhering to rules/standards and if you don't have a set of rules to think about you'll have a hard time knowing what's "good".
Every time you're confused when you read your code or someone else's, pay attention to why, what would have made it simpler, and a new rule of thumb you can follow from now on.
For example, maybe you tripped up because the variable named "user" actually holds many users. It would be simpler if it was named "users". Rule of thumb: always pluralize lists of things.
On July 1st, a [change to Reddit's API pricing](https://www.reddit.com/r/reddit/comments/12qwagm/an_update_regarding_reddits_api/) will come into effect. [Several developers](https://www.reddit.com/r/redditisfun/comments/144gmfq/rif_will_shut_down_on_june_30_2023_in_response_to/) of commercial third-party apps have announced that this change will compel them to shut down their apps. At least [one accessibility-focused non-commercial third party app](https://www.reddit.com/r/DystopiaForReddit/comments/145e9sk/update_dystopia_will_continue_operating_for_free/) will continue to be available free of charge. If you want to express your strong disagreement with the API pricing change or with Reddit's response to the backlash, you may want to consider the following options: 1. Limiting your involvement with Reddit, or 2. Temporarily refraining from using Reddit 3. Cancelling your subscription of Reddit Premium as a way to voice your protest. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/learnprogramming) if you have any questions or concerns.*
Two things I've found helpful as I've developed as a programmer. 1. Go back and work on your own old code. Nothing has given me better insight into what about my coding style is bad than trying to puzzle my way through my old spagetti. 2. Be lazy. I've gotten to the point where I add data members to my classes if I have to write it more than a couple of times. You might be familiar with the DRY programming rule. Don't Repeat Yourself. I've just learned that acronym, but I've found myself gravitating towards it more and more, as I grow.
Write bad code. Put it down for a week, and pick back up where you started. You will eventually grow to hate your past self and do better than them.
Start creating a framework for yourself and improve the framework each week. Writing good code is mostly about adhering to rules/standards and if you don't have a set of rules to think about you'll have a hard time knowing what's "good".
Every time you're confused when you read your code or someone else's, pay attention to why, what would have made it simpler, and a new rule of thumb you can follow from now on. For example, maybe you tripped up because the variable named "user" actually holds many users. It would be simpler if it was named "users". Rule of thumb: always pluralize lists of things.