I've updated my setup! Added another screen. I'm ready for battle with the bugs.

I just encountered this:

switch (boolean) {
case true:
…
break;
case false:
…
break;
}

Really? 😂

You got it.

Me, whenever i work with something other than java: "Wow, this could be done so much easier with java"

After job Interview,
We will come in contact with you later that week.
*Later that week*
You've got mail

Highpayingjob@gmail.com
Job interview

You didn't get the job.
Your didn't Meet out requirements.

Sincerely us.

*5 minutes later*

Highpayingjob@gmail.com
Job interview

We must apollogize, we've sent you the wrong mail.

Sincerely us.

*5minutes later*

Highpayingjob@gmail.com
Job Interview.

You werent good enough at our Interview.

Sincerely us.

*Me*
What. The. Fuck.
Just happened...
WHAT THE FUCK!
2 REJECTIONS FROM THE SAME COMPANY?! IN JUST 10 FUCKING MINUTES!

That moment that you can help a customer with a highly technical question for the first time because you read something a year or more ago about that.

That feels awesome!

Just tried to double tap a Facebook comment to "like" it.

Client: it's not working
Me: clear your cache
Client: what's that
Me:it's a way of cleaning the files of your computer to get new ones.
Client: I cleaned my mac

I mean she literally got cleaning wipes ... and cleaned her computer

P.s I told her all this before and how to many, many times

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.

He's got a valid point

😂😂😂

Hot fix of a production bug!

The only useful indicator of code-quality is the wtf-per-minute scale.