When I purchased my first vehicle, I knew exactly what I wanted, and the price I was willing to pay for her. I scoured car search engines until I found one within my price range and preference.

I contacted the seller, but contrary to website information, they didn’t offer financing options. No prob. I let it roll off my back and continued my search elsewhere.

The next car I found was a newer model at a slightly higher price. This was my chance! I was excited to finally land this purchase. After a 90 minute drive to Manassas, Virginia, I discovered it sold minutes before I got to the dealership…

I was disappointed, but I had a contingency plan! There was an even newer model at a very big discount only two cities away in Rockville, Maryland. This time around, I researched prices and haggling strategies ahead of time. I got in touch with the dealership and as it turned out, the car they advertised was different from the one they had available. I ate the blessing and, with no potential cars, I decided to research auto loans.

After a couple sleepless nights dashing across car buying articles and videos, I realized I would have gotten screwed on the APR if I applied through a dealership. So, I got a loan through my credit union instead.

I also learned credit unions provide auto loans! WHO KNEW!

With this, I was able to get the funding needed to buy a car; cash in hand. I returned to my first choice, obtained a loan, and within a few days, I was behind the wheels of my new (used) baby!

The key to my success was resilience, and programming takes a lot of it. Problem-solving isn’t always cut and dry. As you approach problem-solving, you will run into innumerable walls. Sure, some parts of the process may come easily, but others may not.

There will be lines of code that cause an unfamiliar error. The size of the error can range from a missing semicolon to missing statements for accessing specific libraries. Or maybe there’s a plugin missing in your IDE. The possibilities are endless! Even while researching these errors, you might take a few minutes or sift through solutions for hours. It’s up to you to stay strong, note what needs to be done, and do what can be done.

Documenting your process can help you keep track of your progress as you resolve issues. You’ll better understand how to repair or avoid the issue again in the future. As an added bonus, the time spent troubleshooting and debugging doesn’t feel wasted.  You’re still learning and becoming better at what you do. And most importantly, you’re building your resilience.

Sometimes when solving difficult problems, we start to develop tunnel vision because we believe we have reached a final solution. Especially during long-term projects. That’s why it is important to take time, track your progress, and trust the process.

I thought getting a car was as easy as finding one and signing some papers to pay her off over time. It was a tough process, and at times I felt like settling for an easier purchase. But I knew the only way to the finish line was to walk straight ahead. No matter how tough it gets, stay focused and move forward.

Peaceful in action, never in mind
CodingFanatic