Archive

The Dulin Report

Browsable archive from the WordPress export.

Results (46)

On the role of Distinguished Engineer and CTO Mindset Apr 27, 2025 The future is bright Mar 30, 2025 2024 Reflections Dec 31, 2024 Working from home works as well as any distributed team Nov 25, 2022 Good developers can pick up new programming languages Jun 3, 2022 In most cases, there is no need for NoSQL Apr 18, 2022 Kitchen table conversations Nov 7, 2021 Returning security back to the user Feb 2, 2019 Let’s talk cloud neutrality Sep 17, 2018 What does a Chief Software Architect do? Jun 23, 2018 Leaving Facebook and Twitter: here are the alternatives Mar 25, 2018 When politics and technology intersect Mar 24, 2018 Nobody wants your app Aug 2, 2017 The technology publishing industry needs to transform in order to survive Jun 30, 2017 Rather than innovating Walmart bullies their tech vendors to leave AWS Jun 27, 2017 I tried an Apple Watch for two days and I hated it Mar 30, 2017 Copyright in the 21st century or how "IT Gurus of Atlanta" plagiarized my and other's articles Mar 21, 2017 Emails, politics, and common sense Jan 14, 2017 Here is to a great 2017! Dec 26, 2016 What I learned from using Amazon Alexa for a month Sep 7, 2016 Amazon Alexa is eating the retailers alive Jun 22, 2016 In Support Of Gary Johnson Jun 13, 2016 Why it makes perfect sense for Dropbox to leave AWS May 7, 2016 JEE in the cloud era: building application servers Apr 22, 2016 In memory of Ed Yourdon Jan 23, 2016 Operations costs are the Achille's heel of NoSQL Nov 23, 2015 Banking Technology is in Dire Need of Standartization and Openness Sep 28, 2015 I Stand With Ahmed Sep 19, 2015 Top Ten Differences Between ActiveMQ and Amazon SQS Sep 5, 2015 What Every College Computer Science Freshman Should Know Aug 14, 2015 On Maintaining Personal Brand as a Software Engineer Aug 2, 2015 Social Media Detox Jul 11, 2015 The Three Myths About JavaScript Simplicity Jul 10, 2015 Your IT Department's Kodak Moment Jun 17, 2015 Big Data is not all about Hadoop May 30, 2015 Smart IT Departments Own Their Business API and Take Ownership of Data Governance May 13, 2015 Building a Supercomputer in AWS: Is it even worth it ? Apr 13, 2015 Microsoft and Apple Have Everything to Lose if Chromebooks Succeed Mar 31, 2015 Why I am Tempted to Replace Cassandra With DynamoDB Nov 13, 2014 Software Engineering and Domain Area Expertise Nov 7, 2014 Docker can fundamentally change how you think of server deployments Aug 26, 2014 Wall St. wakes up to underinvestment in OMS Aug 21, 2014 "Hello, World!" Using Apache Thrift Feb 24, 2013 Thoughts on Wall Street Technology Aug 11, 2012 Happy New Year! Jan 1, 2012 Eminence Grise: A trusted advisor May 13, 2009

2024 Reflections

December 31, 2024

2024 in Review: thoughts on aspirational goals


They say goals should be SMART: Specific, Measurable, Achievable, Relevant, and Time-bound. When I talk to students and early-career software engineers, I always tell them to also set aspirational goals. Aspirational goals are just a bit beyond achievable, and they are not time-bound. Set one aspirational goal and lots of SMART goals as a journey towards it.

I’ve been writing about my career for ages and always find it fun to look back at my old posts. Fifteen years ago, in 2009, I wrote about an aspirational goal that I had at the time:
My personality is such that I am always looking ahead of the current step and think about what I want to do next. In the 12 years of my career I’ve seen people who were trusted advisers to their respective business leaders. I always admired them and envisioned myself one day to be in such a role.

Reading about well respected people who shun management roles reaffirms my long-term goal of becoming a trusted adviser or a chief technologist to a visionary business leader

Since 2009, my aspirational goal has been to become a trusted advisor. It’s been driving my career growth for fifteen years. In 2024, realizing that becoming a Distinguished Engineer marked the culmination of my Trusted Advisor goal hit me like a rock. It marked an end of a meaningful chapter of my life. In a twist of irony, this epiphany also brought significant discomfort to me: it turns out I am deeply uncomfortable not having an aspirational goal.

So, for 2025, I am setting my next aspirational goal: to become a Chief Technology Officer (CTO). A CTO is a natural evolution of the “trusted advisor or chief technology” role I envisioned in 2009.

I don’t necessarily mean to become the CTO of a large publicly traded company. What I look forward to is a CTO-style role where I own a portfolio of software products and lead a strategic software initiative, whether within a larger company or leading a “small-ish” boutique or startup firm.

I say this, realizing I may crash and burn and never achieve this goal. The road to get there will be filled with trials, frustrations, and stress. The universe is going to push my buttons. But, boy, am I going to love the journey. Growth is never without pain; somehow, I crave every moment.

As a first step in this direction, I am excited to join the upcoming cohort of the Wharton Executive Education CTO Program. I look forward to exchanging ideas with Wharton thought leaders, industry experts, and senior executives to uncover insights that can drive organizational growth with technology.