Stop Watching Tutorials and Start Writing Your Own Code With These Five Tips

I am a Unity C# developer, educator, and writer from Canada.
Search for a command to run...

I am a Unity C# developer, educator, and writer from Canada.
I want to add this to my list of articles I need to re-read over and over. There is much important advice here
Great tips, Taryn McMillan. 🙌
Start small is a great tip every devs should follow.
This series of long-form articles contains tips for new developers of all ages and skill levels.
Do you like math? Maybe you were a star math student in high school or university. Or maybe it’s been years, or even decades since your last math class. If you’re interested in learning how to code, by now you’ve probably realized that you need to b...
Introduction 👋 Hi, I’m Taryn! I’m a Unity dev who created a small project for Hacktoberfest 2023. In this devlog, I’ll introduce you to the project and talk about my goals for Hacktoberfest as a game developer. Tiny Troves of Dev Wisdom First, let’...

In today's post, I'll be talking about my latest Unity project, which is an updated version of the first game I ever published online. Introducing....No Crooks On Christmas! I decided to upgrade No Crooks On Christmas as a kind of challenge to mys...

Level up your game development skills by learning to spot and fix these common Unity errors.

Learn the differences between a project name and a product name

It's the end of the first week of my first time as an official Hacktoberfest participant! There have been many ups and downs this week, and I thought I'd summarize them here so that others can see what the experience of a first-timer is like. So wit...

When you’re learning how to code, it’s easy to think, “just one more tutorial.”
But how many tutorials is enough?
I started my coding journey taking courses on Udemy and I quickly discovered I was going to have to do more than tutorial projects to really hone my skills.
Courses on Udemy or tutorials on YouTube can act as a springboard, but they’re no substitute for writing your own code.
These five tips will help you take back control, break out of the tutorial cycle and start building projects on your own.

The French philosopher Jean-Paul Sartre said that "commitment is an act, not a word."
The first step as a beginner is to become aware of just how much time you are spending on tutorials and then to commit to breaking that cycle.
You should start by making your workspace distraction-free and conducive to working independently. If you need to, use an add-on to block the websites you typically use for tutorials, like YouTube or Udemy. You can even set up a separate desktop for coding or use a popular add-on like Cold Turkey or Focus to streamline your workflow.
In-app notifications or emails can also entice you away from your work. Be aware that many learn-to-code sites, apps, or free bootcamps send out newsletters that often include tutorials. Instead of viewing them right away, set aside a designated time to do it and don’t fall for FOMO, or fear of missing out, if you see something that interests you.

One of the biggest reasons you feel stuck is because coming up with your own ideas is hard. It’s so hard, in fact, that some of the world’s most famous inventors didn’t make their greatest discoveries until they were in their 40s, or beyond.
You may think there are no 'new ideas' but in fact there are new iterations of the same idea or concept all the time. A quick search on the Google App Store reveals dozens of meal-ordering apps, for example. They are all slightly different, with their own features and quirks. So don't let fear of imitation hold you back.
Here are four popular brainstorming techniques for generating project ideas:
There are also many excellent websites for design inspiration, such as Dribble or even Pinterest. Spend some time thinking creatively and admiring others’ work. And remember, in the brainstorming phase, no idea is a bad idea.

The key to designing a project you can finish when you are a beginner is to start small. It should be something that appeals to you, that you will have the passion to finish. As a beginner, it’s much better to create one, smaller project with polished features than many incomplete ones.
You may find yourself continuously wanting to add more to your project, which can fuel an addiction to tutorials. Instead, try to commit to a set of “core” features that you will ensure are completed, and a timeline for finishing them. You can add a list of optional ones that you will work on, but only if time allows.
How do you know when a project is finished? This is where project management skills come into use. In its simplified form, a project has three main stages:
There are many more in-depth project templates available online but you really only need to remember these three stages if you’re a beginner.

Starting your own projects doesn’t mean never watching another video or taking another course. Rather, it means approaching these learning tools with purpose and intention.
Keep a list in your notes of concepts or ideas you’d like to research more when you have time. It’s easy to do a quick Google search to double-check syntax but once you need to spend more than five minutes looking for an answer, consider whether it needs to happen right now. Don’t let the search for more information break you out of your coding flow, if you can help it.
Ever heard of a spiral curriculum? It’s a term used in pedagogy to explain the idea that you need to revisit a concept multiple times in order to truly understand it. Many coding beginners get hung up watching the same videos over and over because they’re worried they can’t move on until they’ve mastered a subject. But the truth is, you can often work around gaps in your knowledge and then slowly fill them in over time.

We all need help now and then, and as a coding beginner, you will too!
But it’s easy to fall down rabbit holes on sites like Stack Overflow or Reddit. That’s why when you need to ask for help, make it targeted. Otherwise you may end up spending hours following thread after thread on topics that are only tangentially related to what you're working on.
Remember to always make your search terms precise and specific. If there are no results for what you are searching for, go ahead and start your own discussion topic. Don’t get sucked into arguments over semantics if you can help it (frequent users on Stack Overflow know these happen often). Keep your end goal of becoming a better coder in mind-- the rest is just noise.

When was the last time you just sat down and coded, without worrying whether you were getting things “right”?
Practice makes perfect and the only way to truly become a better coder is to start doing it. Tutorials are a great place to start, but they can only take you so far.
I hope these five tips will help you gain the confidence to break out of the tutorial cycle once and for all and start flexing those creative muscles all on your own.
Happy coding!