I actually love Mr. Robot because at least they are trying to show the actual tools plus the codes that can be used to hack, not some kind of random console outputs that doesn't even make sense in the most of the tv series/ movies

When you changed a logic structure but the tests still pass.

KISS.
Keep it simple, stupid.

At the beginning the project is nothing but an idea. If you get it off the ground, that's already a huge success. Rich features and code quality should be the last of your worries in this case.

Throw out any secondary functionality out the window from day 0. Make it work, then add flowers and shit (note to self: need to make way for flowers and shit).

Nevertheless code quality is an important factor, if you can afford it. The top important things I outline in any new non-trivial project:
1. Spend 1-2 days bootstrapping it for best fit to the task, and well designed security, mocking, testing and extensibility.
2. Choose a stack that you'll most likely find good cheap devs for, in that region where you'll look in, but also a stack that will allow you to spend most of your time writing software rather than learning to code in it.
3. Talk to peers. Listen when they tell that your idea is stupid. Listen to why it's stupid, re-assess, because it most probably is stupid in this case.
4. Give yourself a good pep talk every morning, convincing you that the choices you've made starting this project are the right ones and that they'll bring you to success. Because if you started such a project already, the most efficient way to kill it is to doubt your core decisions.

Once it's working badly and with a ton of bugs, you've already succeeded in actually making it work, and then you can tackle the bugs and improvements.

Some dev is going to hate you for creating something horrific, but that horrific thing will work, and it's what will give another developer a maintenance job. Which is FAR, far more than most would get by focusing on quality and features from day 0.

You wouldn't download a house

I heard you guys like rubber ducks. Here is a Tomato Duck.

First day at new job, let's go and see how this is going to go! I'll finally be able to call myself a professional linuxer 🙌😄

In these floods of anxiety and depression, coding is the only thing that is keeping me from sinking... <3

Memories...

The moment when you start looking into Open Source, view contributors out of curiosity and pick one at random, view his work only to find out that the guy has been developing software since the 1980's before your parents were even married.

Holy shit.

Le me: "my code is awesome! The way I did XY and Z is insanely cool, efficient, and maintainable."

Le Boss: "yeah so let's schedule a code review next week."

Le me : "... fuck, Fuck, FUUUUCK!"

Internal Screaming