Yooo, we got the new 420 Linux Kernel!

Got my wife a new Roku stick, which we needed and she was very excited about. She asked me to set it up. I said it might take a little while. She said she didn't mind.

Setup was easy and straightforward, but of course involved pairing the actual device with its remote. Then I had to create an account on the computer, since the previous device was her sister's.

It was at this point when she got mad, like really mad, that setting up a new device had to be "so complicated." Okay, first off, this is the happy path. Absolutely nothing went wrong, couldn't ask for better. Second, I told you it might take a little while, and it hasn't even been 5 minutes. This, I even asked you to make sure you wanted to do this now. And you're not even doing it, I am. Which I don't mind, but don't get mad at me that it's not literally magic.

Root ain't givin' no fucks no mo'

My boss just demanded that I join a conference call. So, I call in, and there's three other people there.

He starts chewing me out for talking with some vendor directly (their VP emailed me directly and asked for a few things, and i was instructed to make him happy). Apparently I used "confusing wording" and "did not talk his language." Bossman was really getting into gear for a ten-minute berating.

It turns out that the guy in question only read half of my first email, and totally ignored the second email where I told him everything was finished and live and working. I told my boss quite bluntly that the guy should have read what I had written, and that he was an idiot. The boss's defense of the guy? "Well, he's a sales guy." I just laughed at him.

Later, bossman started in on me (once again) for not making enough progress on this ridiculous shared-spreadsheet sales tool he wants, saying "We discussed this a week ago!"

I casually reminded him that we had talked about it for the first time ever on Friday night (today is Tuesday), and he had said it wasn't going to be a priority for the next three weeks(!). Again he stopped in his tracks. Again, I laughed at him.

Guy's a tool and I'm so done with caring.

Root's going to be flippant and angry. Root's going to have fun (:

What's he gonna do, fire me? 😂

What do you want?

How to start a shitstorm on normie social media:
"IPv6 is not as good as you think"

GF: Did you watch a movie while you were sleeping?
ME: (Syntax Error): How could i watch a movie while sleeping?
GF: No, the name of the movie is "while you were sleeping"
ME: oh, you forgot quotes for string

Whenever my friend messages me to debug his code or to correct the errors, I google the line with the error, open the first result and copy and send the solution to him.

Now he thinks I'm a badass programmer😂

it is true or not?

Sometimes I wished people had a REST endpoint to query their (mental) status ....

* Starts work with boss
* Works till night
* Decide to continue the next day
* Both leave work at the same time
* Both arrive at work next day at the same time

"Hey is the work done?"

Oh forgive me for not fucking dreaming up the work in my fucking sleep.

I inherited some Java code from a guy that thought you could only return strings from a method.

So how did he ever pass anything other than a string, I hear you ask? He had a (hand crafted, using no libraries, and not escaping anything properly) toXml() and fromXml() method on each object.

Yeah...

TIL: nobody cares about quality, only deadlines

Happened a few weeks ago but still awesome.

Me and a good friend have a website together but we don't monitor it too much.
He studied with me in the same class but went towards frontend/apps where I chose backend/servers/security. He knows how to do basic Linux stuff but that's about it.

We were at a party when he noticed that our site was offline. Walked over to me (because I manage the server) to notify me so I could look into it said I'd look into it (phone):
*visits site: nothing*
*online dig tool: got the server ip*
*remembered this one didn't have pubkey authentication - after three passwords attempts I'm in*

"service apache2 status"
*service doesn't exist*
*right, migrated this one from Apache to nginx....*
"history"
*ah, an nginx restart probably suffices...*
"service nginx restart"

BAM, site is reachable again.

*god damnit, lets encrypt cert expired...*
"history"
*sees command with certbot and our domain both in one*
"!892"
*20 seconds later: success message*
*service nginx reload*

BAM, site works securely again.

"Yo mate, check the site again"

Mate: 😶 w-w-what? *checks site and his watch* you started less than two minutes ago...?
Me: yeah..?
Mate: 😶 now this is why YOU manage our server and I don't 😐

His face was fucking gold. It wasn't that difficult for me (I do this daily) but to him, I was a God at that moment.

Awesome moment 😊

The man who invented autocorrect should burn in hello

Logged into a legacy box with an uptime longer than my age. That's how the troubleshooting went the rest of the day.

Master/Slave terms we're just removed from python. Why? Who needed / requested this? Do people not understand these terms to such a degree that they actually offend people?

WTF Python!!! "Master" and "Slave" perfectly convey the concept. In the English language many words have different meanings based on their context. It's plainly obvious that no allusion to human slavery is meant in the context of software or hardware module relationships. I don't even think it is problematic. The real problem seems to be the people who are taking terms outside their intended space. Why are we linking a scar on human history to terminologies explaining technical relationships?

Then lets also ban 0 and 1 because it can offends non-binary peoples!

New for avatars - emotions! You can now change your facial expression on your avatar to better capture your dev mood! Getting expressions working right turned out to be quite the undertaking due to the ripple effect of the various layers that each expression touched so our total layers just for men ballooned out from 300 layers to 1100. And @dfox re-architecting how layers work to handle the interconnectedness of expression meant tying together facial expression, skin tone, facial hair, and hair color to make sure everything stays in sync. It’s a fun new addition, I hope everyone enjoys!

I also want to apologize for the delay in getting this out, I meant to have this done ages ago but I got thrown a curveball at work and was laid off back in April and have been super stressed running around trying to find a new job for the past 3 months. I figured I’d have more free time to work on devRant, but hunting for work is so exhausting, it’s really taken its toll emotionally and financially (no unemployment benefits because according to my state even though we lose money every month “you’re still a corporate officer”). Things are finally looking promising on the job search front, and I expect once things get back to normal @dfox and I can get our release velocity back up, but until then, please bear with me.

P.S. If you have the resources, we certainly do appreciate your support with devRant++ Your monthly contributions really do make a difference! Thanks all!

I am the new girl. While I’ve been at this company for two years, I’ve only been in my new position a little over a month. I haven’t quite figured out if I am sysadmin or devops yet. It’s a bit all over the place. I am building a new thing at work. I build different types servers and set them on fire frequently as a hobby. This one is a stack I haven’t built before. It wasn’t working. I eventually got to the point where I told the other guy maybe I should consider resigning, I’m not qualified for this job. He said... Finally... now you’re going to figure it out and fix it. The next day, I did find what I kept overlooking and made it work. I guess this is life now.

Why are the most syntactically beautiful languages aren't the fastest ? 😭😭

That fortune cookie is definity meant for programmers.

Project Management Triangle

PHP is shit - Change My Mind

TL;Dr be specific, it's actually helpful.

Client rings... "The internet is down"

Me "ok where are you exactly and how are you connecting"

"Ugh the WiFi! Just fix it"

"Ok but where are you?"

"At $companyname"

"Ok and which wi..."

"The wifi?!! Can you do anything right?"

Well... I'm allowed flexibility in terms of pleasantry...

"Ok, there are 3 buildings, 55 rooms, 2 SSID's, 17 access points, 3 routers a RADIUS server and 2 gateways... Be specific or I'll do nothing"

Simple reboot of an access point, but c'mon... It's not a secret where you are

Worst thing you've seen another dev do? So many things. Here is one...

Lead web developer had in the root of their web application config.txt (ex. http://OurPublicSite/config.txt) that contained passwords because they felt the web.config was not secure enough. Any/all applications off of the root could access the file to retrieve their credentials (sql server logins, network share passwords, etc)

When I pointed out the security flaw, the developer accused me of 'hacking' the site.

I get called into the vice-president's office which he was 'deeply concerned' about my ethical behavior and if we needed to make any personnel adjustments (grown-up speak for "Do I need to fire you over this?")

Me:"I didn't hack anything. You can navigate directly to the text file using any browser."
Dev: "Directory browsing is denied on the root folder, so you hacked something to get there."
Me: "No, I knew the name of the file so I was able to access it just like any other file."
Dev: "That is only because you have admin permissions. Normal people wouldn't have access"
Me: "I could access it from my home computer"
Dev:"BECAUSE YOU HAVE ADMIN PERMISSIONS!"
Me: "On my personal laptop where I never had to login?"
VP: "What? You mean ...no....please tell me I heard that wrong."
Dev: "No..no...its secure....no one can access that file."
<click..click>
VP: "Hmmm...I can see the system administration password right here. This is unacceptable."
Dev: "Only because your an admin too."
VP: "I'll head home over lunch and try this out on my laptop...oh wait...I left it on...I can remote into it from here"
<click..click..click..click>
VP: "OMG...there it is. That account has access to everything."
<in an almost panic>
Dev: "Only because it's you...you are an admin...that's what I'm trying to say."
Me: "That is not how our public web site works."
VP: "Thank you, but Adam and I need to discuss the next course of action. You two may go."
<Adam is her boss>

Not even 5 minutes later a company wide email was sent from Adam..

"I would like to thank <Dev> for finding and fixing the security flaw that was exposed on our site. She did a great job in securing our customer data and a great asset to our team. If you see <Dev> in the hallway, be sure to give her a big thank you!"

The "fix"? She moved the text file from the root to the bin directory, where technically, the file was no longer publicly visible.

That 'pattern' was used heavily until she was promoted to upper management and the younger webdev bucks (and does) felt storing admin-level passwords was unethical and found more secure ways to authenticate.

I don't like interview questions that ask about which libraries you use or what libraries you like. I think these questions are stupid. I'm not supposed to like a library. I'm supposed to use the most suitable tool for the project at hand.

*during my final job interview*

*holding the folder that contains my cv*
interviewer: Wait, before I open this I would like to guess which position you're applying to.
me: Hmm okay sir? Which position?
interviewer: I see you're applying as a back-end developer?
me: Yes sir, I am.
interviewer: Aha! That's because you have a long hair? Like it is a requirement for every devs to grow their hair?
me: *laughs* i think so?
interviewer: Well our devs here also has long hair. You'll meet 'em soon.
...

That sets the mood of my interviewing process that leads me the job offer. LOL.

Been a ReactJS user for a year, today thanks to: @
chrisrhymes, @Devnergy, & @Hammster I decided to go into Vue, so much I like what I'm seeing.

For those that used both, what difference have you found in terms of performance and output size?

Oh, and using their nice resource: https://laracasts.com/series/...

> in da zone, headphones beating, caffeine rushing through my veins, snack-stack at 75%, code and commands flowing like campaign promises, I'm one with the keyboard... I can feel it ~(◉_◉)~

roomie: Hey J! J!
me: ಠ_ಠ I'm kinda busy, what do you want?
roomie: Dude don't forget to pick up bla bla bla
me: Okay
> Headphones back on, feeling the h4ckx0r fire resurge through my gut like a majestic phoenix (not to be confused with taco tuesday gut fire)
roomie: J...J! dude also make sure bla bla bla
me: ಠ╭╮ಠ I know, you don't need to be so specific with me.
> Headphones on...about to hit play again...
roomie: Dude do you happen to know bla bla bla

(ಥ﹏ಥ)
(ノಠ益ಠ)ノ彡┻━┻

FUCK! just tell me everything at once so I can go back to ignoring you and the irrelevant world around me!

I hate when people do this.

As a developer, sometimes you hammer away on some useless solo side project for a few weeks. Maybe a small game, a web interface for your home-built storage server, or an app to turn your living room lights on an off.

I often see these posts and graphs here about motivation, about a desire to conceive perfection. You want to create a self-hosted Spotify clone "but better", or you set out to make the best todo app for iOS ever written.

These rants and memes often highlight how you start with this incredible drive, how your code is perfectly clean when you begin. Then it all oscillates between states of panic and surprise, sweat, tears and euphoria, an end in a disillusioned stare at the tangled mess you created, to gather dust forever in some private repository.

Writing a physics engine from scratch was harder than you expected. You needed a lot of ugly code to get your admin panel working in Safari. Some other shiny idea came along, and you decided to bite, even though you feel a burning guilt about the ever growing pile of unfinished failures.

All I want to say is:

No time was lost.

This is how senior developers are born. You strengthen your brain, the calluses on your mind provide you with perseverance to solve problems. Even if (no, *especially* if) you gave up on your project.

Eventually, giving up is good, it's a sign of wisdom an flexibility to focus on the broader domain again.

One of the things I love about failures is how varied they tend to be, how they force you to start seeing overarching patterns.

You don't notice the things you take back from your failures, they slip back sticking to you, undetected.

You get intuitions for strengths and weaknesses in patterns. Whenever you're matching two sparse ordered indexed lists, there's this corner of your brain lighting up on how to do it efficiently. You realize it's not the ORMs which suck, it's the fundamental object-relational impedance mismatch existing in all languages which causes problems, and you feel your fingers tingling whenever you encounter its effects in the future, ready to dive in ever so slightly deeper.

You notice you can suddenly solve completely abstract data problems using the pathfinding logic from your failed game. You realize you can use vector calculations from your physics engine to compare similarities in psychological behavior. You never understood trigonometry in high school, but while building a a deficient robotic Arduino abomination it suddenly started making sense.

You're building intuitions, continuously. These intuitions are grooves which become deeper each time you encounter fundamental patterns. The more variation in environments and topics you expose yourself to, the more permanent these associations become.

Failure is inconsequential, failure even deserves respect, failure builds intuition about patterns. Every single epiphany about similarity in patterns is an incredible victory.

Please, for the love of code...

Start and fail as many projects as you can.