Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "elliot"
-
From Mr Robot
“Most coders think debugging hardware is about fixing a mistake.
But that's bullshit.
Debugging’s actually all about finding the bug.
About understanding why the bug was there to begin with.
About knowing that it’s existence was no accident.”
— ELLIOT1 -
My friend at school (IT High School in Poland if you're interested) just asked me what version of Windows does Elliot in Mr. Robot use. After I said that it's not Windows, he didn't let me finish my sentence and said that you can't push macOS theming this far.10
-
"Debugging's actaully all about finding the bug, about understanding why the bug was there to begin with, about knowing that it's existence was no accident.It came to you to deliver a message."
-Elliot, Mr. Robot8 -
So here's the story about a big Fuck up by a TRAI chief in India
He posted an open challenge on twitter:
"Here's my 12 digit Aadhar card (social security no for Indians) number. Show me if you can do any harm to me. "
And Twitter obliged, a French hacker aliased @fs0c131y (Elliot Alderson) took the challenge and he started posting his phone number, email, and other personal stuff on twitter.
Still the official thinks he's safe and no harm has been done to him! He openly says, "Even if you get my bank account no what can you do?"9 -
"Most coders think debugging software is about fixing a mistake, but that's bullshit. Debugging's actually all about finding the bug, about understanding why the bug was there to begin with, about knowing that its existence was no accident. It came to you to deliver a message, like an unconscious bubble floating to the surface, popping with a revelation you've secretly known all along. A bug is never just a mistake. It represents something bigger. An error of thinking. That makes you who you are. When a bug finally makes itself known, it can be exhilarating, like you just unlocked something. Because, after all, a bug's only purpose, it's only reason for existence is to be a mistake that needs fixing, to help you right a wrong. And what feels better than that? The bug forces the software to adapt, evolve into something new because of it. Work around it or work through it. No matter what, it changes. It becomes something new. The next version. The inevitable upgrade." - Elliot, Mr. Robot6
-
Not a rant. Just some motivation for lazy fucks :)
Everything is binary. You do it or you don't. So tell me Elliot are you a 1 or are you a 0 !!
-Mr. Robot5 -
//Random Mr. Robot thought//
So this picture and this quote in general has been in my mind quite recently. The first time I saw this scene it just passed through my mind as just a wierd quirk of elliot. But upon further thinking, I question that given Elliot is someone who specializes in network security in a sense. A part of which focuses on finding exploits in networks or even software in general( basically finding the worst in them). And the more I think about that,the more I come to realisation that just like most programmers mix together logic in their life in dealing with people, this scene stands out as an example of just that happening with Elliot and what perhaps, makes him such a good hacker. Perhaps we could all learn from this, or perhaps I'm just looking too much into this. Eh.4 -
more of my favorite "about" sections from various users:
Jilano
"nothing."
Humble like a monk.
kindawonderful
"This user likes to keep secrets about himself."
Aw, hes shy!
molaram
"Part time evil corporation hater & armed infidel trying to blow off some steam."
Is that you Elliot?
dmonkey
"Computer Science student and Math lover."
Your love of math is suspect. I have not seen you participate in any of my math shitposting.
And under his skills
"I was ending up becoming a front-end developer, now I'm thinking to become a farmer after uni."
The total state of frontend in 2021. "Fuck it, I'd rather shovel horse shit than learn another
framework!"
Have you tried Horseshit.JS for that?
What about shove.js?2 -
First company:
- being sat at an office that didn't have chairs with proper back support. It would kill my back every day. Like sitting on a bar stool coding.
- not having access to basic resources (cafeteria, salary bonuses)
- being seriously underpaid ($200 under)
- not having an IT process pipeline (yeah, this is a huge one): no JIRA, no git, no VCS, no continuous integration, etc. I fucking spend 45% of the time fixing coding-unrelated shit.
Second company (very aggravating):
- dumb frontend bitch and privileged colleague who both kept telling me months on end to shut up and who wouldn't listen to my advice on anything, while my advice would actually help the company advance in productive ways. The key here is being told to shut up while stagnating. i.e. dead end job.
- people advancing in the company based on nepotism and favoritism, based on having tits and ass, rather than skills and independence.
- pointlessssssssss meetings where decisions are made solely based on the opinion of Mr. favorite senior dev. The rest just sits there like a bunch of sad saps and yay-nodders. Incompetent PO's who "would like to hear your input" but then when you give it, they completely dismiss you.
- pointlessssssssss monthly meetings with stakeholders, where the dev teams do nothing but clash and act like pussies in front of the PM just to get in his favor, but behind scenes continue to make the same mistakes and telling the CEO everything is fine. Goodness, how can it get more unproductive.
- completely antisocial and nepotistic 'colleagues' who won't even talk to you, let alone smile at you or be friendly. You saying good morning and them pretending you're vapor that doesn't exist. Go go company atmosphere! Especially during lunch, those are the worst times. Imagine sitting at lunch where everyone looks like you killed their dog and the rest is huddled up in little high school groups.
What else? The incessant and pointless smalltalk that makes me want to bang my head against the wall. Talking about dogs, kids, what show was on tv last night. The fuck man, do you have a brain?!
Third company:
- HR bitches who think they are the shit and developers are antisocial, helpless misfits, but they work with computers and they don't even fucking know what a status bar is! The irony!
- forced socializing and stigmatization for the opposite. Imagine coming into a company and you don't say good morning. Should that be a problem? No. Instead, everyone starts dogging on you and hating you just because you didn't smile in their faces and said: hiiiiiiiiiiii how did you sleep? Did you feed your dog? Fuck you.
Elliot (Mr. Robot): "Wouldn't it be awesome if there was a mute button for life?" -boop, boop, boop, boop...- Ahh.. there.. that's much better."
- CEO's sucking up to you but when it comes to salary increase, they say shit like: "Ahhh ya know, it's kinda difficult." Yet another dead end job.2 -
I really love Mr Robot.
The show though... not the guy...
But there's one thing that bugs me since the beginning:
For security reasons Elliot destroys all his drives and puts his RAM into the microwave which of course is effective but why would you even consider frying volatile memory?
Sure... the data can remain for some time but not that long that he would risk anything...
Any ideas?
Oh and btw... SEASON 3 IS NOT THE END??? LIKE WHAAAAAT?4 -
Thoughts on Mr. Robot the show? I'm halfway through season 2 and am utterly taken aback by the brilliance of this series9
-
The world itself is just a big hoax. Spamming with our running commentary of bullcrap masquerading as insight, our social media faking as intimacy.2
-
Mr Robot Season 2 finale was exactly what we wanted , but at the same time didn't expected to happen at all.
-
Looking for the keyboard Elliot uses In season 1 on mr robot and I found a bug
TECHNICALLY it's displaying the correct CSS...just the CSS code instead 😂2 -
The culture in engineering org is to address each other as 'brother' and seniors as 'sir'.
Bhai is the local term for brother.
This is how an average Slack message reads:
"We will make the changes.
CC: @John Doe bhai, @Marcus Fila bhai, @David Elliot sir"
And even though these people are part of the conversation, everyone tags everyone else in each response.
Slack culture is a mess.4