Have you played the second one? I begged my parents for weeks to rent it. Then I got it and… I can’t even describe it. At one point there’s a platformer puzzle room based on the Three Bears. I played it for a whole weekend because I couldn’t believe how awful it was.
maybe this will work
linting and unit tests
Lawyers all dragging screenshots of excitebike into court and counting the wheels.
A thing that hallucinates uncompilable code but somehow convinces your boss it’s a necessary tool.
My cousin rented Megaman 2 and I spent at least an hour in awe of the fact that he could get hit more than twice because he had an energy bar. Then he switched weapons and threw a saw blade and I had to go sit down and think about it for a while.
Yeah, I bought one in my 20s.
Holy cow I thought I was the only person that played that. Excellent game.
In a similar vein, Ghost Master. Some of the levels are fiddly but it’s a ton of fun.
Nah it’s just extra protein.
This is the hardest thing to un-train with new employees: be honest about your mistakes. I will not get mad about a mistake. Everyone makes them. The best thing to do is call it out so we can move to fix it. If you keep making the same mistake, maybe we have a talk about your process to see if there are any blind spots.
So many people try to hide their mistakes or reframe them as successes and please do not do that. Own it, see if you can learn anything from it, and let everyone know so we can help you fix it.
Yeah that’s actually funny. Calling it FRAGS is just the icing.
Now that it’s less broken, I’ve been playing Cyberpunk a lot and it feels like edgy shit done correctly. All the big tough guys are actually just weirdos enamored with the sound of their own voice, the ads are ludicrously over the top, it’s bloody, and everyone’s a human being. I haven’t felt gross with any of the content in it so far and it has at least as many strippers as Duke 3D had. I think the loud edgelords keep trying to paint it as free speech vs censorship but it’s really about not making players complicit in whatever infantile world view the director has.
Lol that’s awful. 2009?!
Nah this is still corpo bullshit. It’s also one of the tamer specimens of that era. The only difference is, the corpos in charge of advertising at that time were all sentient hardons who heard stories about how drugs are and peaked at 14. None of them lived in the real world and they just churned out knee-jerk sexist bullshit because they wanted to appeal to boys going through puberty and men that never left that headspace.
<rant> A lot of the ads from that era are uncomfortable. Hell, a lot of the games were. It was rare to see a female character that wasn’t ditzy and helpless, a thinly-veiled copy of the writer’s mom, or exactly like a dude but hot. Those were the options. I’m not saying I needed every game to be a work of great literature with complex and tormented characters and copious backstory; I just wanted female characters in games that didn’t like someone doing a ventriloquism act with their fleshlight.
I ended up chasing gameplay and trying to ignore how fucking awkward and immature most of the shooters were in that era and I don’t think I was alone. I think a lot of gamers grew up and drove the market in a slightly more mature direction. Some people blame woke bullshit, but for me it was just being utterly sick of how fucking juvenile everything was and voting with my money. There’s still a vocal minority out there that wants the good old days back, but I’d stop playing if the industry went back to exclusively 3xtr33m l33t 4ct10n d00d bullshit.
Sidenote: I played the demo for some Cliffy B game a decade ago on my XBox and hard-quit and deleted when the guy on my comms told me to “fire a rocket directly up the bad guy’s poop chute.” I was in my 30s and Cliff was probably pushing 40 at the time. What the hell? Are we nine years old again? Then again, he was the guy that threw his cat into his scanner and posted a picture of it every day until the internet told him to stop. Ugh. Let’s never go back there. </rant>
Steps to test: “Idk try some shit”
Yep. This is the way. Also, you’d be surprised how many devs don’t run through their own QA steps before asking other people to verify.
Yuck.
This is pretty coherent for an ambien post. I had a friend that used to hang out on groupchat after he took an ambien and at a certain point he’d just start sending random strings of text, but really emphatically.
At some point, they’re gonna have to debug it.
If you’re trying to pull your weight, and it sounds like you are, the problem is either with the tasks, the codebase, or the teammates:
Potential problems with the tasks:
A ticket needs: clear repro documents (if necessary), screenshots, and clear steps to reproduce. It needs more than “Title: Add X to Y. Description: We need Y in X. Implement it.” unless you’re intimately familiar with the codebase. And even if you are, you still need a paper trail to back up what you’re doing. If you’re not closing tickets, be very chatty in the comments. Share where you are, problems you’re running into, and who you’re waiting on for help. If there’s a consistent theme to the things you’re fighting, keep a list of them and bring them to your manager. Be your own advocate and be very transparent about all the research you’re doing because other people didn’t.
Potential problems with the codebase:
Hey, it works. But it’s not documented, someone decided to be clever instead of elegant, the local story sucks, or it’s optimized to such a degree that you have to refactor just to add a simple option ("lol why would we ever need that data here? It’s inefficient!)
Potential problems with teammates:
Everyone pulls their weight. Everyone communicates in clear, declarative sentences and provides examples if necessary. “I don’t know” is an acceptable answer. Evasiveness, vagueness, specialized jargon, or acronyms point to the dev being insecure about their knowledge in that area. Be very suspicious of the word “should”: “that should work”, “that shouldn’t be hard”, “you should be able to…”
And, as an aside, I’ve seen this happen a lot. A new dev or contractor comes on, blows through tickets, gets good marks, and an existing dev or two get called out for not contributing with the same frequency. One of two things are happening here: the new devs are getting softballs, or they’re creating a lot of subtle tech debt that someone else will have to fix because they don’t have a full picture of the codebase. Eventually, those devs will be where everyone else is, but it’s still frustrating.
Hang in there.
It’s funny how soon they realize they want a good one.
I agree with you. Even if you never touch it, it’s nice to know what the libraries you’re calling are doing under the hood.