Archive

The Dulin Report

Browsable archive from the WordPress export.

Results (42)

On the role of Distinguished Engineer and CTO Mindset Apr 27, 2025 The future is bright Mar 30, 2025 2024 Reflections Dec 31, 2024 The day I became an architect Sep 11, 2024 Are developer jobs truly in decline? Jun 29, 2024 Form follows fiasco Mar 31, 2024 Thanksgiving reflections Nov 23, 2023 Working from home works as well as any distributed team Nov 25, 2022 Book review: Clojure for the Brave and True Oct 2, 2022 The Toxic Clique Sep 28, 2022 All developers should know UNIX Jun 30, 2022 Good developers can pick up new programming languages Jun 3, 2022 Java is no longer relevant May 29, 2022 There is no such thing as one grand unified full-stack programming language May 27, 2022 Best practices for building a microservice architecture Apr 25, 2022 Kitchen table conversations Nov 7, 2021 What programming language to use for a brand new project? Feb 18, 2020 On elephant graveyards Feb 15, 2020 Microsoft acquires Citus Data Jan 26, 2019 Teleportation can corrupt your data Sep 29, 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 The technology publishing industry needs to transform in order to survive Jun 30, 2017 Why it makes perfect sense for Dropbox to leave AWS May 7, 2016 LinkedIn needs a reset Feb 13, 2016 In memory of Ed Yourdon Jan 23, 2016 IT departments must transform in the face of the cloud revolution Nov 9, 2015 We Live in a Mobile Device Notification Hell Aug 22, 2015 What Every College Computer Science Freshman Should Know Aug 14, 2015 On Maintaining Personal Brand as a Software Engineer Aug 2, 2015 Book Review: "Shop Class As Soulcraft" By Matthew B. Crawford Jul 5, 2015 The Clarkson School Class of 2015 Commencement speech May 5, 2015 On Managing Stress, Multitasking and Other New Year's Resolutions Jan 1, 2015 Software Engineering and Domain Area Expertise Nov 7, 2014 Infrastructure in the cloud vs on-premise Aug 25, 2014 On anti-loops Mar 13, 2014 On working from home and remote teams Nov 17, 2013 Thanking MIT Scratch Sep 14, 2013 Thoughts on Wall Street Technology Aug 11, 2012 Scripting News: After X years programming Jun 5, 2012 Eminence Grise: A trusted advisor May 13, 2009

Eminence Grise: A trusted advisor

May 13, 2009

While reading "The House of Cards" I came across this:




From time to time over the years, [Alan] Schwartz had thought about giving up his management position at the [Bear Sterns] firm and assuming the mantle of eminence grise in the M&A world, not unlike a Felix Rohatyn or Jack Levy, who were well-regarded senior M&A bankers without a management role.





I did some homework on the meaning of eminence grise and found that what it boils down too is "trusted adviser." Aldous Huxley wrote "Grey Eminence" -- a biography of Cardinal Richelieu's trusted adviser.



I've been thinking about the direction of my career over the past few years. 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. In my mental exercises I've come up with several scenarios of accomplishing this.



Patiently sticking with the same vertical at the same employer and gaining the trust of the management. In this scenario I become a key technologist responsible for the well being of a specific piece of the company's IT systems.



Alternatively, a consulting or a consulting-like approach may work too. With this career development path I see myself focusing on the horizontal aspects of technology while advising client(s) across different industry verticals.



First scenario is less risky and more secure. Second scenario would require me drawing on my past consulting experience and being more proactive at marketing myself. In the first scenario, I am risking being looked over when it comes to promotions in a company where a corporate structure is set up for IT management roles rather than engineering. In the second one, I am risking job stability and there is a chance of becoming a Jack of all trades but master of none.



There are obviously pros and cons to both approaches, a lot more than I had just described. Is there another scenario ? A road less traveled, perhaps ?