Das hier hab ich noch auf einam alte Backup gefunden.
(Zu singen auf die Melodie von "50 ways to leave your lover")
You know I am a systems engeneer,
I care for backends systems and so on.
and I can tell you stories and can swear,
there are fifty ways to ruin you software:
you did not verify that input
and now you got an output bug.
Did you check that access, dude?
And now you are on you-tube
yeah, fifty ways to ruin you software:
what did you deploy, Roy?
We have no plan, Stan
Dont touch that Mouse, Klaus
There is trouble ahead.
Did you us the template, Kate?
I must confess,
we have no process,
but now its to late.
we did not check that file size,
and now we are with no space left on device.
We did not finally { close() }
and now we are without hose.
some of the fifty ways to ruin you software.
I found something that gave me a shock,
but as I checked I did not find a log.
Sometimes We used to many threads
and in the end our code was dead.
and more from fifty ways to ruin you software.
what did you deploy, Roy?
We have no plan, Stan
Used that cryptographic key, Lee?
There is trouble ahead.
Did you close that tag, jack?
I must confess,
we have no process,
but now its all black
After Investiagtion there is no excuse
we did not protect us against abuse.
And that code was slow as toad,
as we did not check the overload.
some of the fifty ways to ruin you software.
I wonderd and checked all night
that random number, it was always eight!
we are so cute and use another tweak
and now we got a memory leak.
yeah, fifty ways to ruin you software.
what did you deploy, Roy?
We have no plan, Stan
Dont touch that Mouse, Klaus
There is trouble ahead.
Did you us the template, Kate?
I must confess,
we have no process,
but now its to late
Materialsammlung
you did not check but used some tool.
that made things worse, you are a fool.
That new design, what did you find?
Your tester there is colorblind!
All you data was save in the cloud
and then the lights went out.