I dunno... just software engineering things I guess.
Guys it's a bit, he's doing a bit. Calm down.
devil_d0c
joined 1 year ago
I think they mean "looting."
Big tech won't chip in is my bet. My company maintains its own version of Linux that has some specific certifications. Updating that box requires an act of god. My bet is that the companies that can afford to will create their own "LTS" versions that just get older and older, and more broken and exploited as time goes on...
Sorry, long night at work =/
115 files changed and almost 3k lines added... sure, I'll have this reviewed by tomorrow for ya 🙄
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 😕
Found this in production while migrating SSO providers. Made me chuckle 🙃
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. 🤷
Oh no my cilantro aversion