![](https://media.kbin.social/media/72/ac/72acad3fb8ac929641eb366b31724ffe59cf88817d010704908aa23271ac9ae0.png)
![](https://lemmy.world/pictrs/image/2665e448-91d9-484d-919d-113c9715fc79.png)
Fuck I mixed up my board game doll companies lol
Computer guy, occasional gamer, shitty music producer. Denver, CO
Fuck I mixed up my board game doll companies lol
Yeah… that trait isn’t limited to Reddit users
I think it is fantastic. Great level design, some of the wonder flowers had me laughing and some had me crying, though I have yet to 100% it (getting close). It’s 2D Mario done well! It’s not supposed to be baldurs gate level deep, it’s Mario wahooo
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.
You may not agree, but they are right. We are not most people. They want, and they have, that sweet “lowest common denominator” market, and they will take advantage of that until something else generates more cash. The “lowest common denominator” demand more CoD and whatnot. They don’t care if it’s bad, because them and all their friends will buy it and perhaps even have some fun. The big studios converging on vapid cash grabs instead of creating interesting content is depressing, sure, but hardly surprising in a world where morals and ethics don’t matter, where you can get away with the absolute most heinous, reprehensible acts, and suffer zero consequences.
I don’t really care though. The indie scene is unaffected by this, and has only gotten better every year for as long as it has been around. It’s fucking GLORIOUS already, and it’s not going anywhere because it’s not run by an oligarchy of publicly traded shitfactories.
LAVOS
To serve butter.
The one that comes with the IDE, because I don’t really care.
I’ll be honest, I just look at the steam store page for the game. If the initial impression from the images is good, and it’s a genre I want to play right now, I watch one or two of the videos and read a few top reviews. Then I just go for it. I don’t watch streams or anything. I am usually perusing indie games so it’s at most like $20 on the line, not the end of the world if I hate it, or if it needs a few years of patches to feel worth playing.
I’ve heard it much better described as a “distributed monolith”, which makes complete sense to me. It’s what you get when you “break up” a monolith into “services”, but the spaghetti is still there, it’s just distributed across services now. You have to actually eliminate tight coupling, define the correct boundaries, and vigilantly respect them. All of which should happen from within the monolith first, ideally, where you still have the massive luxury of one codebase to deal with as you make the huge refactors necessary before completely decoupling into services. Even better, do this required prerequisite work and discover that your monolith is actually… fine.
fzf? https://github.com/junegunn/fzf
Out of the box, would only help searching shell commands that have been run, so for files, things like “vim file.txt”, which is obviously not usually how files are edited (you’d use the file browser in a text editor or IDE)
However if you find a way to list all files on your system by modified time, you can pipe it to fzf for a slick fuzzy find search.
Maybe ag would work here too: https://github.com/ggreer/the_silver_searcher
Sorry m8 didn’t expand the read more to see that. Good luck
Mistborn is great, less dragons and more alchemical science. Begins with a satisfying tale of overthrowing the government, and then tackles some of the “okay… now what” with tons more interesting stuff along the way
It’s definitely worth a play, though even the remake does feel a bit dated in the gameplay department. The storytelling more than makes up for that though!
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.