EmbeddingGemma 2: an open, lightweight multimodal embedding model
deepmind.google·6d ago
AI Engineering
Lobsters·Aug 9·5 min read
I got an email about resistance
TL;DR
A recent email critique highlights a tension in the author's writing about the decline of deep thinking in software. The critic urges a more active resistance rather than passive acceptance of this trend.
✦ Why It Matters
Consider your role in the software industry and decide whether to adapt or actively resist current trends.
Key Takeaways
- Understand the historical context of automation in your field.
- Guide junior engineers through industry changes with caution.
- Avoid inciting radical actions that could harm careers.
- Use your influence to promote informed decision-making.
Full Summary
William Murray critiques Sean's writing for being overly resigned to the changes in software engineering due to automation, suggesting that engineers should either resist or seek alternative work. Sean responds by acknowledging the historical significance of the current moment, likening it to the Industrial Revolution, where craftspeople faced similar threats from automation.
He emphasizes the importance of guiding junior engineers through these uncertain times rather than inciting rebellion, arguing that many lack the experience to navigate the consequences of radical actions. Sean expresses concern that calls for resistance could harm vulnerable engineers' careers.
Ultimately, he aims to provide a voice of caution and pragmatism to help others make informed decisions in a precarious landscape.