A fanfic based on devRant-chan. The character was created by @caramelCase and a drawing by @ichijou.

This is freestyle. I'll think of an image of a scene and go with the flow. I won't remove my fingers from the keyboard and I won't edit or change anything. That's how I come up with my best ideas.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Notes:

B/N = Boss' name (I was too lazy to think of one.)

Anything in between astericks is in italics.
Ex.) *this is in italics.*

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

It was an early January morning when devRant-chan was situated in her desk, typing away on her laptop. She was working on a Python script for her barbaric client when she could've been out with friends. Oddly enough, her Sunday was surged with tranquility.

Normally, Sunday is when her irksome boss barks orders at her on the phone.

"This is wrong!"

"What is this?"

"Change it!"

devRant-chan resented her boss but loved her job. After all, "you can't force yourself to like everyone," was something her elder brother would tell her.

She released a slight chuckle, the one she would only display at the thought of her brother.

Her musings were interrupted when a concerning thought crawled into her mind like an undesirable intruder.

Why hasn't her boss called to complain yet? It's not that she enjoyed his complaining, which she didn't. She simply found it odd, since he's done this every Sunday morning, since she was a junior developer.

Unless he found someone else to complain to? In that case, good riddance!

But still, it wasn't a euphoric feeling to be replaced. She was already accustomed to his Sunday morning calls that it feels almost lonely not to receive them.

She should call him... Just in case some situation—or—problem—has emerged.

She dialed his number, waiting patiently for a reply.

"Hello," said her boss.

"Ah, hello," said devRant-chan. "I called, wondering—"

"You've reached the voicemail of B/N, please leave a message after the beep."

"Damn..." mumbled devRant-chan with a sharp exhale. "I always fall for that."

Why didn't her boss answer the phone? It was odd of him, considering he's always answered her calls.

She was about to dial her coworker when she received an email, which stimulated her attention. The subject of the email read:

*Important. Please read.*

She opened the email. It was her boss. The email read:

*Hello.*

*In case you aren't aware, I had quit my job, due to the stress. I've left the manager in charge. Starting tomorrow, he will be your new boss.*

*-B/N*

Before she could rejoice in excitement, she detected a strange change of voice, emitting from the email. Did her boss really write this?

That's when she spotted something. The word "tomorrow."

Her boss didn't write this.

He would never use words such as "tomorrow," or "today." He would use time instead. If this was her boss, he would say "in 24 hours."

She checked the IP of the email. Oddly enough, it was her boss' IP.

Still, the pieces didn't fit the puzzle. Her boss didn't complain, answer her call, or use his style of speaking in the email.

Something happened to him and she knows it. Whatever it is, has something to do with the manager, and she was determined to figure it out.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This was just a quick random fanfic, and I'm not sure if I'll continue it. As I said, I didn't plan anything, since it's freestyle. I might or might not continue it, so I'll think it over.

I was searching through StackOverflow when I found this guy:
He is using a "dot operator" in LINQ at the end of the Query
Example:
a.Where().
Select();
Not
a.Where()
.Select();

How barbaric

Dynamically typed languages are barbaric to me.

It's pretty much universally understood that programmers program with types in mind (if you have a method that takes a name, it's a string. You don't want a name that's an integer).

Even it you don't like the verbosity of type annotations, that's fine. It adds maybe seconds of time to type, which is neglible in my opinion, but it's a discussion to be had.

If that's the case, use Crystal. It's statically typed, and no type annotations are required (it looks nearly identical to Ruby).

So many errors are fixed by static typing and compilers. I know a person who migrated most of the Python std library to Haskell and found typing errors in it. *In their standard library*. If the developers of Python can't be trusted to avoid simple typing errors with all their unit tests, how can anyone?

Plus, even if unit testing universally guarded against typing errors, why would you prefer that? It takes far less time to add a type annotation (and even less time to write nothing in Crystal), and you get the benefit of knowing types at compile time.

I've had some super weird type experiences in Ruby. You can mock out the return of the type check to be what you want. I've been unit testing in Ruby before, tried mocking a method on a type, didn't work as I expected. Checked the type, it lines up.

Turns out, nested away in some obscure place was a factory that was generating types and masking them as different types because we figured "since it responds to all the same methods, it's practically the same type right?", but not in the unit test. Took 45 minutes on my time when it could've taken ~0 seconds in a statically typed language.

God dammit, this is barbaric!! How can Microsoft managed to fuck people's work every time!!

I hate those mother fucking, Cock sucking, dick farting retarded faggots, who get the opportunity of a new job/internship just because they have a certain "relative" in the said company/organisation.
I mean its ok that you are getting an opportunity, but just don't act all-knowing-god-tier while you don't even know how to print a statement in c++ and got it.
How many more relationships should I increase of mine so that I get into the same position like them.
One of my friends got the internship just because his girlfriend's brother works for the firm.
Now that's just super barbaric unless he gave a blowjob to the gf's brother.
Their Fucking assholes need to be drilled by a giant pile drivers.

Great practice/skill sharpening idea for my fellow mad dogs that like to get down in multiple languages/syntaxes:

Pick something simple that won't cause too much stress, but will make you sweat a little bit and put up a good fight, ha!!!

For example, I picked the classic "Caesars Cipher" and picked 5 languages to create it in! I picked Dart, Java, Python, CPP, and C. Each version does the same thing:
1. Asks for a message
2. Runs the logic
3. Prints the message cipher.
4. To decrypt, you just run the same program again and enter the cipher text at the message input prompt. The message gets deciphered using the same logic an shows up as the original text.

The kicker:
Only dox/books allowed for reference. Otherwise it wouldn't push you to get better!!!

Python, C, and CPP were EASY, even with me never having used C before. I am great at using Dart, and that one really challenged me for some reason, but I finally got it. The previous 3 langs took less than 40 lines of code each (with Python being only 18 I believe). Dart actually took somewhere around 50, and Java took about 371784784. (Much love to Java though for real!)

Kinda boring as shit, but I gotta tell you it felt fuckin GREAT to look at all 5 of those programs after completing them, no matter how barbaric... especially when you complete 1 or 2 in a language you've never used or maybe felt really challenged by. Simple exercises that hold a lot of important, relatable logic no matter the subject is our lifeblood!!!