Lessons Learned: Reflections on my first year as a remote developer over 40.

Lessons Learned: Reflections on my first year as a remote developer over 40.

Ben Gardiner's photo
Ben Gardiner
·

4 min read

Featured on Hashnode

As a remote developer over 40 or "senior citizen" 😂, my first year in this field has been a unique and rewarding and at times challenging experience. It has been a journey of growth and development both professionally and personally.

I wanted to reflect on my journey and share some of the lessons that I learned along the way. I hope it might be helpful to anyone starting their web development career, but they are particularly relevant to those who, like me, have embarked on this journey later in life.

Here are some things I learned in no particular order

Eat your Vegetables

(Adventures in "Why didn't I learn this properly the first time?")

Every time I do something new, I realise more and more how important fundamentals are to understanding problems - abstractions make it easy to learn new tools but don't help you out when stuff breaks. HTTP Codes, the DOM, the react render loop, debugging, CSS, and promises. So respect your fundamental vegetables.

But yeah, remember it’s also not the end of the world if you don't remember the syntax of stuff - just make sure you have a good collection of notes and places to find things right quickly. And CSS grid is massively OP and I love it. In general, I like to use a grid for layout and flex things inside containers.

Learn.How.To.Read.The.Docs

(Helping you help yourself)

Dear god, it’s so important. Can be intimidating when you start out but make it your first stop on the road to understanding

I feel like now I can understand when people talk about how much they love certain technologies and then they say "and.. the documentation is amazing" or the "discord community is really strong" and how important that stuff is to DX.

Also trying to bridge that "assumed knowledge" part of some documentation can take a while but don’t get discouraged because when it clicks it means freedom.

Calling in the Bomb Squad

(Learning when to call for help)

Let’s face it we're determined people. We love the thrill of solving coding puzzles and conquering challenges on our own. But sometimes, we find ourselves in a tight spot where calling in "Code Brown" becomes necessary. Learning to recognize the right time to seek help is a skill worth cultivating.

When you reach out for help, make sure to come prepared with a list of what you've tried and your own thoughts on the matter. This way, you can maximize the value of the intervention and make the most out of the experience.

The "Cardboard Superman" technique (Borrowed from my colleague Dan). Sometimes, all it takes is borrowing someone for 5 mins to gain a fresh perspective. I can't tell you how many times I’ve been wrestling with a problem and started off with "Can you help me - Im stumped.., I don’t understand why it's broken... see I did this, then this, then this should be returning this... see, let me show you.... oh... dammit."

Remember, seeking assistance doesn't make you weak— done properly it makes you resourceful and accelerates your growth.

"Oops, I Did It Again!"

(Embracing Mistakes as Opportunities for Growth)

I recently read Extreme Ownership: How U.S. Navy Seals Lead and Win so with that in mind make sure you accept ownership. It's crucial to accept it without placing blame on others. Take ownership of your mistakes and view them as valuable learning experiences. By accepting responsibility, you demonstrate professionalism and a willingness to improve but also maintain control of your outcomes.

Be prepared to defend your code - when you PR make sure you have a logical, reasonable argument as to why you did something. Defending your choice beforehand can help you identify silly mistakes.

Try, Try Try not to make the same mistake twice. If you find this occurring make sure you get to the root cause and take action.

Remember, even the best web developers have their fair share of "oops" moments, so take it easy on yourself and don't compare your progress with someone else's. It really is super important to look back and see how far you have come, smile and be proud of yourself.

"404: Self-Care Not Found"

K, Imma just leave this here. All these things are ultra important and working from home you get to manage your own time which is great because you have no excuse not to do the following 😊

For those who are considering starting their web development careers later in life, I want to assure you that it is absolutely possible. My own experience as a remote developer in my forties has been filled with unique challenges and rewarding moments.

Remember, age is just a number. Accept responsibilty and don't blame others. The wisdom and life experience that we bring to the table can be invaluable assets in our web development pursuits. Embrace your unique perspective, and don't be afraid to follow your dreams.

Thanks for reading and "Stay El Positivo".

Did you find this article valuable?

Support coding in the sun by becoming a sponsor. Any amount is appreciated!

Beginner DevelopersremoteLearning Journeylearn codingover40
Â