Don't use tutorials from tutorial hell in your portfolio

Tutorial hell is a term used to describe the state where someone learning a new skill, such as programming, becomes stuck in an endless cycle of following tutorials without progressing to creating original projects or developing their understanding. I would advise not to put tutorial projects in a portfolio. This is not meant to be an anti-tutorial. This article will focus on programmers who are trapped in tutorial hell.

Factors of tutorial hell

There are various ways programmers can end up and stay in tutorial hell. Here are the factors that make up tutorial hell.

• Dependency on tutorials
• Lack of application
• False progress
• Stalled growth

When I was learning how to program in college, I had to sift through good and bad tutorials. Good tutorials go in-depth and explain the details of how and why. Bad tutorials don't offer much explanation and go straight in. Some of the tutorials I encouraged had incorrect syntax and I had to figure out how to correct it myself. The learner relies heavily on step-by-step guides without practicing problem-solving independently. Copy and paste is common and contributes to the "Software engineers just copy and paste" counterargument. Software engineering is not just copy and paste and it's more complex than what most people think on the surface. There's little to no transition from consuming information to applying it in unique, real-world scenarios.

Completing tutorials may give a sense of accomplishment, but it doesn't always translate into mastery or the ability to work autonomously. Gaining experience is important because it prepares you for the work ahead. I got my start in web dev before getting into software and still learning and working with web platforms to this day. Learners often don't develop critical thinking skills, which are essential for troubleshooting and writing efficient, original code.

Why shouldn't tutorial projects be included in your portfolio?

Projects from tutorial hell can hinder a portfolio. This also includes coursework from academics unless it's a polished project. A few main reasons why not to put a tutorial project in your portfolio.

• Lack of originality
• Limited skill representation
• Signals lack of independence

As competition for jobs becomes insanely competitive, a portfolio needs to be polished. Employers and recruiters often recognize popular tutorial-based projects, which can make your portfolio seem less creative or authentic. Now not all employers or even recruiters will view your portfolio, but there is a greater chance that your portfolio and profile will be viewed. Especially in the age of social media and technology, employers will likely check your profile more compared to a decade ago.

Tutorials typically offer a controlled environment, which doesn't showcase your ability to tackle unexpected challenges or devise unique solutions. Presenting tutorial projects might suggest that you're not yet ready to work independently, a crucial skill for professional programmers. As I continue learning, not everything is about coding and soft skills do matter when I delve deeper into the business side of things.

What to include in a portfolio?

• Original projects
• Customization
• Documentation
• Range of skills

Create projects that solve specific problems or showcase unique ideas. These can be based on personal interests or real-world applications. In my opinion, you should care and have a great interest in personal projects. If inspired by a tutorial, significantly modify it to create something unique and demonstrate your problem-solving abilities. Include well-written code, comments, and documentation to show your understanding of the project. I have a detailed README for my projects and to go the extra mile created a wiki page for the project. Highlight diverse projects that showcase different programming languages, frameworks, or tools you’ve mastered. I don't like to pigeonhole myself and work with various tools in the last few years.

I like to build my projects and learn. By focusing on projects demonstrating your creativity, problem-solving, and technical expertise, you’ll create a portfolio that stands out and effectively represents your skills.