https://github.com/morgangallant/mlaas
Simply the best way to instill a sense of urgency within your engineering team.
https://github.com/morgangallant/mlaas
hardcore-engineering memory-allocation
Last synced: 3 months ago
JSON representation
Simply the best way to instill a sense of urgency within your engineering team.
- Host: GitHub
- URL: https://github.com/morgangallant/mlaas
- Owner: morgangallant
- License: mit
- Created: 2023-01-10T16:54:38.000Z (over 2 years ago)
- Default Branch: trunk
- Last Pushed: 2023-01-11T04:27:12.000Z (over 2 years ago)
- Last Synced: 2025-03-15T07:55:26.476Z (3 months ago)
- Topics: hardcore-engineering, memory-allocation
- Language: Go
- Homepage:
- Size: 3.91 KB
- Stars: 2
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# MLaaS
Introducing Memory-Leaks as a Service! MLaaS is a simple, cost-effective strategy to keep your engineers shipping code as fast as possible.
Here's how it works:
- Add the MLaaS library to your existing Go server.
- At startup, simply call `go mlaas.Start()`. This can be done inside of your `init()` or `main()` function.
- Every hour, MLaaS will allocate 100MiB of memory (and of course, not free it!).
- If your engineer's don't deploy new versions of your server code fast enough, then your servers will crash after a little while! How long? Who knows, it's a suprise!
Benefits:
- Establish a culture of "hardcore" engineering within your team.
- Increases motivation throughout your engineering team to ship code quickly and often.
- Increases server load, which means your engineers will have to write better, more efficient code to compensate!
Disclaimer:
This is a joke. Please don't actually use this library in production. It's not a good idea. This was inspired by a memory leak that we've had in our production servers at [Operand](https://operand.ai) for some time now. Our memory graphs may resemble the himalayas, but to be frank, we're not in a huge rush to fix it, as long as we deploy new code every day or two, everything works fine!