Posts made by WTFE

It has been [10] hours since @shangexile "quit" MSB.
It has been [1] minutes since @shangexile last posted.

@shangexile said in RL Anger:

@Auspice It's funny when people ignore your posts and don't realize when you've stopped arguing pages before they have. Then they tag you and insult you for still arguing. Wait, now I'm arguing. Fuck. Bye!

Fuck, now I have to open a gofundme for a liver transplant!

@shangexile said in RL Anger:

@WTFE I'm guessing you read my posts all the way up to, but not including, my last exchange with @surreality. Read those and you will see why I am actually and honestly done here. I have nothing else to discuss here. I'm not MU*ing anymore.

Ow! My fucking liver!

@shangexile said in RL Anger:

@Meg OK, cool! Be a place where people "name and shame" and form factions. That's awesome. Just don't be surprised when the people who are named and shamed come by to do creepy shit- like, say, upvoting posts. Oh, the horror! How can we defend our fragile senses of self against the unmitigated assault of using forum features?

Oops, did I continue posting after I said I'd leave? I've seen other people do that, so I think it is OK. (Though I do intend to leave, rest assured.)

Oops. Did I say a week? I meant a minute.

@shangexile I give you about a week, tops, before you come slinking back and pretending it was all "just fooling" us.

Which one of you fuckers is going to be paying for my new liver, is all I'm asking?

@Apu shows wisdom. Listen to @Apu.

@surreality said in RL Anger:

@Thenomain said in RL Anger:

Sometimes an apology isn't enough. Sometimes an apology is the wrong thing to do, because too many people stop there when they need to fix the damn problem.

^ This. Not in regard to you in any way, but in regard to that being a very broad, if not universal, truism.

Too many people have a habit of treating an apology like a 'get out of jail (almost) free' card, and there are absolutely certain circumstances in which actions have to back up the words for the words to have any meaning at all.

Smart people view the apology as the first step toward making good.

MUSHing isn't full of smart people (present company not excepted).

@Pandora said in RL Anger:

Fake apologies are kind of like fake tits, they look nice but they feel fake. Who has the time?

Have you tried a genuine apology?

Oh, right. I forget who I'm talking with. (Hint: I didn't forget.) Of fucking course the thought that you might make a genuine apology never crossed your mind.

@Kanye-Qwest said in RL Anger:

@WTFE said in RL Anger:
ver understood why this was considered a virtue instead of an exacerbating condition.

If someone doesn't realize they're being an asshole, it's not really quite their fault (except insofar as not knowing you're being an asshole is often fucking stupid).

Wrong.

How cogent and coherent! Your rebuttal has me rethinking the very foundations of my beliefs, it has shaken me so deeply.

@Arkandel said in RL Anger:

@WTFE said in RL Anger:

That isn't the kind of usage I'm talking about though. I'm talking more about the people who say things like "well, I'm an asshole, but at least I admit it" or "well, I'm an asshole, but at least I know I'm one". As if knowingly being an asshole mitigates.

I guess that's better than being a hypocrite about it? "I'm not an asshole, I just tell it like it is".

That would depend. If they honestly believe the "tell it like it is" thing, that's a stupid asshole. If they are saying "tell it like it is" knowing that it's a lie, that's a dishonest asshole. Dishonest asshole is worse than stupid asshole.

@Arkandel said in RL Anger:

@WTFE Not many people are assholes all the time, but even more importantly, almost everyone is an asshole sometimes.

Absolutely agreed.

Personally when someone acknowledges it I look at it as an admission of fault; it's not an apology - maybe that'll never come - but maybe more of a request - hey, I know I can be a jerk but I've got upsides too... is that okay?

That isn't the kind of usage I'm talking about though. I'm talking more about the people who say things like "well, I'm an asshole, but at least I admit it" or "well, I'm an asshole, but at least I know I'm one". As if knowingly being an asshole mitigates.

If I waited to hang out either here or iRL only with perfect human beings I'd be one lonely son of a bitch.

Hmm... I'm a lonely son of a bitch. Perhaps a strategy change is in order...

@Pandora said in RL Anger:

At least I own being mean and hateful when I am in fact being mean and hateful, which is honestly not that often.

Never understood why this was considered a virtue instead of an exacerbating condition.

If someone doesn't realize they're being an asshole, it's not really quite their fault (except insofar as not knowing you're being an asshole is often fucking stupid).

If, however, someone knows full well that they're being an asshole and then flat-out says they know it this actually, to my mind, is worse. It means they recognize assholeish behaviour and then explicitly decided to continue doing it.

Purebread cat.

@Coin said in RL things I love:

@WTFE said in RL things I love:

@Catsmeow said in RL things I love:

Tattoo!!

If I ever get a tattoo it will be of a spider. On my scalp. I will shave my head, get a tattoo of a massive spider, then wear a hat until the hair grows back to cover it.

Why?

Well, first, I kinda think spiders are spiffy. But that's not the main reason. The main reason is that I'm balding. There's a race on my head between the hair thinning out to the point of absence on the top, friar-style, and the corners above my forehead pushing back to meet behind my head. And as I bald, more and more of that spider will become visible. That will be fun.

Man, I hope you have a high threshold for pain, 'cuz that shit is gonna HURT.

My threshold for pain is called 白酒.

@Catsmeow said in RL things I love:

Tattoo!!

If I ever get a tattoo it will be of a spider. On my scalp. I will shave my head, get a tattoo of a massive spider, then wear a hat until the hair grows back to cover it.

Why?

Well, first, I kinda think spiders are spiffy. But that's not the main reason. The main reason is that I'm balding. There's a race on my head between the hair thinning out to the point of absence on the top, friar-style, and the corners above my forehead pushing back to meet behind my head. And as I bald, more and more of that spider will become visible. That will be fun.

@Ganymede said in RL Anger:

Animal snobs can fuck right off.

FTFY.

In general when I start a new project I divide the issues up into several boxes: PD, DS, SI, HI, and NY.

PD: Problem Domain
This is the code for the actual functionality. If you're calculating artillery trajectories, this is where you put your kinematics code. If you're writing a chess engine, this is where you put your move tree pruning. If you're writing control firmware for ABS systems, this is where you link your sensors to your actuators via your PID controller. (This happens to also be the code that is most likely going to require few to no changes even if changing platforms.)

DS: Data Storage
This is where you map the data needed by the PD code into how you plan to persist it. This is where you have your flat file reader, your database integration layer, your file system handling, etc. It may be mildly system-specific: you may need minor changes in file systems when moving from Windows to Linux, say, or from SQL Server to MySQL, but the code here will be generally stable as long as you don't profoundly change your persistence model.

SI: System Integration
This is where you toss the stuff that's not related to data storage but is variable across systems. Your concurrency mechanism maps from your model to the native model here. Your network interaction layers are in here. Even your I/O primitives could be found here depending on the precise nature of your PD.

HI: Human Interaction
Whether command line or GUI or VR or whatever else is dreamed up, you put this into a separate box. If your PD code has any code related to human interaction in it, you've done fucked up and you've locked yourself into a single mode of interaction for no good reason. (Most software, sadly, has done fucked up in this regard.)

NY: Not Yet
This is the box where features that would be cool but that you're not going to put into this release go. Why don't you just toss them out and deal with them later? Because knowing that you're going to put a feature in will have you thinking of how you'll put it in and leave you room in your design for that later feature expansion. If you just toss out the NY features without thinking about how they'd fit in in the future you're opening a can of whoop-ass on your own code base.

Now, not all software has all five boxes filled. An embedded sensor monitor, for example, may not have an HI component at all: its controller will have that. And your HI and PD might be the same thing if your software is, say, a GUI framework library. But in general an overwhelming majority of software would be well-served by using this simple model.

And here's the thing.

Even beginners and hobbyists would be well-served by doing this boxing. Because separation of concerns makes for simpler code bases, not more complicated ones. But it does mean you have to think before you type. Which is the major distinction between "programming" and "coding".

This, @Ashen-Shugar, is incidentally why I don't think there's actually a clash between supporting the CONFIG.SYS-lovers and the WIMP-lovers in properly-constructed software. The issue isn't that it's impossible to support CLI and GUI and whatever in the same program or program suite. It's that most software is written by people who can't imagine that it's even possible.

@Thenomain said in UX: It's time for The Talk:

This is me changing my mind and making a post just to point you out as someone who may know what they're doing but has no interest in helping the hobby.

The hobby has absolutely zero interest in being helped. Look in this thread: a bunch of grognards being told "you know, this could be made simpler" are frothing at the mouth about how it's ABSOLUTELY ESSENTIAL that there be bizarre prefixes in front of commands because ... REASONS! DIFFERENT, CONTRADICTORY REASONS!

This hobby is dead.

So I amuse myself by poking at the grognards and watching them say utterly idiotic things from a perspective of complete ignorance. It passes the time.

@Derp said in UX: It's time for The Talk:

I cannot imagine an 'intuitive' way to create a command line anything.

Proof by lack of imagination…

The very first book I read on what would later be termed "UX" was called something like Human Factors in Computer Interaction. It was written in either the late 1960s or the early 1970s. I read it in the early 1980s, long before everything and their dog had GUIs.

It had three chapters or so devoted specifically to how to structure command systems so they could be learned quickly and be built up upon from easily-learned basics.

It amazes me how little of a sense of history programmers and programmer-wannabes have given how little history programming has as a discipline. Electronics engineers are familiar with history that stretches back something like two centuries. Mechanical engineers have to learn a history that stretches back to the dawn of civilization. Software developers have about 70 years of history--tops!--to concern themselves with and are utterly fucking ignorant of anything that's older than six weeks.