Progress, tho: nothing needed to be scrubbed, I just had to undo my changes. So that was fun.

Half my network went offline, everything with a browser interface was inaccessible, and I was a bit getting that fixed (especially those with no option for display). The logs were so cool tho, and I watching the progress--it was fast, as I'd mapped the vlans individually into a few.

2.) Programming Languages (Part 2)
Participation: 100
Final Grade: A!!!!!!!!!!!!!!!!!!!!!!!!

Yeah, I did not see that coming at all.

My final assignment (converted from mp4). Zooming from largest to smallest.
Fractal Data:
fractal:
width: 1466.0016441514904
height: 1134.7661586761242
polygons:
count: 80001
smallest: 2.337266889026511e-13
largest: 748.7044043921807

2.) Programming Languages
Assignment 11: 80/80
Final Assignment: 130/120
Final Grade pending for participation points, but as that's never been a problem....wheee!!!

Currently trolling through homelabs subs for the first time. Now that Gaia is up and running with my first rack server (though granted, right now it just holds all my singleboards and switches), it's time to level up and practice load balance skills.

So for fuck's sake, let me make modules, collect data on everything to both display to console and save to file, stuff tens of thousands of polygon coordinates into lists, randomly create user interactions that allow four different program outcomes from randomly selected vertexes, and also, colors.

Because unless it's very simple and very small and not a big deal, I will need at least a day to see dev's unit tests and the rest of third week to test it while they message me hourly in increasing desperation for my results. Super fun for both of us.

So...yeah. Just saying.

Mostly, they split their time between desperately trying to figure out what it does, how it's broke, what it looks like when it's not broke, and fixing it, all in a murderous four week sprint that's actually only three weeks (code freeze starts on Tuesday of the last week) and for devs, two weeks.

As a software tester in a fucking Agile environment where testers and devs are forced into an unholy alliance against stakeholders just to survive to demo...I have seen the face of development in a professional environment and no one is playing with the code.

All you know is this part is broken because it's doing x and it needs to do y. Sometimes you are even told what x and y are (not always). Rarely, they might have documentation; don't count on it.

So no, playing with the code is not an option. Figuring out wtf this shit is consumes a lot of time.

Like five other people will be working on adjacent code in that program and another team is working on the program you will have to integrate this with. Sometimes, you will have no fucking clue what this shit actually does in the grand program scheme of things.

Also: in general, being a dev, especially for a big company, means you will only rarely, if ever, be given something to work on that is even vaguely interesting enough to play with. Most of the time, you are not working on a program; you are working on a very tiny part of twenty programs.

But more importantly: why for the love of God would I want to play around with the code of a work program???? It's work; that's a job. I don't tell stakeholders they are idiots or my manager they're a moron or announce in an endless TEAMS meetings with unknown people I'm bored and logging off.

It's the weird-ass reason they give for it that gets on my nerves.

Reason: when you get assigned a program at work, you have to follow their requirements.

Me: No. Shit. Sherlock.

Note: this is not a reflection on my teacher. He made me interested in the history of ballet and become a frustrated fangirl of Niginsky. I just hate hate hate writing papers.