One of the marks of a good senior developer is that they have lots of interesting opinions. After years of working on different software projects, they'll be able to passionately explain why they think is ass, paired programming is no fun, and the GitHub CLI changed their workflow. MongoDB I have anecdotally found 2 things to be true: Senior developers without opinions tend to not be very good Junior developers with many opinions tend to not get good quickly (and are annoying AF) Let the gatekeeping begin As a new developer, it's smart to consume developer content. However, when you listen to Prime, Dax, Theo, or myself give opinions, you need to remember that they're opinions, not . our yours Don't misunderstand: I publish my opinions to convince you to join my cult ( is based) but taking my word at face value does a disservice to yourself. If you simply regurgitate another developer's opinions, not only will you stunt your learning, but it will look bad in interviews and on the job. Go It's obvious when your opinions haven't been forged in the fires of your own experience. Context-specific opinions There are kinds of developers out there: many Frontend Backend Mobile Embedded, etc. But we don't just discriminate on tech stack! There are also many kinds of : companies Venture-backed startups Indie hackers Established tech incumbents Non-tech companies with internal software Consultancies, etc. No matter what advice you're hearing about technology, you need to remember that the speaker comes from a specific background. coming from people with can both be great takes. Opposing hot takes different backgrounds Do you need to scale computing power across a cluster of machines? good. Kubernetes Are you building a personal site for your dog? Kubernetes bad. I work mostly on Backend HTTP servers in Go and think debuggers are a waste of time (the state of the program is easy to reproduce) John Carmack does a lot with game engines and loves debuggers (the state of the program is hard to reproduce) Theo works on a startup where product requirements are constantly in flux and performance isn't the #1 problem. He likes TypeScript. The Primeagen works at btw and works on performance issues where product direction is relatively static. He likes Rust. Netflix Now, the best opinions tend to carry the infamous "it depends" as you keep digging for exactly this reason. However, if you're a Xitter enjoyer like myself, you need to appreciate that the context is contained in the tweet. You'll only begin to understand the context surrounding a hot take once you're familiar with the author. never The point? If you're new to coding, understand that this stuff is nuanced, but adding nuance to titles, thumbnails, and tweets gets clicks. never So what's this about TDD? Test-driven development is a somewhat controversial development methodology. Some developers love it, some hate it. MBA's love it because it makes them feel safe. TDD falls into the same category as a few other hot-button topics: always Pair programming Agile & Scrum SOLID principles Micro-services vs Monoliths FP vs OOP NoSQL vs SQL, etc. These are things that you'll hear about often, and most developers tend to form strong opinions about them. Here's my advice: If you haven't used it in a real project, don't hate it (yet) That's why it's to hate Haskell. No one has tried it in production yet. literally impossible Be a humble junior dev (I wasn't) One of the biggest mistakes I made early was simply assuming I knew more than I did. I would push for refactors that made no sense to get away from technologies that I thought were "old" or "bad". I wanted to rewrite perfectly stable parts of the code because I thought the new hotness was more maintainable. By all means, consume coding content online, but try to understand the reasoning behind the opinions you're hearing. Try to think about the context that influences the speaker. Then, when you have a chance, try the thing out for yourself before making your own bold claims. PS: The only exception to all of this is scrum. , you can just trust me on that one. It sucks regardless of your company, religion, political beliefs or sexual orientation. Scrum always sucks Also published here.

Every Developer Should Learn to Give Up Sooner

What Web Framework Should I Use?

Learn to code on Boot.dev

Nominated for 2022 - HackerNoon Contributor of the Year - Algorithms

Nominated for 2022 - HackerNoon Contributor of the Year - Mathematics

Nominated for 2022 - HackerNoon Contributor of the Year - Cryptography

Nominated for Coding Guru of 2022

Nominated for 2022 - HackerNoon Contributor of the Year - Github

Nominated for 2022 - HackerNoon Contributor of the Year - Online Education

Nominated for 2022 - HackerNoon Contributor of the Year - Job Hunting

Nominated for Super Career Strategist of 2022

Too Long; Didn't Read

You Aren’t Qualified To Have an Opinion on Test-Driven Development Just Yet

You Aren’t Qualified To Have an Opinion on Test-Driven Development Just Yet

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

A Complete Overview of Cryptography

3 Habits That Will Help You Become a Top Developer

15 Things I Wish I'd Known As a Junior Developer

3 Simple Rules to Writing Better Code Instantly

7 Best Tech Career Paths of The Future

A Complete Overview of Cryptography

3 Habits That Will Help You Become a Top Developer

15 Things I Wish I'd Known As a Junior Developer

3 Simple Rules to Writing Better Code Instantly

7 Best Tech Career Paths of The Future

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps