I thoroughly enjoyed the thread Dean weaves through the rise of the CIA, its big personalities, high tech, and tradecraft.
As the nation realized its decade-long dream of reaching the moon, the CIA undertook another near-impossible goal of recovering a Soviet nuclear sub three miles below the surface of the Pacific Ocean, all under the cover of a fake Howard Hughes-backed undersea mining operation.
Nonfiction storytelling at its best. Grann draws on extensive research to tell a gripping account of the Osage Indian murders. In 1920s Oklahoma, the frontier was closed, but the Indian killing continued as corrupt men sought to separate the Osage from their newfound oil wealth. During a four-year reign of terror mostly forgotten to history, scores (or by some accounts, hundreds) of Osage died under mysterious and often violent circumstances. The investigation of these deaths built momentum for the organization that became the modern FBI.
The response to my previous post was amazing. Within a week, I had met with people from a half dozen companies trying to find the best fit. By the end of the next week, I had a great offer in hand with a company where I felt I could make a real impact.
Then I met Nick one Wednesday for lunch. Over tacos, we reflected on how the development landscape had changed in the twenty years since we'd started, especially on the frontend. Though still rapidly evolving, the rise of design systems and component frameworks makes it feel like we're closing in on the reality of a shared process between designers and developers. Nick works at InVision, a company who has been enabling designers and developers to collaborate better for years.
Nick asked if I'd be interested in exploring a role there. I told him that I definitely would, but I already had an offer in hand, and I didn't want to string that company along indefinitely. I was hoping to give them an answer by the end of the week. He said he understood and would talk to his boss and see what they could do.
The next 48 hours were a blur. Thursday, I met with Kirby, Nick's manager, and we had an engaging conversation about the product, the tech stack, and scaling engineering teams. That evening I got a call from Clay, an InVision recruiter, asking my availability for interviews the next day. I cleared my calendar, and he scheduled five back-to-back interviews via video calls on Friday. I've run the interview gauntlet many times, but never have I had a series of effortless conversations as these.
By 3pm that day, I had received an offer to join InVision as a Principal Engineer working on Studio. I was thrilled to accept.
I'm so happy to be working on such a cool app for a great team at an incredible company.
Larson tells the incredible story of hubris, disaster, and loss behind the fall of Galveston as America's premier Gulf Coast city from the perspective of several residents, most notably Issac Cline who oversaw the nascent Weather Bureau office there. Well-paced and immersive, it's an entertaining read.
I picked up this book because I wanted to understand better the rise of the world's richest man and his legacy — a business legacy that lives on in corporate logos we see every day and a family legacy that extended all the way to the Lieutenant Governor's office of my home state of Arkansas.
Taking nothing away from Chernow's meticulous research and understated storytelling, the actual life of John D. Rockefeller seems rather dull. There was the ongoing tension between his Northern Baptist faith and his desire to accumulate and steward wealth, but the far more entertaining portions of the book follow Rockefeller's unresolved tension with his bigamist father and conflicts with Ida Tarbell and Teddy Roosevelt.
Perhaps the book's greatest value is its telling of, primarily through the life of one man, the transformation of American culture and mainline Protestantism. From Moody and Fosdick to Jung, Rockefeller, his family, or his surrogates were riding the same streams of the oncoming wave of Progressivism at the turn of the last century.
Building on his previous work in Liberal Fascism, Goldberg makes the case that tribalism, populism, nationalism, and identity politics aren't new phenomena but merely evidence of civilization returning to its natural state, like an overgrown garden. Following the thread of Lockean and Rousseauian thought, he argues that modern populism is really the same Romantic reaction to the Enlightenment that never really faded, now dressed up as reality TV.
Well-researched (the appendix is nearly a fifth of the book's bulk) and well-written with Goldberg's usual wit and sarcasm, it's an entertaining read.
A vivid history of Comancheria, its conquering of and collision with other cultures in what is now New Mexico, Texas, and Oklahoma. Though disturbing and shocking in places, the story could not be told without acknowledging the brutality executed by and on the Comanche people.
Born in Southwestern Oklahoma and now living in North Texas, I felt a special connection to the people and landscape. My mother's family is from Comanche County, Oklahoma and farmed over three hundred acres of land once a part of that set aside as the last vestige of grassland once ruled by perhaps the most adept cavalry in the world.
Twenty years in, I'm still thankful to make a living doing what I love to do: developing software and building engineering teams. I enjoy the creative process, solving problems, and defining & refining the way we work to ship code to provide value.
Due to some harsh startup realities, I'm unexpectedly looking for my next opportunity to join and grow a great engineering team.
I'm T-shaped, a generalizing specialist, a Jack-of-all-trades, master of some. I'm driven by curiosity. You don't make it long in this line of work if you're not a lifelong learner.
I don't like to work alone. I like being stretched by people with more experience and specialized knowledge as much as I love mentoring and sharing what I've learned. I've gained some experience in:
- Platform, APIs - I helped build and scale the GitHub API, powering many features of the product and enabling an entire ecosystem to build value upon GitHub.
- GraphQL - I haven't been this genuinely excited about a technology since the early days of Rails. As a long time REST nerd, I was skeptical about the promise of GraphQL early on, but having been a part of three implementations now, I've come to appreciate the accelerant it can be for frontend teams.
- React - Returning to the frontend after years of building APIs has been a fun challenge. In the last couple of years, I've learned a ton about how to build a manageable frontend architecture with React.
- Process - I've written about process because continual improvement is important to me. Success isn't individual, and the way a team works is a function of its mission and its makeup. Process has to be continually shaped and refined.
- Leadership - As a technologist, as a business owner, and as an engineering manager, I've learned the value of collaboaration, empathy, and leading without authority. I've helped build teams from scratch and scale teams into groups of teams.
My ideal role
I've worked as an individual contributor. I've led small teams, large teams, and teams of teams. Each role has its own unique set of benefits and challenges. Ideally, my next role would afford me opportunities for:
- Technical leadership. Pure personnel management does not interest me. I enjoy leading and serving a team, but there has to be technical content to the work I do. I like to bring technology into service of business goals, clear roadblocks, bring clarity, and provide space for others to do their best work.
- Opportunities to learn. As a lifelong learner, I'm my most content when I'm in a regular rhythm of learning, doing, and sharing. Before accepting a role, I want a clear picture of opportunties to learn something new.
- Stability. At this stage in my career, my family gets my nights and weekends, which rules out most seed stage startups. I've been apart of stable growth stage businesses and tumultuous public companies. For me, stability means near term financial runway and a values-driven culture that can cohere as the company grows.
If you're looking for proven technical leadership to help build your engineering team, let's connect.
Perhaps my favorite Chernow book to date, which is saying a lot. I'm not sure if it's because I learned much about Grant (growing up in the South, I knew little of his life before Vicksburg and after Appomattox, even though he served two terms as President) or because I found him relatable. Loyal to a fault, a little too eager to trust, he was a man ill-equipped for ordinary life yet seemed to thrive in a crisis.
As always, Chernow employs a full cast. The focus is on Grant, but by the end I felt invested in Washburne, Rawlins, Sherman, and even the hard-to-like members of his family.
Having loved the film of the same name, I was delighted to find the book devote so many chapters to the lives of these women at Langley during and just after WWII. The book goes deeper as you would expect in a historical narrative, but it also goes much broader than the movie. It includes fascinating accounts of women like the brilliant Dorothy Hoover who helped design wings for jet planes.
The author holds in tension two compelling aspects of these stories: the struggle against segregation, sexism, and the "stubborn underbrush of low expectations" alongside the remarkable account of these technologists, in their prime, good at their jobs who worked on some of the most incredible human endeavors of the twentieth century.