During the interview process, I observe the people who are interviewing me. I ask them non-work questions to get a feel for who they are as individuals. How can you use this? Make sure that the people who are conducting interviews are exemplary of the culture you want to promote. Like attracts like. But, as I was once a hiring manager, I discovered that most candidates will blindly accept a job offer, no matter what culture is presented in the interview process. By the time someone submits a resume, they’re already sold on you. If it’s culture you want to promote, you need to establish this during your advertising process. And make sure that the culture you want to present actually exists in your company. If it doesn’t, you’ll have high turnover.

(1) is the product interesting to me? (2) do i like the people who work there? (3) can they pay me enough? (4) how professional are they?

“By maintaining a junior role while my own output is objectively on par with my senior friends at work, I'm effectively short-changing myself.” Yes, you absolutely are. Stop it. I’m going to break with the crowd and tell you to seek out new employment. Just try it. I bet you will be surprised by who is willing to hire you. The problem with your current situation: a precedent has been set and everyone sees you as that junior person whether it is true or not. And you may be reflecting their feelings onto yourself, believing that you are what they see, not what you actually are. Three years at one company is too long. Especially if you are starting out. Go seek new employment. Set strong boundaries. You will surprise yourself. Do not accept what you’ve been told you are. When you start at a new company, you get a reset and a chance to create a perception that fits who you are now, not who you were three years ago.

That is cool, Zenobius. And ironic. I’m using Django right now. I also crashed through the back door of the software industry several years ago. It’s a long/humorous story for another time.

Not unit testing. It’s not that noticeable when you have a small project, but as things get bigger and more complicated, the work required for end-to-end testing increases exponentially. Not setting a clear end goal before you start. I’ve completed many projects, but the one I didn’t had a fuzzy end goal that I told myself I would eventually define. I never did. If the goal is crystal clear, it will motivate you to keep going.

Walk away for 20 minutes, do something else. If task is too complex, break it into smaller tasks and combat each of them seperately. If you are bored and can’t seem to finish, focus your thoughts on the end goal and the reward.

There is no === operator in C#. == in javascript is not similar to == in C# === in javascript is similar to == in C#

+1 on VSCode. Concise design, lots of power, and not bloated like Visual Studio.

Django. I wanted to be a rebel and use Flask, but eventually gave in. It’s hard to ignore a well designed/supported/documented project.

Do some research on modeling languages for behaviors and behavior trees. You are on the right track with idea 1. Don’t destroy actions, cache them for later use.