About Lawrence Lockhart Jr
Lawrence Lockhart Jr. is a Developer Advocate at Vaadin, a Finnish company that builds solutions for Java-based web developers. He transitioned into tech through a coding bootcamp called Launch Code and previously worked as a fullstack developer at FedEx Services before joining Vaadin in August of the previous year.
Episode Summary
- Lawrence explains the role of Developer Advocate at Vaadin, emphasizing that it's a non-standardized role that varies by company and involves advocating both for the company to developers and for developers back to the company.
- He describes his diverse daily activities including conference talks, social media management, technical writing, community engagement, and preparing for major conferences like Dev Nexus in Atlanta.
- Lawrence discusses the challenge of transitioning from the structured environment of traditional software development to the more fluid, multi-responsibility nature of developer advocacy.
- He shares his simple whiteboard productivity system with three columns: 'Today', 'This Week', and 'Long Term' to manage varying responsibilities and timeframes.
- The conversation covers the importance of contextualizing advice based on the advisor's background and the recipient's current situation, using examples like LeetCode preparation and productivity systems.
Key Takeaways
- Developer advocacy requires building trust with the developer community by being authentic and providing genuine value rather than just selling products.
- When transitioning between roles with different structures, create your own organizational system that works for your brain and situation rather than forcing digital solutions that don't fit.
- Always contextualize advice you receive by considering whether the advisor's background and situation align with your own circumstances.
- Success in developer advocacy comes from balancing multiple time horizons and responsibilities while maintaining focus on both short-term deliverables and long-term relationship building.
- The key to managing unstructured work is creating visible, simple systems that get tasks out of your head and onto a manageable tracking system.
Productivity & Success Habits
Lawrence Lockhart Jr. has developed a surprisingly simple yet effective productivity system that helped him transition from the highly structured world of software development at FedEx to the fluid, multi-faceted role of developer advocacy. After struggling with the lack of structure that came with leaving the regimented Sprint-based development environment, Lawrence discovered that analog solutions work best for his brain. His entire productivity system revolves around a whiteboard with three simple columns: 'Today' for absolute must-dos, 'This Week' for everything that must happen within the week, and 'Long Term' for future items that don't require immediate stress or attention.
What makes Lawrence's approach particularly effective is his evening review ritual and the way he handles task rollover. As he explains, 'Every night I review it once and make sure I've checked off my things for the day if I have it it gets roll over to the next day with a star because now this is high priority that was a yesterday thing.' This system allows him to manage the unique challenge of developer advocacy, where responsibilities span from daily social media engagement and community interaction to long-term conference preparations and content creation. Lawrence emphasizes the importance of finding productivity solutions that match your personal context, noting that sometimes popular methods like Pomodoro can actually be counterproductive: 'Sometimes Pomodoro is the worst thing that I could possibly do because I've gone by 25 minutes but I'm now in a Zone the worst thing I can possibly do is break it up and then have to get back into the Zone.'
Final Thoughts & Advice
Throughout the conversation, Lawrence emphasized several key principles that have guided his remarkable career transitions from restaurant industry to supply chain management to software development and finally to developer advocacy. His most fundamental advice centers on honest self-analysis and contextual learning: 'You have to be able to honestly analyze you and I knew even with all the excitement of being in Tech now I wasn't growing all at all not a lake so as quickly as I could I got enrolled into a camp.' He stresses that when receiving advice from others, it's crucial to consider the context of the person giving it and how it relates to your current situation and goals.
Lawrence's philosophy is built on unchanging fundamentals that transcend career changes. He believes deeply that 'if one person has learned it and done it there's nothing about me that I can't learn it and do it as well.' This growth mindset, combined with his faith-based approach and commitment to doing right by others, has enabled him to successfully reinvent himself multiple times. His advice to those considering career changes or facing challenges is to embrace difficulties as growth opportunities: 'When we get all different little problems the thing is you're going to feel it... but then you need to be able to respond in a way to figure out what approach can I take to solve this knowing that when I solve this thing that solution... is going to give me different skill sets within my person that will be useful for bigger problems down the road and that's what we call growth.'
Notable Quotes
"You have to take advice Solutions about career about life about family take advice you get into context how does the advice given and the person giving it relate to who I am and where I am"
— Lawrence Lockhart Jr He was explaining why generic productivity advice like using Notion or Pomodoro technique doesn't work for everyone
"Developers don't like to be sold to period even when they have to buy something they don't want to be sold to but they will listen to a recommendation from a trusted friend"
— Lawrence Lockhart Jr He was describing the key principle behind effective developer advocacy and building trust with the developer community
"There is definitely without question no typical day or week... it is a role that is not really standardized it's not like you can go into college and major in the Devo"
— Lawrence Lockhart Jr He was explaining the nature of developer advocacy roles and how they vary significantly between companies