Leaving big tech to build the #1 technology newsletter | Gergely Orosz (The Pragmatic Engineer)

The primary motivations included a promise to himself to take a risk after Uber's layoffs, a desire to be in charge and have more autonomy, and a realization that he enjoyed the writing and sharing aspects of his work more than managing large teams.

Initially, Gergely committed to one in-depth post per week. He later increased this to two posts: a weekly in-depth article on Tuesdays and a more timely 'scoop' on Thursdays.

Key downsides include loneliness from lack of colleagues, the surprising stress of managing a business and external validation, and the difficulty of taking meaningful time off due to subscriber expectations and the need for consistent high-quality content.

He uses a script to block distracting websites, sets 20-minute timers for focused work, and finds that external deadlines or the end of the workday naturally increase focus. He also mentioned using apps like 'Center' that use video cameras to encourage productivity.

He enjoys having an open calendar with very few meetings, allowing for deep focus time. He also loves the entrepreneurial aspect, the creative freedom to experiment, and the feeling of being in charge of his work.

Unlike traditional companies, a newsletter is tied to the individual creator, making a direct sale difficult. Potential paths include building a larger media company with employees or continuing the direct creator model, which offers less of a traditional 'exit'.

While it appears rapid, it was built on six years of consistent blogging on 'The Pragmatic Engineer' and establishing credibility. When he launched the newsletter, he already had an engaged audience familiar with his content.

Build depth in your field first, share your knowledge consistently, establish a cadence, and be open to trying new things. Start small with side projects and focus on controllable goals.

Gergely emphasizes that his initial blog started before his extensive tech career. While pedigree from respected companies can help, the core is continuous learning, sharing knowledge, and building expertise over time, regardless of the starting point.

Writing allows for efficient scanning and quick access to information, which is crucial for technical content. Video, especially long-form, is time-consuming and difficult to scan, making it less ideal for deep learning in fields like software engineering.

You can find Gergely at pragmaticengineer.com, which lists his Twitter, LinkedIn, talent collective, and investment companies. You can also sign up for his newsletter there.