Drunk Post: Things I've Learned as a Senior Engineer
The Substack article, provocatively titled "Drunk Post: Things I've Learned as a Senior Engineer," was unfortunately inaccessible, leaving readers to fill the void. The comments section exploded with candid, often contentious, takes on programming languages, career longevity, interview practices, and personal finance for developers. This discussion became a spirited, unfiltered "drunk post" in its own right, sparking debates across the spectrum of developer experience.
The Lowdown
The original Hacker News post, titled "Drunk Post: Things I've Learned as a Senior Engineer" from Luminousmen Substack, proved to be an unexpected blank slate as the article content was unavailable. Despite this, the provocative title and implied subject matter ignited a lively and opinionated discussion among Hacker News commentators. Rather than being deterred, the community took the opportunity to share their own "drunk post" style wisdom, covering a wide array of topics pertinent to senior engineers and the tech industry at large.
- Language Philosophy: Strong opinions emerged on the utility of dynamic versus static languages, with some advocating for the former's flexibility (especially with gradual typing) and others decrying it for "significant" projects. The relative merits and roles of Java, Rust, and Go in the modern development landscape were also debated.
- Career & Code Impermanence: Many contributors reflected on the fleeting nature of software, noting that most code has a short lifespan and that a developer's true legacy lies outside their professional creations. This led to questions about the perceived "significance" of one's coding efforts.
- Industry "Cults" & Interview Critiques: The discussion touched on the "cult-like" aspects of methodologies like TDD and Agile, and even entire startup cultures. The efficacy and fairness of current software engineering interview processes, particularly those heavy on algorithms and data structures, were also critically examined.
- Personal Finance for Engineers: A significant thread provided detailed, actionable financial advice for young, high-earning engineers aiming for early retirement (FIRE), which in turn generated debate about the feasibility and sacrifices required for such a path.
Ultimately, the absence of the original article transformed the Hacker News comments into an unfiltered, collective outpouring of senior engineer insights, gripes, and advice, providing a rich, albeit fragmented, digest of industry wisdom.
The Gossip
Lingual Lodes & Lifespans
The debate over programming languages was fervent, with some asserting that dynamic languages are unsuitable for "significant" projects, while others championed their flexibility, especially with gradual typing. Java was lauded as a "shitty programming language that's good at almost everything," with Rust being proposed as its true evolution, and Go as a similar, simplified alternative. A deeper philosophical thread questioned the actual "significance" and longevity of any code, suggesting most work has a short shelf life and little lasting legacy.
Cultish Cultures & Cringeworthy Critiques
Many commenters resonated with the idea of certain industry practices and environments feeling "cultish," specifically citing TDD, Agile, Scrum, and startup cultures where charisma often trumps evidence. The interview process for engineers also came under fire, with participants questioning the relevance of trivia-like algorithm questions compared to other professions' hiring practices.
Financial Futures & FIRE Fallacies
A popular thread detailed comprehensive financial advice for young, high-earning software engineers, advocating for aggressively maxing out 401ks, HSAs, and IRAs, alongside building significant emergency funds, with the goal of achieving early retirement (FIRE). However, a counter-perspective quickly emerged, highlighting the extreme frugality, lack of dependents, cheap hobbies, and low cost of living required to make such an early retirement plan realistic.