About my time in Split, Croatia; about Schengen rules for travellers, and Uber outside of the US
My name is Dmitry Vinnik, and currently, I am a Lead Software Engineer at Salesforce. I have been in the industry for quite some time now, and I have had a pleasure to work with and to meet amazing people. I learned a lot from them (and continue learning today). Fortunately, it brought me to my true calling of sharing these lessons with others.
One of the ways for me to share has been public speaking. I have been giving talks at conferences and user groups since 2017. From the very beginning, my goal was to make developer's lives easier by showing simplicity in complex problems.
This search for simplicity is why my topics of interest have been developer relations, developer wellness, software quality and software design. Although every topic in this list is enormous, I believe that only by discussing all of them, developers can simplify their work, so they can focus on what matters most to them.
Why starting a blog?
While I have been a frequent speaker in the past few years, I had neglected the written word. While talks (especially those recorded) can reach a couple of hundreds of people, I (hopefully) can reach more people through writing. Ultimately, I want to try new ways of producing content which could be useful to developers.
What is Proactive Developer?
I recently read a book by Stephen R. Covey, "The 7 Habits of Highly Effective People", and it made quite an impression on me. This book has a lot to teach about success and provides a detailed guide to personal change.
One of these lessons (or "habits") is the idea of proactivity. Stephen Covey says that a proactive person is someone who, faced with adversity, chooses and focuses his or her efforts on the response. In other words, the proactive person does't care about things he or she can't control (i.e. "stimulus"), and instead makes a change where he or she can affect something.
For instance, if my cloud provider is down, I don`t want to start running around, looking for who is at fault. I would instead focus on mitigating the problem and implementing ways to minimize the impact of future failures (and there will always be future failures).
This idea of proactivity is what I want to apply to software development, developer wellness, and teamwork. Instead of worrying about things we cannot change, we should start making changes where it counts. I hope to share my thoughts on how we can do it.