this post was submitted on 27 Jul 2023
231 points (98.7% liked)

Programming Humor

3239 readers
1 users here now

Related Communities !programmerhumor@lemmy.ml !programmer_humor@programming.dev !programmerhumor@kbin.social !programming_horror@programming.dev

Other Programming Communities !programming@beehaw.org !programming@programming.dev !programming@lemmy.ml !programming@kbin.social !learn_programming@programming.dev !functional_programming@programming.dev !embedded_prog@lemmy.ml

founded 2 years ago
MODERATORS
231
DO NOT TOUCH (infosec.pub)
submitted 2 years ago* (last edited 2 years ago) by devil_d0c@lemmy.world to c/programminghumor@lemmy.world
 

Edit: so im done with my preliminary research into this codebase.

Our corporate SSO provider is changing, so I've been updating our tools to take advantage of the new badges. I found this in a web application that I started on today. The original developer is long gone, and according to our PaaS, this app has been running for just under 3 years without an update.

There is no CI/CD, blue-green deployment, or back ups. The database is an H2 db with ddl-auto set to create-drop on startup, meaning that this database will delete itself if the app is restaged but thanks to this guys code, it won't populate itself. ๐Ÿคท

you are viewing a single comment's thread
view the rest of the comments
[โ€“] devil_d0c@lemmy.world 53 points 2 years ago (1 children)

Found this in production while migrating SSO providers. Made me chuckle ๐Ÿ™ƒ

[โ€“] yamsham@lemm.ee 40 points 2 years ago* (last edited 2 years ago) (2 children)

DO NOT RUN IN PROD

Found this in production

Classic

[โ€“] devil_d0c@lemmy.world 9 points 2 years ago

When I sat down today I thought I was just going to be updating some properties file with oauth end points.

This is so blatantly stupid that I now have to pick through the code base and write up a change request and incident avoidance report ๐Ÿ˜•

[โ€“] yukichigai@lemmy.world 6 points 2 years ago

Only thing better is finding commented out code below that which would actually prevent it from running in Prod. Bonus if there's a code comment next to it saying "disabled per email" with no further explanation.