chance + stakes = gambling
chance + nothing = chance
Computer guy, occasional gamer, shitty music producer. Denver, CO
chance + stakes = gambling
chance + nothing = chance
Yeah lol learning poker hands is all it does, which is trivial. The hard part of gambling is learning odds and how to bet. There is a little bit of odds calculation in the game, but it’s incredibly unrealistic with all the modifiers, and they change on each run.
It’s more like asking a carpenter to build a hammer as their practical carpentry interview. It’s probably good they know about hammers, but what you actually want to know is if they can build cabinets.
I enjoy it, started playing recently! All the fun for me is in trying to find good loadouts completely on my own. I don’t want to watch some YouTuber show me the absolute maxed out best loadout, because that’s the entertainment to me. Progress is slow, I still haven’t cleared the game lol, but when I do, I know it will be my own choices that got me there. No shame in researching how to win if that’s your thing, I just love diving into games like this blind.
You joke, but Rails actually does make Integer do too many things lol. I’d argue they’re useful things, but it does so by patching the core Ruby Integer class :p
Strings became ubiquitously used for a reason, they map really clearly to the way we think as humans. Most importantly, when you’re debugging, seeing string data is much friendlier than whatever data your symbols map to (usually integers, from enum structures)
No, obviously it’s not the most efficient thing in the world, but it hardly matters, and you’re not getting anyone to stop because you’re “technically right”.
Excuse me. This was one of the greatest RTS and 40k games of all time, and I will accept no other answers.
Death Stranding is one of my favorite games of all time that I will recommend to literally nobody.
It took me a long time to really grok iterative methods like this, but once it clicks, you will absolutely know and feel like you have unlocked a new super power.
It starts with completely understanding that you are just passing functions as arguments, and those functions are being invoked, in a loop, for each item in the collection. Once you have that concept internalized, you should then learn the difference between filter, map, reduce, etc. The general difference boils down to: 1. How the iterator function changes the value being iterated over (most don’t) 2. What does the iterator function itself return (i.e. map itself, not the function passed into map. map and filter both return a new list, reduce returns the data structure being reduced into)
I would skip trying to understand reduce at first, though it’s the method you can implement all other such iterative functions with. The derivations like map and filter are just easier to start with.
And again, seriously, it took me like 2 years to completely internalize all of this, even after CS classes.
Fuck I mixed up my board game doll companies lol
I didn’t even know this was a thing. It would not have been great, and may have been good, but Naughty Dog doesn’t really seem to be in the camp of settling for good
Yeah… that trait isn’t limited to Reddit users
Isn’t it that horrid ugly fucking foot
deleted by creator
It’s always been one of my favorite ways of describing the job :)
It’s a huge faff, you will get a different answer from every person you ask. They’re used interchangeably, and it just doesn’t matter.
To entertain your prompt. Real world engineers (structural, etc.) aren’t entrusted the title because they “care” about what they build, it’s because they have to be correct, and as such, they follow extremely rigid process and take the time to never be wrong. Obviously I do not have real world structural engineering experience, but I think we can all agree on this from an outside point of view.
That’s not how software works most of the time, and it’s even heavily discouraged in a lot of the industry. We learn from failure, and the consequences of software failing are nil compared to the consequences of a bridge failing. This is a huge superpower of software, not a weakness, or some sign of deficiency. It is the key reason software evolves so quickly. Software engineers (or developers, alchemists, whatever) are allowed to fail, learn from mistakes, and improve. They can test completely new, never been done ideas, nearly for free, and nearly instantly.
Again, I don’t really care though what the industry wants to call it, developer or engineer. It doesn’t matter and it’s all made up anyway.
Was always a big fan, but the steam deck has me playing a handful of new indie games every month, and it’s fucking awesome. So many little gems, so many unique ideas, for way less money, way less time invested, way less SERIOUS BUSINESS.
Rocket League. Games are quick, you can play one or many in a session. I don’t know if epic has ruined it yet, but last I played the good old core game was still there.