Just started a new job last week. Ive been in the industry for 3 years so not completely junior but getting in to a new codebase is always rough. Especially when only 1 huge library file is documented, every component is cluttered af and most variables and parameter names are 1 character long.
Doesnt help that functions are 100 lines either when each the parameter names makes the logic incomprehensible.
Bringa back Hats! Ive said this many times, but we need to bring Möre headwear into fashion. Hats go hard.
Will update the original post but I solved it. Apparently there's specific gamepad settings inside of Wootility under Settings > Gamepad. There you have to select what type of controller the software will emulate. I just took the recommended (Xbox Controller) and now it works as expected.
The keyboard itself is fine if I use regular mappings, however in the wootility software they provide (yes they have an official linux version) you can map controller inputs to your keys. So for example I can map (emulate) controller joystick left input to my A key to emulate the analog signal. These does not seem to register in-game. Other key inputs work fine.
In Sweden we just say "vvv"
This. Starting at the company in 2023 and first task being to "start enhancing a 5 y/o project" seemed fine until I realized the project was not even using git, was being publically hosted online and contained ALL customer invoices and sales data. On top of this i had to pull the files down from the live server via FTP as it didnt exist anywhere else. It was kinda wild.
Using Filezilla FTP client for production releases in 2024 hit me hard
This is the most banger tattoo though. Random answers to a test that could potentially exist in the future.
What youre describing sounds alot like Grayjay
Fair, but they wrote "states" which immediately maked me think it's the US.
Got one of those rare holo hieroglyph Mew pokemon cards stolen when i was a kid, i still think about it.