EmbeddingGemma 2: an open, lightweight multimodal embedding model
deepmind.google·6d ago
AI Engineering
Hacker News·29d ago·5 min read
Don't call yourself an artisanal programmer
TL;DR
The author critiques the dichotomy between 'serious' engineers and 'artisanal' programmers, arguing that true engineering requires deep engagement with code for reliability. They express concern that the industry's shift towards rapid development undermines the importance of careful programming practices.
✦ Why It Matters
Prioritize thorough testing and code review to ensure reliability in your software projects.
Key Takeaways
- Challenge the use of 'artisanal' to describe serious coding practices.
- Advocate for clearer terminology in software development.
- Highlight the importance of reliability and maintainability in coding.
- Engage in discussions about the value of AI-free coding.
Full Summary
In the software development community, a divide has emerged between those labeled as 'artisanal programmers', who prioritize the coding process, and 'software engineers', who focus on end results. The author argues that this classification is misleading, as many who are considered artisanal are deeply committed to producing reliable and maintainable code.
They express concern that the term 'artisanal' diminishes the seriousness of their work, while 'vibecoding'—a more casual approach—has gained acceptance. Citing interviews from Hillel Wayne's crossover project, the author notes that many experienced engineers believe that not all software development qualifies as engineering.
The article emphasizes the need for clearer terminology to distinguish between different types of coding practices and to advocate for the value of careful, AI-free software engineering.