Mullet: The Skill for Job Security

(github.com)

10 points | by russell-dot-js 9 hours ago ago

2 comments

  • phillc73 5 hours ago ago

    A seminal project of the generative AI era.

  • russell-dot-js 9 hours ago ago

    In the ever-evolving world of agentic development, the strain of justifying our existence as developers is load-bearing. CFOs want to see a positive ROI in our organizations' investments into LLMs, and made up metrics like "features shipped" and "uptime" are subjective.

    Software engineers at the forefront of creativity and progress know that the only meaningful measure of productivity is lines of code. It's a number, it grows, and tools like "ponytail" are directly impacting our livelihood.

    For years, we've specialized in creating systems that only we know how to maintain, ensuring we never have to search for a new job again.

    mullet is the seasoned developers' answer to ponytail.

    Built for those of us who know your system isn't trustworthy or production-ready if it doesn't include at least 5 different programming languages, mullet helps ensure that at least 10% of all features include raw assembly that runs in the JVM, a stored procedure, or anywhere else you're clever enough to ship it.

    mullet also embraces WET — Write Everything Thrice. Everyone knows their initial implementation isn't trustworthy, and the only way to truly master a business domain is to write the same logic at least 3 times. WET ensures that you never know which of your 3 implementation gets called, or when, by utilizing an innovative "random number generator" (patent pending) to decide which code gets to run at any time.

    Why do in 2 lines of code what you can do in 2,000? Because you didn't just make your on-call teammates spend their weekend debugging your outage — you made sure they could only fix it by adding at least 20,000 lines of code. You saved jobs, and that takes leadership.