The gift that keeps on giving... the Custom CMS Of Doom™
I've finally seen enough evidence why PHP has such a bad reputation to the point where even recruiters recommended me to remove my years of PHP experience from the CV.

The completely custom CMS written by company <redacted>'s CEO and his slaves features the following:
- Open for SQL injection attacks
- Remote shell command execution through URL query params
- Page-specific strings in most core PHP files
- Constructors containing hundreds of lines of code (mostly used to initialize the hundreds of properties
- Class methods containing more than 1000 lines of code
- Completely free of namespaces or package managers (uber elite programmers use only the root namespace)
- Random includes in any place imaginable
- Methods containing 1 line: the include of the file which contains the method body
- SQL queries in literally every source file
- The entrypoint script is in the webroot folder where all the code resides
- Access to sensitive folders is "restricted" by robots.txt 🤣🤣🤣🤣
- The CMS has its own crawler which runs by CRONjob and requests ALL HTML links (yes, full content, including videos!) to fill a database of keywords (I found out because the server traffic was >500 GB/month for this small website)
- Hundreds of config settings are literally defined by "define(...)"
- LESS is transpiled into CSS by PHP on requests
- .......

I could go on, but yes, I've seen it all now.

I feel like an idiot... I just realized why my builds were failing.
My entrypoint was setup as to not overwrite a specific file if it was already there. The problem is, the said file is auto-generated, and I need a different configuration for it to work properly in docker. But I forgot this, and the result was a failing build, plus me scratching my head for a few hours. :(

>Working on code
>Shit works as intended first try, nice
>Goes to play strange bootleg Gameboy Color ROM sent by a friend
>ROM immediately fucking dies
wtf.svg
>Pop emulator's debugger
we're executing from VRAM, stack's firmly embedded in ROM
>why
>Add execution breakpoint to entrypoint of game, restart emulated system (because i'm actually using the legit bios i hacked so it allows null/corrupted games to run)
>Step through everything, everything goes well until all of a sudden we call a function and shit hits the goddamn fan
well we have the culprit
>step through subroutine
if <unused_byte_in_HRAM> != 0 then stackPointer+=32;tryAgain();else return
>***y***
>Realize this is using a bootleg Memory Bank Controller with hard-backed encryption so none of the bytes executed or read as data are the right byte
>Find emulator that'll handle the jank MBC
>read code to try and figure out how it works
if checksumExtendedLogoBlob == some_number then set MBC_Bootleg1 else if checksumExtendedLogoBlob == some_other_number then set MBC_Bootleg2 else if...
>of course
>Spend 10 minutes finding the right bootleg MBC
>code shows 8 possible tables for real bit order based on some value in the cart header
>look for code that gets this value
>not in the header
>not in ANY header in this 1000+ file emulator
>not in any related cpp files???
>get desperate
>email author
>"Delivery failed: email doesn't exist"

fuck me i guess

Quick question..

INFO:
Im attending Computer Science Study's im at the end of 1. Semester. We'r going to cover app development in 4th semester, but i cant wait that long, i want to use my spare time starting to build apps to get ahead of studys.

Im currently pretty decent in Java, so i want the app based on java language, and we've used scenebuilder for our desktop GUI's so far with FXML..

QUESTION : What do you use to develop java based ios/android apps - software,languages, etc.

Dont want to start a "this is better than that " war, just looking for a good entrypoint to java app development.

THANKS 👍

Dude ist sysadmin at server Pool hosting our app for the client.

Client: something minor is not working.

Dude: Let me just restart app, works at my windows laptop everytime or whatever.
*restarts app, hangs on entrypoint*

Dude: Dear client it's brocken.

Clients: *calls us in panic.*

Horus: Dear dude, when it hangs on startup consider to download an update because we fixed some issues with in theis area recently. Also maybe enlarge the docker compose timeout.

Dude: Still does not start up.

Horus: ok just call me on this Zoom link, then we can debug together.

Dude:...

Dude:...

Dude:...

Dude: oh i just saw it did startup mean while, it just took some time.

Fuck you dude, and your impatience!

Setting up dockerfile with ENV(from Visual Studio) was such a stressful endeavour from the point of view of someone that doesn't work daily with containers that I'm wondering how you master folks of net core and docket live and breath.

The gotcha was to put the ENVs at the first FROM from which the running environment was going to execute the WebAPI and not later on where there is the ENTRYPOINT point