As a release engineer for Electronic Arts for 13 years, this looks like to me a copy of either the source folder from Perforce, a devs machine that had synced a stream, or the same from a build machine. It's not uncommon to use batch files and python scripts to reconfigure a workspace to switch workspaces. I see a solution file in there.
I would bet that particular file is an automation script to configure a machine for development.
I do this. That fucking troye sivan song haunts me now.
Can confirm. Worked at BioWare for ten years. They did a presentation at some big release event and they had the pc off stage with a pan of ice and a fan directly blowing on the open pc. Mmmhm it totally won't melt your pc! They eventually fixed it, but video game announcement trailers are total smoke and mirrors typically.
Most, if not all podcasts are just an rss feed to a url. The application consumes that xml and delivers it to you as icons for you to listen to.
So when I was in the interview, you know, typically you answer questions, right? I mean there's some back and forth, but typically you're on the end of the stick.
It was Zello. They wanted someone to continue manual deployment. Are you fucking kidding me? Read the reviews. They are all consistent with a good product and an outdated infrastructure team.
Best of luck.
edit: grammar
AntennaPod (Easy-to-use, flexible and open-source podcast manager and player) https://f-droid.org/packages/de.danoeh.antennapod/
edit: just now trying the app. Really awesome, better than the thing I'm currently using. Thanks for the suggestion!
Yeah i don't think another wiki is a reliable source. I think that would fall under user forums or some shit. https://en.wikipedia.org/wiki/Wikipedia:Verifiability#Reliable_sources either way, good for them lol
Lol it's not new, it's always been like this for as long as i can remember. Keyboard warriors will be exactly that. You just have to work around it. It's precisely why i never became an admin. These days i just stick to typo fixes using awb. Useful but not too much.
As a 15 year long editor to Wikipedia, this comment is exactly how i feel and it's hilarious.
edit: my God i just waisted 2 minutes of my life I'll never get back reading that article. 40 editors are a SPEED BUMP when it comes to editing the Wikipedia. Also what's up with the terms they are using for group of editors? Lol
What id like to see is the appeal to the admin thread on the Wikipedia. Instead we have a slate article about this click bait bullshit.
Reminds me of an interview i was in. I was like, this isn't even in my job description... 7 interviews later. Come to find out, they were HAND DEPLOYING Linux servers to try to scale for double of their user base. I feel like I dodged a bullet.
Visual Studio