Lobsters is a community-driven platform for sharing and discussing links to articles, tutorials, and projects related to technology and programming. Readers can learn about a wide range of topics, from software development and system administration to cybersecurity and artificial intelligence. With user submissions, comments, and voting, Lobsters provides a platform for collaborative learning and knowledge sharing among technology enthusiasts.

Lobsters

The Makefile effect describes the phenomenon where engineers copy and tweak existing, often complex, tools instead of creating new solutions from scratch. This practice, while practical at the point of solution, can reveal underlying issues in tool design, leading to inefficiencies in debugging, limited learning, and security vulnerabilities. Tool designers should be aware of this effect and strive to minimize it to improve usability, learning, and security.

Be aware of the Makefile effect

<p>For me, using <a href="https://taskfile.dev/" target="_blank" rel="noopener nofollow">go-task/task</a> took away the frustration of creating a Makefile from scratch…
The Taskfile schema is simple enough to use and remember.</p>


<p>From my years of doing MFC/C++: yes, the API was ugly, broken in many ways, hideously complicated, but if you used Visual Studio, you had access to a suite of generators and other tooling that made it livable.  Stuff like SOAP had wsdl that popped out a fully functionality API suite with a few command line params (we have Swagger today but it’s not the same).
One thing I do not see much of in the modern programming community is tooling and generators.  Of course, programmers copy/paste the last project.  Who wants to deal with all that boilerplate?</p>
