Me, a junior dev: * reports an important issue and a possible fix *

Senior dev 1: nah, it'll do just fine.

Senior dev 2: that won't be an issue, don't you see? It's under control, man.

Senior 3: why are you even here? Why are you even talking?

Manager: yeah, what could possibly go wrong?

* a year after releasing the product, one of the seniors got fired and another one was hired *

New senior: this thing is bananas, code is inconsistent and there's memory leaks everywhere, how does that even work?

Me: nobody believed me when I said that.

Manager: it did work very well, where's the issue?

Me: it's everywhere, goddammit! Don't you see?

New senior: junior dev is right.

Me: I've been a WHOLE YEAR saying that!

Manager: did you? Really? Nah, you didn't.

...

I'm tired of this shit.

Newbie telling me about the new Linux commands he was learning-
"So there's sudo.. It's like !important in CSS. Whenever something doesn't work normally, use sudo.
Me: 😵

I was newly hired to company. A customer came in yelling saying "there's a bug, this should do this but it's doing that..."
PM came to me and told me to "urgently fix this as this is an important customer".

So I started debugging for hours and asking around and all follow devs agreed that this is a bug. Then I found it!! And it was clear that it was not doing what the customer wanted.

I decided to look through this code history and found out that this part of the code wasn't changed for a year but the code commited before it did actually what the customer was expecting (whaaaa....)

Gathered the devs and the PM showing them what I found. They all looked at each other and then one said "ouuhhh right...yes it was doing this but we changed it to that..."

Turns out it's a feature not a bug, and everyone forgot about it.

FML

Me: Optimize a sort & match method in backend because users complain it's a bit slow.

Coworker: These algorithms are both O(n), so they're identical *closes PR*

Me: *start zoom call* "Heeeeeeeeeey Iiiiiiiiiii wouuuuuuuld liiiiiiiiike toooooo diiiiiisscuuuuus thaaaaaaaat puuuuuuulllll reeeeeequuuueeest yooooouuuuu cloooooossseeeed"

Coworker: "wtf are you doing, why are you talking so slow"

Me: "No matter whether I talk fast or slow, the information still reaches you in O(n) time, so why are you complaining"

I fucking hate it when people misunderstand the purpose of (or abuse) big O notation. It's an estimate of how an algorithm SCALES once the set increases in size, in which case you leave out both less significant terms and constant factors.

But those terms and factors are important when you're talking about the DIRECT PERFORMANCE of the algorithm on fixed-size sets, instead of SCALING to larger sets.

1n and 10n are both O(n), but 10x performance on a job that used to take 10 minutes is still significant.

string excuses[]={
"it's not a bug it's a feature",
"it worked on my machine",
"i tested it and it worked",
"its production ready",
"your browser must be caching the old content",
"that error means it was successful",
"the client fucked it up",
"the systems crashed and the code got lost" ,
"this code wont go into the final version",
"It's a compiler issue",
"it's only a minor issue",
"this will take two weeks max",
"my code is flawless must be someone else's mistake",
"it worked a minute ago",
"that was not in the original specification",
"i will fix this",
"I was told to stop working on that when something important came up",
"You must have the wrong version",
"that's way beyond my pay grade",
"that's just an unlucky coincidence",
"i saw the new guy screw around with the systems",
"our servers must've been hacked",
"i wasn't given enough time",
"its the designers fault",
"it probably won't happen again",
"your expectations were unrealistic",
"everything's great on my end",
"that's not my code",
"it's a hardware problem",
"it's a firewall issue",
"it's a character encoding issue",
"a third party API isn't responding",
"that was only supposed to be a placeholder",
"The third party documentation is wrong",
"that was just a temporary fix.",
"We outsourced that months ago.","
"that value is only wrong half of the time.",
"the person responsible for that does not work here anymore",
"That was literally a one in a million error",
"our servers couldn't handle the traffic the app was receiving",
"your machines processors must be too slow",
"your pc is too outdated",
"that is a known issue with the programming language",
"it would take too much time and resources to rebuild from scratch",
"this is historically grown",
"users will hardly notice that",
"i will fix it" };

It's important for developers to remember that......

For the rest of the world a "string" and a "thread" are the same thing..

At the end of the day, do not forget that the important thing isn't the language or the tools you use, it's about the problem you solve and the people you help.

passionately making love on Friday morning.

Cellphone buzzes for WhatsApp notification, ignored.
Call ignored, SMS ignored, again call, ignored.

She : whose that bitch calling you?
Me : it's no one important.
She : Checks WhatsApp, message from CTO, server crashed.
Me : Umm, darling, I need to fix this.

It's been 2 days she hasn't answered my call after she left.

Going on a vacation, so notify all clients that I won't be available during two weeks.

Client: well we have this huge presentation and here's a list of stuff we absolutely need for it
Me: sure I have a look.
Me: holy shit dude! That's gona take about 2-3 days. I'm leaving soon!
Client: it's realy critical to have them in a week as it's a very important presentation! Is there any way you can make it work? If we can do anything to help, just name it.
Me: well I'll do my best (planed 1 day for such rhings)
Me: *pulling a 15h day*
Me: here, all done budy! Did a 15h but now it's done, so do that presentation!
Client: oh, nice, but it wasn't that urgent
Me: ...

Next day:
Client ssh in to the server, fucks shit up
Client: well I did a thing and now stage and prod is fucked, can you do anything?
Me: (knowing it will take 30min to fix) well... I try my best. Btw. I'll leave in a few hours and won't take my computer, so try not to fuck every thing again, okay?

How do I un-idiot my users when it comes to clicking on dodgy email-links??

Got a forwarded email just there from a user who said;

Good afternoon,
Is the below ok to open?
I just tried but got a popup saying I've been blocked from opening it.
I'm not sure who it is coming from and I am not waiting on anything but as it says its from dropbox and is important, i know it's okay.
Can you unblock the link ASAP please?
This is really impeding my work-day as I need to know what it is and act accordingly.
Regards... user.

The Original email came from a random jumble of letters with a subject line of 'important dropbox program' - not only does it look dodgy but its english is horrible! It said;

"Hi tu my freind,

You tu still read a pending verrry important document sent by one of your own contact to be vieweddd.

Install "Highly Confidential english.pdf" by clickinggg here

*insert link leading to something called 'viral-update-trojan.exe'*"

I mean, seriously... help!!! 😢
We have sent emails explaining how to hover over links and to not to click them if it looks wrong.
No one does it.
We hired a company to send fake phishing emails to train users in what to do.
It made no difference!
We now make people 'verify' their email addresses when opening any sort of link to try get them to actually look at what they're opening.
We also strip emails of original attachments and create 'safe' html copies as we can't trust them to look at what they're opening.
Everyone complains about it but Jesus Christ, this is why!!!

Its so exhausting!! What is wrong with people!!! Argh!!! 😤

Clients who keep calling in.

I'm a first liner and sysadmin, both (official title is Linux support engineer) so I do tickets+calls+server engineering.

It's highly annoying when you've got a busy day with loads of calls and I'm the first first-liner and I'm working on an important/high-prio ticket and PEOPLE KEEP CALLING.

Every time I can write like a few more words and then the fucking phone rings again aaaand so fucking on.

Your concentration is gone, workflow interrupted and my short term memory is shit so I entirely forget what I was debugging.

But, phone comes first 😞

Even though I'm a web developer I work in a very small IT department, which includes just me and my colleague.

Yesterday we got a pretty usual request. Someone forgot the password to an excel file. We already started a brute force attack, but we had some fun going through the worst passwords we ever stubbled over in our carrier.

He was like:"Maybe it's just his name?"

Me: "Oooh or maybe it's just the brand and 123?"

We laughed a lot. Not really considering we could crack this "important" file.

But it really worked out. The password was the brand of the business unit and "2017".

I've sent everthing back to the user, telling him exactly how we cracked it... His answer was:"Oh yeah! I knew it was something easy, so me and x could remember it easily!"

...

Why do you forgive easy passwords anyway? If I can crack it within 5 minutes... Everyone can! ...

And if you do it to "remember it easily"? Why the fuck don't you remember it?

Private chat pops up. (- separator for new message)

Hello
- (1 min)
Can you help me?
- (2-3 mins)
Please it's urgeeeent!!!!!
- (1 min)
Come on you're online, I see the green dot.
- (5 mins)
Ok then I won't be able to work. Will write this down in the ticket.

- (15 mins) - new private chat pops up
Hi, we need to talk.
- (3 mins)
Regarding ticket XY, why aren't you responding? It's really urgent.
- (5 mins)
Please notify me as soon as you're available, it's really important!!!

- (20 mins, new private chat opens)
Hi mate, I think the devs are up to mischief. Said you're not reachable, I'll try to poke them with the stun gun.

- (60 mins, message in the official and only endorsed support room)
@all We broke staging, <Me> never responds and <Team mate who tried to use the stun gun> wasn't helpful either.
We really need this now!!!!!!!

- 30 mins later... la me:
@all I was in a meeting with the stakeholders as we had an priority meeting... What was so important that you not only ignored the rule of not messaging privately and even ignored <team mate>s instructions?

- 5 mins later, answer
no need to be so unfriendly.... We broke staging as we had to test stuff out for next week's sprint review [something which is still 3 days away or sth like that]. We really need to take a look in the team at it and for that we must have staging working now!!!!
- (La me)
If you need it urgent now, you didn't plan ahead. And if you didn't plan ahead, you have to wait for others. The sprint review and all other important days are planned ahead for a reason.
- (Silence)

- (20 mins later, private chat, team lead)
Will you finally fix staging now?

- La me
If it could wait 3 hours now and you / your team ignored all netiquette, it can wait till next day, too. We had this discussion more than once, I don't think I need to explain this further.

(Silence)

All in all, the joys of communication...

Now the fun stuff is when this not only happens with 1 team, but many teams....

Having 35 - 40 private chats and chat window looking like a christmas tree thx to the immeasurable amount of notifications and colors... Yay...

Did I mention that I hate the ego some programmers have -.

Code formatting is important when it's not too long...

Contrary to most people I really love to receive email related to jobs when I'm in holiday. I keep important alerts on.

It's like:
email: ***urgent, server down***
me (sipping mojito by the pool): fuck them. let's them deal with that
email: ***requirements all wrong, must develop the feature again***
me (enjoying a dinner): oh, I told them 100 times!, fuck all of them, work for me now, stupid moron.
email: I destroyed by mistake the db with an update..."
me (dancing like crazy): ahahaha I told you that support guys should not have access to production db, fuckfuck you, fix it yourself!!!

and so on..... I don't know, it just boost my pleasure during holiday.

Headphones ON ears means DON'T disturb unless it's important.

Talking about the chance of rain is not f*ing important. Especially when it's the 10th effin time I'm interrupted by nonsense officetalk in one hour!

Me: I'd like a new phone please.
Manufacturer: Okay, what do you look for in a phone?
Me: Well as long as the other specs are good, it's important to have a headphone port, SD card slot, and removable battery.
Manufacturer: Okay, fingerprint scanner. Got it.
Me: What?
Manufacturer: The only thing you want is a fingerprint scanner?
Me: No I don't care about that, what I want is-
Manufacturer: A fingerprint scanner, we know. Every device needs one.
Me: But-
Manufacturer: Shhh... Don't worry, we know our customers.

"Everyone must attend this meeting. It's really important that you all attend".

Me: *walks into meeting with other co-workers

Host: So what should we discuss today?

Co-worker 1: We can discuss how we did on the recently completed project.

Host: We'll save that for next meeting.

Co-worker 2: Any strategic plans for upcoming project?

Host: That too, for next meeting.

Me: Black Panther.

Host: That was actually a great movie. I saw it over the weekend. Who else saw it? ....

Me (in my thoughts): Just wow! 😂

PS: I still haven't seen that movie.

Devs: Feature A is done! Faster than planned even.

Manager: Hmm... what about feature A+B?

Devs: That requires feature B, and you said that feature B was not as important as feature A during our last meeting, remember? So we planned to do A, B, and then A+B. It's there in the meeting minutes.

Manager: But feature A does not make sense without feature A+B. Let's not release feature A just yet until we have feature A+B.

Then why didn't you say so during our last meeting?!

KISS.
Keep it simple, stupid.

At the beginning the project is nothing but an idea. If you get it off the ground, that's already a huge success. Rich features and code quality should be the last of your worries in this case.

Throw out any secondary functionality out the window from day 0. Make it work, then add flowers and shit (note to self: need to make way for flowers and shit).

Nevertheless code quality is an important factor, if you can afford it. The top important things I outline in any new non-trivial project:
1. Spend 1-2 days bootstrapping it for best fit to the task, and well designed security, mocking, testing and extensibility.
2. Choose a stack that you'll most likely find good cheap devs for, in that region where you'll look in, but also a stack that will allow you to spend most of your time writing software rather than learning to code in it.
3. Talk to peers. Listen when they tell that your idea is stupid. Listen to why it's stupid, re-assess, because it most probably is stupid in this case.
4. Give yourself a good pep talk every morning, convincing you that the choices you've made starting this project are the right ones and that they'll bring you to success. Because if you started such a project already, the most efficient way to kill it is to doubt your core decisions.

Once it's working badly and with a ton of bugs, you've already succeeded in actually making it work, and then you can tackle the bugs and improvements.

Some dev is going to hate you for creating something horrific, but that horrific thing will work, and it's what will give another developer a maintenance job. Which is FAR, far more than most would get by focusing on quality and features from day 0.

The next time you see developers wearing headphones, please understand that it's our most polite of saying:

"I'm in the freaking 'zone'. Don't you dare disturb my rhythm in coding and lose my momentum. Now unless it's reaaally that important, leave it in our group chat/email and I'll read it later."

Tap gently. We're at overdrive when we headbang to music while coding.

38°C, sunday afternoon, client be like: "Omg, I need you, it's important, can you call me?"

*calls client*

"So I got this E-Mail that said my SEO could be improved alot, why didn't you do that"

*looks at auto generated spam mail, hangs up*

Why is the ternary operator such a hated thing? I constantly hear people saying it's less readable, confusing, etc.

I think it's a beautiful, useful, and important operator and I use it constantly wherever readability won't be much affected.

How can you justify a repetitive if/else structure over a ternary, given that you're sure you're not going to put anything else in the ifs?

Whatever happened to DRY?
Whatever happened to KISS?

If those guidelines are what you code by, what's the excuse not to use it?

Because you can't read it as well? Familiarity breeds comprehension and legibility, my dudes.

So, my wife is in the hospital with two of the kids for an annual checkup. Should be nothing to worry about but still it's stressful and I want to be there.

I'd booked the day off (until the end of the week) and last week I got told, you've taken too many holidays, just the Friday is approved.

Ok, fine, I'll do some extra hours work from home and be there for the appointment. But fuck no, they schedule an "important" client meeting this morning and I'm required to attend.

TWO FUCKING HOURS and I contributed a sum total of 2 sentences which could have been filled in just as well by the other developer on the call

Just another reason I'm happy to be interviewing at other companies.

Every time I post a question to SO I feel so anxious.
Did I provide enough code samples and information?
Did I provide TOO MUCH information?
Is my English alright?
Did I really try everything else or will someone point out something totally obvious after that I feel that I need to delete my post because it's just dumb?

Feeling anxious right now... Worst of all: it's an important work related question, so I have to think about a new task because this issue was my only one and a road blocker.

AAAARRGGHHH!

Cmon guys it's an important security update..

Get your code reviewed by as many good devs as you can. Tell them to be harsh, swallow your pride, expect the code to be torn apart. Then rinse and repeat.

It brings the "know it all" fresh grads down a peg or two, and often brings those with low self esteem up a peg or two (when they realise their code is better than they thought.) Anyone can write code that works. But writing decent, clear, well-tested code that stands up to scrutiny is a different ball game - and it's important to learn that quickly.

I have no words to describe how I'm feeling these days. I have to do a C project for uni.

After a couple of years dealing with web dev, javascript, typescript, angular and stuff, for the first time I have a project where I have to deal with only two problems:

1) my code
2) my machine

No tools, no bloated libraries, no webpack, no json configurations, no tutorials.

It's just me, vim, gcc (actually nvcc, it's a cuda based project, but still) and the cuda manual.

I feel I'm actually building something.

Plus, the guy I'm doing the project with is cool with this stuff and most important he's open minded.

I'm happy

Customer: «We want all the users belonging to this organization share the same username and password»
[Editor's note: we are talking about 500 users, more or less half of the total in the system]
Customer, after some minutes: «It's very important for us having the web interface using HTTPS, because we care security a lot».
So, please, go fuck yourself. And die.

Alright, so my company wanted to redesign its old website, so we (the dev team) got tasked with making it happen.

Talking with the people making the marketing decisions for the site (think clients but in-house) :

CLIENT : We don't want any colors, black and white only, it's trendy.

US : Okay, but you actually do need colors for call to actions, to achieve the effect of levels of importance and such.

CLIENT : No colors.

Why would they listen to us, not that we are the experts are anything... Oh and they scrapped pretty much all of our CTA, why would you need those anyways, right?

Sometimes later, while coding the Dealer Locator :

CLIENT : The more important dealers will be shown on the map in black, the ones a little less important in white, and the ones we would rather not send people to will be in blue.

US : In blue? Blue, the only color in a sea of black and white? You do realize that the only thing the user is going to see are the blue ones, achieving the exact opposite of what you want?

CLIENT : We have decided.

(╯°□°）╯︵ ┻━┻

We live in a world where portability is more important than usability.

I've got to buy a fucking adapter just to get enough USB ports to use a mouse and keyboard with a monitor, as well as ports for other things like my laptop fan.

It's also becoming evident with the lack of headphone jacks to save that 0.000001" of phone size. It's fucking bullshit that adapters are required to charge phones and listen to music at the same time.

Android, you fucking cunt!

Battery saving, yes it's an important thing. So first you want applications to display a big-ass notification when they're running in the background. Fair enough, it can be hidden away by the user if they want to.

But now there's a big-ass notification and the applications STILL get force closed?!! If I'm browsing Tor and I have Orbot running, don't you think that I might want to KEEP IT RUNNING?!! Or better yet, if I'm connected to my VPN server and the application is actively using the VPNService API, DON'T YOU THINK THAT THAT SHOULDN'T BE CLOSED?!!!

But yeah, ARTIFICIAL FUCKING INTELLIGENCE is doing some leety-ass fucking battery saving. MY FUCKING ASS CAN DO BETTER BATTERY SAVING!!!

I'm the leader of a team developing a project at my company. Recently I had an accident which required me to have a surgery, and I was out for the last month.

Since it's an important project, our CTO reassigned a Xamarin dev to help my team (in JEE) while I'm out, you know, cause "C# looks like Java". The guy had to write a file stream handler, and - though the guy does a really good job - it's funny to see how desperately he's trying to understand how Java works with streams. Censored because of reasons.

Favorite dev tool? My keyboard. I don't like coding without my keyboard, it's a very important tool.

I built a tracking suite for our fleet of printers quite some time ago. Once a day, "bizteam" (aka sales) gets an alert detailing how many printers are in critical need of attention (out of paper, mechanical error, etc.), and how many of them are flat-out offline. They don't seem to care. I mean they do, I think? but. the offline percentage hasn't changed much in the past month or two.

These printers constitute a primary part of our business model and... screw it. they're goddamn important, okay?

A full 16% of our printers are OFFLINE. Most of those HAVE BEEN OFFLINE FOR 3 FUCKING MONTHS.

3% of our printers have been online BUT OUT OF PAPER FOR OVER A MONTH.

and what really baffles me...
We've convinced a few of these merchants to actually plug in their goddamn printers. (and yes, they actually *paid* for these things, and they're absolutely not cheap.) Some of those were previously both offline AND out of paper, yet after being plugged in, they're *STILL* OUT OF PAPER?! What the crap, people! It's a printer! it's not difficult! It's the same as every other fucking printer you have! and it's probably the same goddamn fucking model!

Did AlexDeLarge skullfuck your brain into mush? FIX YOUR SHIT!

!dev related whatsoever fuck off if this bothers you

Just got into a big argument with my brother in law because the little bitch was exposing my father and mother in law(which I adore) to the virus by virtue of this little shit partying every other fucking day, going out with people etc and then having my in laws pick him up etc.

I am not gonna lie, I love the kid, but this shit pisses me the fuck off, my in laws are over 60 each and I ain't about to fuck with the chances of my child's grandparents dying because some fucktard thinks partying is more important.

Been wishing for the motherfucker that would since a while now, just hope it's not this kid.

"Did you not see (x important announcement) guys?! It was posted very clearly in the group teams channel and everyone was tagged!"

"No, we turned off notifications for that teams channel so didn't see it."

"What?! Why on earth would you turn notifications off, everything posted there is incredibly important! You must turn them back on now!"

Channel history:
- @everyone "HEY GUYS IT'S FRIDAY! Let's celebrate by everyone posting their favourite gif! Go go go!"
- @everyone "Choo choo guys it's the training train! How about we all share our best training experience for a bit of positivity?"
- @everyone "Hi I lost my laptop can anyone help find it"

Yeah... I wonder why...

Client: it's very important that we go live with the app's sign up process.

Me: ...but the mobile apps aren't complete yet.

Client: Yes, but marketing says we need to start getting downloads and sign-ups so we get better ratings than our competitors.

Me: ...but the user won't be able to do anything.

Client: We'll add the rest later when we have users!

!rant
Our lead dev in the company seems to be a smart guy who's sensitive about code quality and best practices. The current project I'm working on (I'm an intern) has really bad code quality but it's too big an application with a very important client so there's no scope of completely changing it. Today, he asked me to optimize some parts of the code and I happily sat down to do it. After a few hours of searching, profiling and debugging, I asked him about a particular recurring database query that seemed to be uneccesarilly strewn across the code.
Me: "I think it's copy pasted code from somewhere else. It's not very well done".
Lead Dev: "Yeah, the code may not the be really beautiful. It was done hurriedly by this certain inexperienced intern we had a few years back".
Me: "Oh, haha. That's bad".
Lead Dev: "Yeah, you know him. Have you heard of this guy called *mentions his own name with a grin*?"
Me: ...
Lead Dev: "Yeah, I didn't know much then. The code's bad. Optimize it however you like. Just test it properly"
Me: respect++;

It's my first week working at shithole.co (can i say that?). My boss is a micromanaging asshole who knows the bare minimum re: programming. He thinks css is hard (no offense). I'm fresh outta college. He expects me to be able to do a very complicated api development through an equally complicated authorization process. Every fucking day "Is it working yet?" [This is my first week on the job]. I don't think he's read the documentation and I don't think he understands how to. As I am typing this out I realize I'm more educated than this dumb ass. Oh, some more context. Our senior dev is working on a more important project So we don't have time to bother him? So I am doing his job for 1/10 the cost. Oh, and i'm not allowed to contact him because he is too important. When the app inevitably crashes and no one knows how to fix it. I will give them my nutsack to swallow (can i say that?).

My manager is an idiot and a complete asshole.

Knowing that I was working on a solution for an important problem, he sent an email to our customers saying that the problem cannot be solved, and the customers need to take care of it themselves. He sent this email the evening before I was supposed to present my solution to everybody.

It's not the first time something like this happens, but this stupid individual RESIGNED ONE MONTH AGO. He's in notice period right now, and nonetheless he keeps fucking people like he used to do. WHY THE FUCK MANAGEMENT DOES NOT BLOCK HIS EMAIL!?

I really hate it when online sources aimed at educating people looking to get into programming attack specific languages. I'm ok with them recommending some good starting languages (ex. JavaScript, Python, etc.) but I find it extremely inappropriate and damaging when they list languages they consider "bad." Languages like JavaScript, PHP and Java constantly get called out even though they power a huge chunk of the web and services hundreds of millions of people use every day. IMO it's a huge disservice to tell beginners not to even look at these languages. We should be teaching the language isn't really what's important - it's what you build with it.

Believe me, it's really damn important 😬

When the impostor syndrome hits me, I try to remember my achievements :
- I won a national coding contest when I was 18,
- I made and still maintain a complex app for 15 years, still actively used,
- I cannot count the number of languages I know; too many of them...

Not bragging here, btw. It's just important to actually enumerate your achievements.
If you get hit by the IS, just remember what you did 😉.

Really unfortunate that we all just accept people being assholes because they're good at their job. I guess it's just the way the world is but personally I don't think you get a free pass to be rude just because you're a key player.

Life is short and whatever bullshit project for whatever dumbass company you work for is ultimately not that important in the grand scheme of things. Don't let your hyperinflated ego misguide you. Be nice to people.

"The client has an important meeting next week! You have two days!"
If it's that important why are we just hearing about it...

The headset rule. If put on, project managers, the pope and everyone should stay away the developers. If put on one ear, it is allowed to disturb if it's important. Headset off, party time.

In a marriage party.
Guy1: let's have the diner fast and run away. Have to deploy a very important update.
Guy2: brother, it's your marriage party.

Last week I was erasing a 2Gb USB thumb while copying some really important shit to my backup disk. I look at the terminal and see it's taking a lot of time to did zeroes on dev/sdb.
Then I realized that dev/sdb is the backups drive and I just erased the firsts sectors of my only fucking backup.
It's ok, I said, let's see what can TestDisk do for me. And it only could find an empty sad partition that had useless shit on it. Whdd couldn't even find the drive. Cat and dd vomited 160Gb of nothing to a file that couldn't be read. I was lost, because I failed doing something I'm really good at. And I did it because I was to stupid to check fstab...
It's the very first time I couldn't recover data, so I'm thinking about delete "Data recovery" from my resume skills and put "Data cleaning. Really effective. I can send you 160Gb of pure horse shit to prove it" instead.

Joined a call during a potentially important life event. Work laptop password expired this morning, personal laptop didn't connect to vpn, desktop not connecting to vpn. No one knew what's wrong on the call (just that it's not working).

Not a good call.

It's highly important that these wet wipes are not, and I repeat NOT, used by non other than professionals.

So... Manager pulls us in. Meeting in 10 minutes guys. I know it's unplanned, but it's important.

Not only is it the 10th time he's interrupted my workflow, but it's almost time to go home. And I was getting some important shit done.

Anyways, come the meeting: we are going to abandon all the work we've done on our microservice platform (2yrs+ in the making) and make it a monolith. Oh, and we have to do it in 4 weeks, because a client is asking for it. Oh, and you'll probably have to do overtime.

🤦‍♂️ FML

Client have this amazing idea about a website that they wanted to convert into reality by using our service. Me and my friend started working on it.

After a month later when it's almost ready, they informed they are not investing into the idea anymore. They would like to discard the project and will pay half of it.

I am eventually realising why signing a contract is really important

Users and Bosses.

I honestly don't know who is worse, the end user or the boss.

The boss thinks all you do is click a button and everything just works, so everything should take 30 minutes to complete, why on earth would it take a week to do something?

The user seems to think every tiny idea is the most important thing ever to add, so they tell said boss it must be added, and boss normally agrees.

I get it, Marge (Fake name), adding in a copy button because you're too dumb to press ctrl + c is way more important than updating the security after a Ransomware attack.

No boss, I can't add in 30 new things and make sure the security protocols are updated all before the meeting in 15 minutes.

If you think it's all so easy and just pressing buttons, why did you hire me? Anyone who can read and press a button should be able to do it....

I'm beginning to think that it's not important to know how to code anymore, but how good you are at handling management.

Please check xy ASAP IT'S URGENT!!
I'm already checking before client even finished writing.

Forcefully disconnected from server by client.

Ok, not THAT important I guess.. :/

Current list of developer skills:

* Can find 3rd or 4th best solution to most problems

* Easily ready to accept blame for anything to save time since it's likely my fault anyway

* Caffeine addiction only enough to make you worry, not intervene

* Can explain how JavaScript DOESN'T work, thus getting us both closer to understanding how it does

* Only choke on parts of presentations that aren't critically important, like minor details and Q&A

* Good at smack talking other languages I also don't know how to use

* can make a mean gumbo

I don't understand, you pester me to send you an email and stress how it's so important. I send you the email and you don't read it. I remind you about the email days later and you still don't read it. You miss a deliverable because you DIDN'T READ THE FUCKING EMAIL I SENT AND ITS SOMEHOW MY FAULT??!?

Furthermore, you call a meeting after the fact and ask me to read out and explain the contents of the email to you? GTFO you friggin time drain 🖕

Just in case you thought you and your tech job were weird I give you:

Herpetologist: I caught a turtle here in Costa Rica.
Camera man: Cool. What kind is it?
H: this is the white eared red footed mud guppy. See what's interesting is that it has white sides of its face. And red feet. And lives in Costa Rica. In the mud. It is not a guppy though. Guppies are fish.
C: Cool and why is it important?
H: It's a white eared red footed mud guppy.
C: what does it do?
H: It's a turtle.
C: yeah but is it endangered? Venomous?
H: Nope. Just a regular old turtle.
C: so you just ran 50 miles and dove in to a random body of water that probably contained malaria and herpes to catch a regular turtle.
H: well it's not a regular turtle
C:(glares) it isn't?
H: it is. But it's a white eared red footed mud guppy.
C: so why did you catch it?
H: I like turtles.

So look at it this way: you could be the camera man.

You know a good way to handle all of the issues with W10 force updating your system? Do it yourself FFS!

You know there are updates. Windows has been telling you ...

Pick a damn time, start the update and go get a coffee, lunch, take a dump or go home for the day.

It's *never* going to be the right time if you don't choose it. It will always be an inconvenience or you'll be "in the middle of something important" and then you'll get all pissy about it.

Yeesh ...

So it's 23h30 last night and I've turned on the projector to watch the last episode of Mr Robot.
As I start the episode, I receive an email on my phone telling me that some important Azure webjob is throwing exceptions...
Fuuuuuuuuckkkkkkkkk
1 hour later it was fixed, and I watched my episode. Win!

I absolutely hate it when people doesn't care about the ratio of a picture. It's worse when you try to explain them why ratio is important and they look at you like you're an alien.

So, I'm a Jr. Webdev started one year ago to work on a €200mln. retail platform. Our development team consists out of my Sr. dev who designed the whole platform and it's basically his baby. Now he's leaving and it's expected from me to do new developments, support, meetings with managers from all over Europe, roll-outs in new countries, deal with all the issues SAP has, eat their bullshit when they can't upload a .csv file because they are too stupid to check for missing leading zeros. Listen to important their new functions are that they want because 120% of the salespeople needs it. How stupid can this company be to take the financial risk? I'm done.

Found an answer on Quora discouraging to learn Javascript because "it's not as important as php". It was a question about frontend development. Soooo 2000

Some of the smartest and brightest people I know are arrogant as fuck.

And I believe they have all the right to do so, for they have earned it.

Be kind and leechers will drain the living soul out of you.

If you aspire to achieve greatness for self, then setting boundaries is important.

This does not mean, you have to harsh to everyone, rather it's about figuring out whom to give your time and attention.

Hey so found another tiny bug, well more like a typo, if you're​ a subscriber and you go to edit a post more than it's time limit in this after 57 mins you get the old can't edit after 5 minutes alert dialog message, super easy to fix (I guess lol) and not too important

It's 4 am in the morning.

I have an important test at 9.

My laptop decided now was just the right time to make the screen go black.

Sometimes Murphy just politely hands you your ass.

Damn hackers! Within the course of a week, the internet of my country has been DDOS-attacked three times! Last week the attacks came from Russia or China". Yesterday they came from Russia and Ukraina. Is this a part of the Russian military exercises Zapad 17? Well, when an important part of the infrastructure is down and thousands of civilians are affected, it's for real and not an exercise.

I usually convince myself like "no corporate/government has enough computational resources to classify useful information from enormous pile of worthless junk they could blindly collect from tracking every single step of all their users."

But every time I see this, it's like I hear them saying "Why we should bother? You just handpick the important ones. Thank you."

Can we all just have a moment of silence for BASIC...

Got caught in a YouTube spiral watching nostalgia need and never realised how big and important BASIC was when it came to home PC's (I'm 21 so have no actual experience with said PC's)...

Also that leads me to the question as to why BASIC isn't still used?

It's actually a really legible language ¯\_(ツ)_/¯

If a tree falls over in the woods..
And important dev work gets done and shipped,
And it's not in JIRA.. did it even really happen..

I got my new Oryx Pro today, from System76. It came with Ubuntu 18.04 LTS. I opted not to get Pop!_OS or Ubuntu 18.10, as I would prefer to leave the OS on it for the longterm.

Even at 15.6", it's a BIG laptop. It measures 18" from corner to corner, when it's closed. It comfortably fits in my backpack, which is a bit on the small side, but it's probably about 30-50% heavier than a MacBook Pro.

But that size and weight are vindicated by the most thuggish hardware I have ever seen in a laptop. As configured, this machine has a 4.1GHz 8th gen i7, 32GB of DDR4 at 2666MHz, an 8GB GTX 1070, a 250GB nvme system disk, and a 1TB SSD for data.

The display is set by default to 4K resolution, but I cranked that down to FHD for the sake of my eyes and the battery. I will try some games at higher resolution at some point, but for desktop navigation, I get more use out of multiple virtual desktops than in massive resolution.

I will comment tomorrow or the day after with the steps I've taken to bend this beast to my will, and it's also important to say that I have not finished yet. This is just a summary, but I should have been in bed an hour ago, so I'm gonna go do that.

Every time you use an unnecessary !important in css code, God kills a cat :(

Please don't use !important if it's not necessary.

I fucking hate stupid accountants!

Yesterday we went to a customer to talk to the accountants because we want to remove one of their unused PC's in the office.

First, just the way they think (and talk if) they are the most important and it's absolutely critical everything works 100%. I see they are important but not 100 times more important than everybody else!

They called us their EDP-guys (EDV in German, that's the translation I found). That insulted me a bit. I'm rather called IT-guy, I don't know anything about the fucking EDP systems nor want I to. I'm there to make sure the hardware works. But whatever, fine, call me what you want.

Then they straight up threatened us, because their work is so important, they can't afford to have downtime in their systems. They don't really care, but the bosses of us both do and if we fuck up they (the bosses) will hold us responsible. There is a fucking update for your piece of shit software (datev)! I don't do the update, I'm just responsible that the update can be deployed on the hardware. I'm not responsible if this update fucks your system and frankly I don't care!

I could tell them all of this but they won't listen. They always talk in this patronising arrogant voice, because they are so important and we better don't fuck up the update.

I'm there to help. I don't want downtime for your systems. I want you to work with our systems the best you can.
But fuck you, I hope the server burns down!

Wanted: Senior Software Engineer for important job at NATO

Required: all sorts of leadership certificates.

2 pages of jibber jabber. But not a word about the software stack or even technologies used 😂

It's the opposite of where they ask you have experience with everything, I guess they found out that wasn't working either.

So my girlfriend just flipped out and sad that her whole Dropbox was totally empty. All of her files studies, her jobs and even her poems and short stories were gone...
Turned out she has 2 accounts.
One for...@gmail and one for...@googlemail

this is actually not my first instance where someone asked me for help regarding an important account where they just didn't check if maybe they used one instead of the other.

I know it's good that they changed it and kept both addresses but some people just get confused by it

For fucks sake can people stop using phones while walking, especially in busy places it's getting fucking ridiculous not to mention dangerous, the number of people I've seen that have headphones on and are glued to their screens almost bumping into people. What can they possibly be doing that's so important that they cant leave their phone in their pocket for 15 minutes while they get to where they need to be.

I have a huge deadline coming up. It's important for the future of the project that we show a mostly complete version of the product to the client that day.

They ask if I can do it. I say yes, but it will be very taxing. And by taxing, I mean it's going to use up the remaining energy and motivation I have for anything. And I've made that clear to everyone.

Coworker:
Here's an unrelated task that will take 6.75 hours of your day and I will hound the boss until he makes you do it. And I am going to send you messages after work that foreshadow another day of doing things that aren't deadline related.

So when deadline day comes around and I have to present something that has two work days of work missing, they're going to look at me like I failed. And not that I had two of my days stolen from me doing miscellaneous chores that could have waited.

Two tasks at the top of the backlog that was approved by the scrum master, and pm. We finish them in a few hours. Pm comes out.

Pm: Why are you guys working on those tickets!?!?!
Us: because they are the first things in the list.
Pm: but the client hasn't agreed on the work yet.
Us: then why is it the top of our list!!!
Pm: cause it's important.

A lot of things dev say are true, but this one I don't believe as much:
Many devs say that it's important for everybody to learn a bit of a basic programming language, to learn about computers and how programs are made. I disagree, I think that instead people should learn *how* things work. Ex, in my school people always use a VPN to get around the proxy. I don't care if they know basic statements, I think it's more important to learn how a VPN works. Most of them don't even know what VPN stands for. Am I the only one?

every project leader's project is the most important!!!!!!!! not the others!!!!

fullstackclown! do this now!!!!!!

it's apes trying to impress apes, all the way down

People: "Well we could put this data in the address book.....?"

Me: "Wait, what does that data have to do with the address book? Does a given address need that data / is it specific to that address?"

People: "No it's not related to addresses ... we just thought we could put it there."

Me: ....

Me: "So if you use that address you always want that specific data you want stored in the address book?"

People: "Oh no it's not tied to addresses."

Me: ....

Me: "So help me out here, when do you use a given piece of data? In the example here, what made you add that information?"

-Silence-

People: "Um, I'm not sure."

Me: "I think it would be a good idea if we found out. That might provide us some important guidance here."

Before, when you bought $3k Cisco router you got the box that will run indefinitely as long as it has power in about any environment you can go to install it; with or without fans, it had more important business than to give a shit about such things.
Now, when you buy $500k Cisco box you get a over-engineered chassis with 5 separate fan modules with their own firmwares, self tests, watchdog timers and shitload of bugs. It's a fucking fan, it should spin, not do quantum chromodynamic simulations.

Pic related.

Next rant could probably be how Cisco's switch from monolithic to modular linux arhitecture (in order to reduce downtime) turned into having time bombs just waiting to do some crazy shit.

I remember the first time I had a code block, I sat on my desk for up to 18 hours trying to fix it. In the end realizing that my impatience is not helping me. It was all in vain. A tired mind did not help.

I finally came to realise that I was lacking on knowledge and a tired brain did not help. I did it the next day but learnt a huge lesson. When it's just not your day, it's not you day. A fresh mind will help next day. Relax, do anything apart from code.

Too much of code can drain you of ideas and smartness. You need to let your mind breathe. Life away from the PC is important too.

When you're really fuckin proud of that extremely clean, elegant, efficient 30 lines of code. It might not be important, but holy shit it's pretty!!

introductory rant

So I am new here, hi! :)

So the devRant android app does not seem to support this mail format:
user+devrant@domain
(the important part being the "+devrant" thing)

Now I waited 2 days for a confirmation mail that wouldn't arrive and was greeted with the "please confirm your fucking mail" popup every damn time.

"Okay, let's just change my mail to user@domain and deal with it", I thought. Guess what: You can't!

So I contacted the devrant team via e-mail.
And I waited.
2 days.
No answer.

Okay.

Delete account, recreate with other mail, be happy.

Don't worry, I'm not mad. It's just really fucking ironic.

Looking forward to a great community! :)

I have to comment, how the fuck do you guys stay up so late and work for so long into the night? It doesn't matter how much caffeine is in my system, my productivity eventually just reaches absolute zero and I can't go on without sleep. And that's being awake for like, 18 hours. At most! I'm frankly kind of jealous.

But hey, if you are that type, just remember sleep is just as important as food and water. If you've been up more than a day, it's probably time for bed. Your brain will thank you. :) </psa>

In a call with the big boss of the huge company I'm working for:

HER: Yeah, this MUST be in the next release or we better not even release

She's talking about a fucking carousel to let the user know its stuff has been merged, I get the point! It's important, but do you fucking realize that the user is currently NOT EVEN LOGGING IN?

HOW TF IS YOUR PROBLEM WHAT THEY SEE ONCE INSIDE THE PLATFORM IF THEY CAN'T EVEN LOG THE FUCK IN?

FUCKING BUSINESS BITCH JUST SAYING WHAT HAS TO BE DONE AND THEN PRENTEDING SHIT TO ACTUALLY WORK PROPERLY

Me: I don't understand, why is this not working?

After a few hours of debugging and continuous re-starting the server and most important praying to GOD

Me: F**k! how is this working? Ok let's not touch it, it's working

University makes us sign our documents electronically. What this means is that we're required to put pictures of our signature onto all sorts of declarations. Since none of the documents we "sign" this way are important it could be okay, but I don't understand why it's beneficial to encourage us to keep a photo of our signature on our computers, paving the way to identity theft.

Hurricanes that start with the letter F can go fuck themselves.

Fran - 1996
Floyd - 1999
Florence - 2018

All 3 hit (well Florence hasn't hit yet, but it's fixing to) NC and did significant damage.

I wanted a few days off from classes, but not like this man. Fucking hell I hope it doesn't take the power out for too long or destroy anything important (like people).

Something I have learnt in the past month:

Never settle for a low salary no matter how good a company sounds (unless it's a really prestige company) if they don't realise your worth and don't care about their employees. Salary is important. You are important. And customers are important. Any company that just values money, income, profit and growth over their customer and employee experience is a huge red flag. If your work life is so stressful that it doesn't let you have a good work/life balance then avoid it. What comes above being a developer is being healthy and I think alot of people don't realise this. It may sound good to work as an engineer for a big platform but if they only value themselves you are just a cheap slave, move on and do something respectable and enjoyable.

Just my life lesson in applying for grad jobs.

Co-worker is in his office.
Co-worker whistles continuously "The rains of Castamere" from the Game of Thrones series.
I like Game of Thrones.
I also like the series' score.
But not the way my co-worker interprets it.
Because it's wrong.
Anyway, he whistles.
Sometimes louder, sometimes less so.
It's very out of tune.
It's annoying.
I can't concentrate, let alone code.
Co-worker goes to a meeting.
Silence.
I delete the bullshit I've written earlier.
Then, I get some coding done.
Then, I'm relaxed again.
Then, Co-worker returns.
Now he hums.
It's the same song.
Over and over again.
Again.
It's not that much out of tune, but it's still annoying.
I can't think, I can't concentrate, let alone code.

My thoughts drift to a certain Red Wedding.
I imagine it in vivid detail.
Strangely, it's a happy place right now.
I imagine throwing my screen through two fucking walls.
I don't do it, because the laws of physics are against me.
But the thought is enough.
I'm at peace, again.

... also, I got to leave early today, so I got that going for me which is nice.

(I already had to tell that co-worker *not* to whistle loudly in the cafeteria - you can hear it in a big part of the building. We had some important customers over and Office Management was not amused.)

CoWorker: I fixed the code so it doesn't throw any errors or warnings anymore.

What He did? Well.. he just commented the whole important part and it's my turn now to really fix this C mess.

Each time I try firefox after somebody mentions it again or it's in my rss feed, it still seems to never actually advance

It's stuck and either gets worse or goes back to its stable non improving level again, how come do they still not have a proper mobile responsive tester, why are even the upgraded addons still suffering the same container and rendering bugs

how is it more important getting bad image by implementing mr robot malware, than getting on an actual competitive level

why is it default bloated with random pocket addon bullshit, why did it begin to lag, ..

I remember when I was using firefox for a good portion of my life and laughed at how google chrome is laggy, but nowadays theres simply no competition to chrome, its stability and developer tools

I wish there was competition, the grid tools were a great start, but then nothing followed and they just went back to their never improving flatline

NEW RULE

From the 15th minute of a meeting onward, my mind will phase out and I'll stop listening.

It's your care to make sure you say everything important before that happens.

I think it's incredibly sad that one of the first serious discussions I ever have with my child will be how to Google yourself effectively, to do it at least once a week and how to go about getting certain things removed (If you can) 😕

I really want to stress that we should add the ticket for adding the missing test cases in *this* sprint and not postpone it any further.

-- "Isn't there something more important to be added instead?"

There. ALWAYS. Is. Something. MORE. Important. The real problem was that we implement the test cases in the past to begin violating our definition of done. We have to fix and one point and we have to own that decision as nobody else will care about passing tests and test coverage. It's our job to care for that.

Yes, we can instead focus on all the other high-priorities task that should have been done yesterday, yet that won't change the fact that large part our codebase will remain an untested messy blackbox just asking for weird bugs and wild goosechases in the future.

Don't hide behind "high priority tasks". A job is done when it is fucking done and tests are part of that. Hurrying from one important task to the next will just mean we'll never do it. There is no better time than right now.

If code coverage got left behind in the past, then we'll have to suck it up in order to fix it as soon as possible, otherwise we'll just suck forever.

So ... I'm just watching an anime (Musaigen no Phantom World) ... and this scene isn't related to the main plot. This is the intro of the third episode - the intros of the first two episodes were about the "phantoms", "illusions" ... :)

It starts with a blue screen and the little fairy (it's a phantom btw) said: "When the PC goes crazy, you panic quickly."

In the screenshot he says: "It is important to back up your data somewhere in case of an emergency."

A second screenshot is added in the comments.

TLDR boss is an idiot.

Boss has an issue. Sends screenshot, and a one sentence explanation, boss-style (not really clear, but the screenshot helps).
I set to solve it, not a minute passes, the boss os calling.
Explains the issue, i tell him I'm working on it, will msg when done. He explains the problem again, and tells me to hurry. I tell him, sure, let's hang up, give me five minutes, so he starts explaining again, that it's IMPORTANT.

Finally hangs up, it didn't take more than 3 minutes to solve it, msg him, it's done. test it, screenshots for the two parts i solved (of the one he wanted corrected and one where a similar case is still as it's supposed to be, not altered).

He calls me, I start telling him this us what I did, the screenshot.... *Interrups*
This is not what he needed, it's important, IMPORTANT i say, and tells the problem again.
I'm pretty annoyed by now, and just calm fuckoff mood comes over. I practically told him to click the link and see for himself....

if you want to take 10 minutes for something i would explain in 2 sentences, is it really that important....

We had today a meeting in management that ended in a discussion about prevention instead of crisis and risk management.

Or to make it bit simpler: prevention instead of treatment.

In IT / management / government, treatment is usually the way - you let the crisis happen, despite knowing it could have been prevented, and treat the damage / crisis.

Needless to say, the discussion escalated like usual.

It's funny how managers are able to put sentences like: "it's important to have quality assurance like prevention but staying within budget should be priority" (loosely translated from German, it's hard - sorry)...

You mean the budget that exploded and quadrupled in size because you dumb fuckers pay no attention to quality assurance? Or the additional cost of hardware, maintenance etc. to compensate for the fuckups regarding performance evaluation and regression testing?

"We cannot prevent everything nor anticipate everything, it's safer to deal with an estimated risk than with the unknown"...

"But we'd need to invest in ..., which reduces value"

I could give more details, but I think the point is clear... the discussion became quite heated and the longer it went on, the more I wanted to have an morphine drop with suicide option...

Why do people hate prevention so much?

Is the concept that hard to understand? You prevent things to not deal with crisis.

You invest to prevent loss.

It's just one of these weeks where the only happiness consists of tipping the delivery guy with 20 % plus and getting an honest smile.

:(

When you are in the zone coding and you get a call at work "asking if your busy?" :/ then being told it's not important it can wait.... So you hang up and cannot remember wtf you were in the middle of.

"We don't need to design this page, we'll just wing it in dev. It's not an important page."

result: 47 jiras about choice of fonts, alignment, padding, missing images that were never provided, how it looks shit on mobile and can we make it black instead?

It's important to redo old projects and ideas, here is why:

I worked on a project about 6 months ago, it was mostly just a "coding challenge" and I worked on the project for 3 days and I didn't get it to work. But I started working on the project again from scratch 2 days ago and I got it to work this time!

The moral of this story:
Just making new projects makes it hard to see how much you've grown and improved. But redoing old projects (even if they worked) gives you a concrete representation on how much you've improved (and if you have at all😉)

Important memos to future self:

If the specs the client gave you seem written by a confused pre-teen, run.
If the client says something like "this can't possibly take THAT long", run.
If the client can't pay you enough, but reassures that (in return) he won't stress you and let you work in peace without imposing deadlines: he's lying, run.
If he politely asks to do something but then when you say no he keeps insisting, Don't. Give. In. Ever.
If the project seems shitty and not likely to have success, but hey, seems also simple and easy: it's not. But it's shitty anyways.

And on top of all: trust your fucking guts, you've been right tons of times by now. You didn't want to do this but you forced yourself, because "it's still an opportunity" and stupid slogans like that. Never again.

!dev

Look what I'm fixing to say is gonna make seem like a cunt and it'll probably be deserved but at the same time, I think it should be said too.

The increasingly high number of people fishing for compliments and attention because of their CHOSEN profession being important in the current times is starting get old as fuck.

I've seen so many people fishing for compliments; rather it be medical workers or truck drivers because their job is more important now than usual.

Like don't get me wrong, they're all necessary for society to function. But for crying out loud y'all chose this profession for yourselves. You knew this could happen whenever you decided to go to school for your job. You don't hear server admins bragging and fishing for attention whenever they restore access to a service.

Just do your job, know that everyone appreciates what you're doing even if it's not being verbally said, and let it end there. Personally feel that if you went into the medical field for the praise and recognition, then you went in there for the wrong reason.

Anyways, y'all stay safe and let's get this shit show over with already. Ya boy is going insane

"But using XYX is better and it's not hard to set up!"
No, fuck you and your recommendations.

It's too time consuming to set up that blazing-fast minimalistic modular shit, because I know I'll want to configure it to perfection until I bang my head against my tiny keyboard when I have finally realised that all the config I went througu only achieved the same outcome as the 'bloated' software I was originally using.

So, fuck you.
I'd rather get on with my life and get some work done.

It's not like I wasn't aware of XYZ in the first place; I'm not using it because I know what's more important to get my shit done.

Imagine going on quora and answering somebodies carbon offsetting question by pushing your own stupid fucking agenda with propaganda answers like

"oh we need rainforest money!"

"oh we need grassland!"

"oh support the cows"

jesus fucking christ, THIS is why we have a problem with people not accepting climate change, becuase every fucking liberal wants to pile on one another and have their 'most important' cause behind it

give me a break you fucking idiots, it won't be solved by acting this way

sorry this is in no way software related, but it's the only place left i have to rant (however in some ways it is somehow software related, due to being able to think about the real world without being an absolute idiot and pushing some stupid peer pressured political idea because your social identity and friends are more important than actual facts, but whatever)

I think a question should be added to tech interviews and maybe the most important one.

How many times in a week do you use Google/internet to look for a solution to/information about ur problems.

Tests for a developers ability to learn or try to figure things out themselves..

Feels like a lot of people on my team just do it the way it's always been done ,. Which is ahitty.. and if they don't know something,.. they need to ask someone instead of trying to figure it out themselves...

Reminds me of that fish adage?

They never learn how to fish....

I finally made my first production-level bugfix at my new job! 😄 After weeks of training and then being assigned a live bug, I resolved it quickly & elegantly, which helps prove my worth to the team.

Man, it's so gratifying to be making contributions that are going to affect real devices that actual people are using. It seems being a dev with a sense of purpose is nearly as important as enjoying what you do. ☺️

PTSD flashbacks of the 🤡s wanting us to change every subscription price less than 24 hours before a major release that would be the live version after we aired on national television...

management at its best folks. remember, your time doesn't matter, only theirs, it's way more "important"

🤡🤡🤡🤡🤡🤡🤡

<rant>
when a female feels it's important to clarify that she's female in the middle of a programming discussion. what if males did the same thing?
dev1 - This recursive function just blew up the server, bitch.
dev2 - I'm a dude, bro. don't call me bitch.
commence: miles of much lost productivity.
</rant>

This utilization shit is stupid! Seriously man what the hell! Yes yes it's an important number yes yes I don't even care. You want me to increase my utilization and at the same time be wary of the budget, which are unrealistically tight to begin with. It's freaking impossible! Who comes up with this shit?

You know what? Half of this shit ain't even my fault! A project was set for 200 hours and a guy wasted half of that trying to figure out just HOW TO CONNECT TO THE API! Like the guy only wrote 30 lines in 100 HOURS! ARE YOU FREAKING KIDDING ME! THEN YOU PASS OVER THE PROJECT TO ME AND SAY YOU HAVE ONLY 100 HOURS LEFT TO CONNECT TO THE API, GET THE DATA (WHICH BTW DOESNT EVEN EXIST), PARSE IT, AND THEN CREATE GRAPHS AND A FULLY FUNCTIONAL SOFTWARE, WITH A USER INTERFACE THAT SHOULD RUN AS AN EXECUTABLE!!!! ME? ALONE?

MAN FUCK YOU!

I think it's more important to have right kind of headphones and music than a good editor to improve productivity as a developer

Do you guys think it's fine to leave a company even if you're a team leader and currently working on an important project for them?

Because I feel sad, underpaid, and abuse on this company.

How many of you use the right data structures for the right situations?

As seasoned programmer and mentor Simon Allardice said: "I've met all sorts of programmers, but where the self-taught programmers fell short was knowing when to use the right data structure for the right situation. There are Arrays, ArrayLists, Sets, HashSets, singly linked Lists, doubly linked Lists, Stacks, Queues, Red-Black trees, Binary trees,.. and what the novice programmer does wrong is only use ArrayList for everything".

Most uni students don't have this problem though, for Data Structures is freshman year material. It's dry, complicated and a difficult to pass course, but it's crucial as a toolset for the programmer.

What's important is knowing what data structures are good in what situations and knowing their strengths and weaknesses. If you use an ArrayList to traverse and work with millions of records, it will be ten-fold as inefficient as using a Set. And so on, and so on.

Oh,I have learned a lot, I would not say from programming but from the career as a whole

Never get peer pressured
Always show empathy
If in a leading position, taking care of people is your top priority
Overconfidence will destroy a lot of good work
People by definition will always remember your mistakes
Never get over involved in the company you are working for, it's just a job
Your health is more than important
Nobody knows everything
Always be humble
There is a lot of bullshitters out there
Success is relative
Competition is high and there is always someone with better skill set, so you will suffer if you don't accept that

In this era, information is much more precious than money itself.

I'm not saying that information wasn't as important back in the days. It's just, at present gathering information is much easier than it ever was!! Especially on people who spend more time on mobiles phones and computers.

Formally stated, Newton's third law is: For every action, there is an equal and opposite reaction. As we're consuming information continuously, going through so many webpages, laughing at menes that are relatable and using apps that we need to perform day to day task. We're also providing information that we don't realize doing. This adds up to determining out individual personality.

One can never be too careful to prevent all these, but we can still minimize the damage.

Oh no 😱
.
So I have a database with 12 tables, It grows really slowly and it's not really important, so I just do a manual backup once in a while.
.
Today, I wanted to do a backup, and realized that the content of the only table I cared about has disappeared.
.
I miss you Data, rip

It's annoying when you're approaching the deadline on two separate projects and the AMs for both think their project is the most important. Leave me alone and let me do my job and both projects will get done, pester me and they won't. Pretty simple concept.

God I hate when dev work gets all political.
Our team had a technical meeting with a difficult partner/customer, that wants to connect to our internal service, so we are writing an Integration Service for this.
Apparently the project is very important on both sides and highly political so in the meeting there was a member of the Board of directors of them. We just wanted to check one feature to verify they can connect, etc.
After some minor bugs showed up, that guy goes on ranting about how this is all a joke ("Verarschung" literally) and how we did not deliver all features yet as promised (Note : that was not promised) and basically indirectly personally attacked us, our company and our team.

It's incredible how such assholes can stay in such positions.

It's been broken in production for two weeks, and you want to tell me it's "drop everything urgent" now? Is it important? Yes. Is it urgent? No.

Also, how the fuck did you not know this was broken for two weeks, and what the hell do you want me to do about it now? It's your codebase, it passed all the tests in staging AFTER I made my changes to the infrastructure.

I've built multiple profitable SaaS apps in my career, from scratch, by myself...

...but it's sure damn important to know wether fucking Cindy or Bob or neither can fit into a parking lot after muddling through stupid obtrusive rules that don't mean anything

"its to understand how you think"

yep, clearly don't know how to do that, that's why i'm taking this labrat, i mean, cognitive test

🐀🤡🐀🤡🐀🤡🐀🤡🐀🤡🐀🤡

Little brother wants learn programming and asked me if I could help him learn it.
"Sure, I'll show you how I learned it."

Gave him a book for starters to go through it. To have a slightly better time, I'll read his code and recommend some ways to go.

In my opinion it's important to learn to learn by yourself and learn to help yourself. Therefore I think this is kinda a good way to start with a bit of supervision from me.

What do u think of it, or how would you have done it?

I mean sure I could be some kind of teacher, but with a fulltime job + uni I don't really have time for that.

Today a client opened a ticket saying that all the content for a customer returns 404. Turns out it's kinda important to end a prefix on a separator if you plan to recursively delete all data /user/<user_id> or you might end up deleting a bit of extra data

I got so inspired when a chrome extension i made ,was used every day and is an important part of my every day student and development workflow.

It's on github right now.

New CTO.

New CTO pushes policy change to all browsers to open Facebook Workplace on every new tab and as start page.
Locks option to change it.
This also kills restoring tabs from past session.

New CTO handles the complaints
'It's fine to complain, we don't even have to agree. If this is important to you, then come up with a suggestion on how to solve this for all our employees. Business equirement is that one page is shown at startup, that's it. This has nothing to do with Workplace.'

Morning guys. How are your desks? Do you use normal desk or maybe standing one? Do you keep your desk clean or maybe it's more like a mess? Haha!
If someone is curious about my hardware on the photo:
- Dell XPS 15 9550
- Marshall Mode Headphones
- 16gb pendrive that's in business card format but just the important part of it as you can see
Post your desks!
Greetings from my coding buddy cactus 🌵

I never had a good boss, I've got two of the worst stereotypes of boss :
- the exigeant non-tech thinking he knows tech that asked to make an Android app for 1000€ and forgot to say he wanted an iOS app also
- The typical "fonctionnaire" (don't know if there is an equivalent in English, it's a state worker in France) manager, who thought his work was the only important work, who made me do a work I would have done in two weeks in 6 month

Just because it's popular, doesn't mean it's good.

An overengineered solution can usually be simplified without breaking anything important. An oversimplified solution can rarely be upgraded without major breaking changes.

Not everything needs to follow the "best practices" - if it's not a part of the core functionality, diminishing returns often kick in quite fast.

Some people just don't get it. When you meet friends who are either non technical or very new to programming, all they ask you is what language do you use.

The language is important but not everything. It's what you do with it that matters. Just because you know python, doesn't mean that you can do machine learning. Even simply asking what do I do is better than that!

The language is just a tool! Learn to be language agnostic please. Be a programmer, not a code monkey

I'm a developer, member of the A-Team. Actually I'm the leader of the A-Team.

We are incredibly skilled. Our problem solving capabilities is amazing, almost 100 times more effective than the rest of people. We produce code 10 times faster and better than anybody else. We have THE knowledge.

We can save the company in case of emergency.

For that reason, it's of paramount importance to nurture and protect the A-Team.

- When there is a bug, A-Team will not correct it. Because, if A-Team is busy, and bad shit happens, the company could be destroyed and we couldn't help

- When there is some important features to develop with a deadline, A-Team will not participate: A-Team must stay alert and ready in case of emergency

- If huge catastrophe happens and long hours, night and weekend are needed to fix it, A-Team will not risk burning the A-Team because it's the only high skilled team we have. The company cannot afford to have an A-Team member exhausted, underpaid, unhappy leaving or sleepy. Therefore, the company will sacrifice other less important people.

A-Team is company biggest asset and must be protected in any kind of situations.
The company should also pay training for them in order to increase their skills and make them unreplaceable.

These are my conditions. I'm the leader of the A-Team. You can't afford to loose me.

It's my yearly cleanup day, when I fully nuke down my windows installation, to clean out all the installed trash and residue.

Have moved all important data and I will be ready to fully refresh my computer as soon as it syncs, heres the question though.

I decided this time I'll create a dev vm, so I can just each time reset to point 0 and also because I miss having local development.

What new linux distros or flavours are out there that would be worth looking at? (I saw things like ubuntu budgie being mentioned)

If you use it and it doesnt break if I sneeze, mention it, I am open to getting to know other environments, even if its not my usual debian homeplace.

Dear managers:

Don't rush developers when they're reviewing code - telling them to cut corners.

You're not a dev (anymore). This shit is important if you want a system that doesn't blow up / takes months to make a simple change.

It's my name going against this approval and I (and the team) have to live with the code every day

Why in 2017 it's still so important for companies that their candidates have a motherfucking CS degree?

Most people I know with a CS degree are less skilled and knowledgable as I am in technology, and they tell me that all you learn in CS degree is a lot of irrelavant math and a lot of theory, with some rare places actually teaching you relevant courses.

What's more prefarable to a company, someone with a diverse tech experience or someone with a CS degree?

I've been working for 6 months now, and the boss tells me he's not satisfied with my work compared to someone that has 15+ years experience. He clearly states that for him - it's more important lines of code, than planning and defining the architecture which he don't like because that doesn't provide anything...

Of course, I can just jump into the code if that is whats important. I've seen the code produced by the other guy, and its shit.

The guy is a talker, and knows how to talk. I'm more like, hey lets create a simple design prototype or do some UML diagrams to get a better visualization of what we need.

Anyway, its just annoying to be compared to someone with many years of experience, its not that I can achieve it overnight...

So our sales rep got this email from some random dude yesterday (jan 12) saying he wants a simple webpage with a video background and some shit and that it's upmost important that it's done by jan 21.
Ignoring the fact that we are busy af, i thought well yeah it's doable. A simple onepager with some nice elements and some shit, ez pz.
In the email he also sent a link to a website simmilar to what he wants (as an example i presume) and it turned out to be a fully functional blog, a medium sized webshop (by the looks of it) and a whole lot of other stuff.
He didn't state a budget but seeing his demands I'd say his budget isn't much more than a couple of hundred €.

!rant
When did you guys join devRant?

I can't believe in just 6 months, it's important part of my daily life and the community has grown so much.

I joined on 6/23/2016

From my experience you can't really avoid bad companies with 100% success ratio. You can pay attention to the surroundings during an interview, you can research the company online, but in the end whether the company is good or bad is a purely subjective feeling. I think the most important thing is to make sure you don't get too attached to the company either emotionally or legally, so you can just gtfo when you decide it's not right for you.

Recently, I was hired by another company. It's a huge change for me and my career, so I'm looking forward for start in my new position.

By then, in my current company I just started a high-prioritary-super-important project for the company. So, I asked to my new company some extra time before join them in order to finish some stuff on that project and to make a good project transfer.

Today, halfway throught that extra time, boss anunced me that super critical project is no prioritay anymore due bussines decisions, so only we have to do is usual tasks (which my junior coworker can do without me).

I feel like newbie in the world of work.

I'm not jumping on your shitty bandwagon on LinkedIn for a "world-wide customer", "really important" .. and fucking shady blah blah blah to hire me.

I PICK the company I want to work for.
I RESEARCH the company I want to work for.
I DECIDE where I'm gonna be miserable,
it's my fucking choice.

You ain't selling it to me, keep sending your shitty messages i'm trashing as soon as I get them.

"When an engineer builds a building, it's very well built, but it's so ugly that the people tear it down. When an architect builds a building, it's very beautiful, but it falls down" - difference between systems engineer and systems architect

You must combine both, but the latter (beauty) is less important.

I think I'm getting to the point to where I'm burnt out at my job. Don't get me wrong, it's a great place to work. But it is very, VERY boring. And I'm starting to struggle to even pay attention anymore. I know it's important but I'm struggling to care. How am I supposed to do good work when I can barely even focus? Good code is not magic! I can't be barely holding my eyes open and expected to be worth anything.

I'm also still technically a junior developer which I have some issues with >_>

I was about 8. A family member was like a secretary, but not exactly. There are was a term used, but I can't remember. It's not really that important.

Anyways, I was like 8. Their job consisted of backing data up on.... Floppy disks. The software they used to back this data up just used a console and you had to input commands. Well this was amazing to me at the time. So they taught me the order of the commands and let me do it. Was the most fascinating thing to me. And it definitely planted the seed of interest in computers.

Some other early experiences also involve me hanging around the IT guy that worked with my relative. He taught me a little bit, such as some keyboard short cuts.

PM here. I'm having an interview with prospective junior devs next week. I want to make sure that they know a little and can learn a lot. Do you guys have any suggestions of how to ascertain that? I'm thinking simple programming exercises or something.

Again, it's not that important what they know today.

You constantly see these professional profiles with labels such as 'Expert'/10 years experience/senior/CTO/CIO/Consultant.

Isn't it funny when you go and work with these people in the field, they appear to be frauds? How can these people legitimately have these titles and know less than a snotty freshman year student? Their knowledge is so poor, a 14-year old with basic Windows and Javascript knowledge could outmatch them. If only this weren't true.

I think it's very unfair because they attract employers and they even get hired, while some of us with veteran knowledge in several fields don't get considered for a job.

May I add that it's always the funny guys who get a job. Apparently being a relatable frat bro at an interview is more important than having priceless expert knowledge.

You made a very important device used in pharmaceutical labs which stores important data, but for some fucking reason you decided to write the communication protocol so poorly that I want to cry.

You can't fucking have unique IDs for important records, but still asks me for the "INDEX" (not unique ID, fucking INDEX) to delete a particular one. YOU HAVE IT IN THE MEMORY, WHY DON'T USE IT?!
How the fuck you have made such a stupid decision… it's a device that communicates using USB so theoretically I could unplug it for a moment, remove records, add them and plug it in again and then delete a wrong one.
I can't fucking check if it's still the correct one and the user isn't an asshole every 2 seconds because this dumb device takes about 3 for each request made.

WHY?
Why I, developing a third party system, have to be responsible for these dumb vulnerabilities you've created?

I'm frustrated with an abundance of different *Ops we're having right now. You can spell a random word followed by "Ops", and it's probably a thing. I get that Ops people in general are important but when there is stuff like GitOps, MLOps, FinOps, it gets confusing pretty damn fast. There's no value in all these titles besides "duh" usually, since Ops are just Ops in most situations. They kinda can slap a tracing tool or two on top of your code base but in general they just do Kubernetes (with whatever's hip like Jaeger, etc.) nowadays and that's it. Hell, even "DevOps Engineers", for a majority of cases you'll encounter, are basically just Ops with a misleading prefix since it's just a way people call them nowadays for whatever reason.

I wonder if NPM prevents allowing a package to be it's own dependency. If not I have important trolling business to tend to.

Anyone else hate the phrase "as soon as possible" with a passion from the mouth of a client? I feel like saying it'll be f*cking done when it's done. Yes you're important but so is everyone else. Be patient, you only asked me to do it 3 hours ago. Just because of that, you've now gone to the back of the queue.

My company is getting a new website. This involves getting new hosting.

I made the old one, and it's all just static html. I'm not that attached to it but it's an important detail.

The bosses want the switch to the new site to happen instantly, but I pointed out that with DNS propagation times etc it can't really happen that way.

So I suggested the new web guys host our old site for a few days and we change the DNS now. Then when they want to launch we don't have to wait for the DNS and they can just swap it out.

This involves dropping 10MB of html files into the web directory on the new server.

For this service they are charging us for 2 hours of their time!

I guess I'm in the wrong business...

I've thought of the perfect analogy for people who constantly interrupt us while we are coding.

It's like you're a mechanic and you are working on a complex engine. You're focused on what you're doing, your hands are filthy, and you're just about to fit the part in that you've been trying to fit in for the past hour.

Someone comes along and asks you to help them open a pickle jar in the middle of your work. So you have to stop what you're doing, wash your hands, and then help them open the jar. By the time you're done your focus has completely shifted, you lost all momentum, and your progress comes to a complete halt.

This is what it's like for us when you come into our office or call us to ask us a question that isn't important or urgent whatsoever. It's especially frustrating when it's the same question that has already been asked 100 times.

devRant seriously cuts into my hackernews and regular news time. But it's important to have priorities, I guess.

Shady business practices. You see a lot of stories of people getting fucked over on here. Companies giving applicants a "coding test" to get work done for free, or guys promising to pay when the work is done(and then bailing), deserve to be thrown screaming from helicopters.

Some quick advice for people starting out:

1. If it's important, get it in writing. Promises are worth precisely dick, unless it's legally binding.

2. Exercise caution in interviews. The shadier companies know a lot of applicants are desperate, and they take advantage of that fact if they're allowed to.

Not sure if I'm rambling at this point, but fuck it. 🤣

I wish there was some 'sudo shut-the-fuck-up' which would shutdown the entire internet network, for humans to realise that it's important to step out of the pixels into the real world.

I keep posting that I need job and I appreciate the feedback but I feel just saying that makes it seem like I'm not trying.

Like. I legit don't know. Could it be my cv that's a dud? Thinking of paying a resume writing thing

Cause I'm actually trying hard af to learn new stuff as well keep doing what I'm good at.

I got one interview in a year and even then they didn't gimme the chance to show tech side. It's soo tilting.

I'm actually competent though inexperienced I think.

Any advice or questions please. I legit need to sort this out this year. Like its very important that I do.

Help.

I don't understand why people drive with high beam on, even when it's not needed!
Is it only in India or anywhere else too?

Literally, I'm so frustrated with this shit.

This point should be the very first and most important in the list of the learning driving.

I work full time in the data protection field for healthcare whilst investing all my free time into coding as a career change.

I've discovered that despite people telling you how much you need to spend every hour you get free to learn to code, you also need to consider the people closest to you. I was ignoring my partner who I live with because I thought this was more important and that she should be able to see that. But what's the point in being in a relationship if you aren't making an effort with each other?

It's OK to slow down and invest time into the people you have in your life. Give yourself a break.

Why does Visual Studio feel so special that if I add a file using File Explorer instead of through Visual Studio, it doesn't detect the file? Why does Visual Studio feel it's more important than the operating system itself?

*Executed maven build*

Me: What's this "no tests found?"
Senior: Nevermind it's not important. Just check if your code works.

Perhaps one of the most important things I will ever learn in life is how powerful regularity is. Read up on a topic once? Understand nothing? Read more random shit on it. Keep reading. And then stare in awe as things fall into place.

I'm writing this out not because people don't know this. Almost everyone knows this. But it's nice to be reminded of it. It's nice to be reminded that learning new things and honing bew skills is never easy. It's nice to be reminded that there's great knowledge and skills waiting to be learned.

This is not meant as motivation so much as it is meant as a reminder. Our colleagues may be garbage. Our clients may be garbage. Our bosses, the interns, the new dev, and almost certainly ourselves, are almost always garbage.

But if you've learned 1-2 new things today, the day wasn't garbage.

I'm just learning move semantics...

I know it's like the shittiest thing you can do in CSS, but sometimes I use !important because I feel dicking around with CSS for countless hours is !important.

@notRant
The devRant team seem quite humble. I feel it's quite important to have a humble face to your user base, because without it, our jobs as devs would be meaningless, even if you develop a cool app like {{ $coolApps[0] }}.
@include('funny_meme.jpg')
@endNotRant

Learnt a lesson today:

Never try out new hotkeys in a SQL query editor window.

Or if you do, at least make sure it's not connected to anything important :)

I was trying out new hotkeys and accidentally executed a SQL deploy script to rename something in multiple stored procedures in a large system.

Thankfully - so I saw after my heart stopped - it was only our QA db so not too bad, just a couple of devs set back.

Who woulda thought ctrl-l would execute :O

Oh my god, when will Firefox shut up about its motherfucking colours!? Themes have been a feature since forever, none of this is new. Also, I DO NOT want my fucking userchrome to be colourful, and I DO NOT want to be constantly bugged about this. It's a fucking browser. I want iit have a reasonably high contrast and otherwise blend into the edge of the screen, because for a web browser, the UI is not important and should not stick out.

I respect if someone has different opinions about UI, but it pisses me off to no end that Mozilla doesn't respect mine.

My most recent dream:

I come to the bookstore and see the 1000-something pages book called "We are not cucks". It's about how stoicism and how to defeat biases with thought experiments. The author is a German guy named ?.?.????rreize, I can't remember it precisely.

Everyone on the internet is discussing this book and why it is important. There are hashtags, influencers and virality.

Some time later the other book is released, 2500-something pages fundamental stuff called "We are cucks" with criticism of "We are not cucks" and whole new theory about why biases can't be defeated because of some "layers" IIRC.

>stick holding important data goes bad ("Insert DVD" IT'S A FUCKING FLASH DRIVE)
>no backups as it's a flash drive so my PC never did an auto-backup despite being configured to do so
>might be recoverable
>"short pins 2 and 3 while running tool to reconfigure NAND and controller then recover data from quick format with TestDisk"
*looks at drive*

Well.
Fuck.

it's not even sharp enough to slit my wrists with

It's really important to have a portfolio?
What's the value of a beautifull and fullfill portfolio? How it can help?

Why is the AWS Web UI so fucking terrible?!?
The most important buttons are always hidden somewhere in the Nirvana.. I have to scroll a thousand miles to get to the stuff I need (always below the fold!). They botch my settings all the time... it's a fucking ugly terrible UX... I have to click 20 buttons just to inspect some simple stuff. Fuck you AWS and your fucking UI. Fuck Fuck Fuck

Told some Devs today, "I've given you information on how to start testing. Java is easy to test. I've explained why it's important. Now, if the next change you make isn't tested, that's a choice. If you make that choice, please consider other places of employment."

So tired of lazy.

I'm glad that you have a Very Important Call but if it's longer than 5 minutes could you just fucking move to a room instead of just making noise for everyone on the fucking floor. Just take half a second and think how it would feel if everyone else did that.

purity might just be the most important thing when refactoring code you didn't write.

for real, if you purify everything in that code, future refactorings will go way smoother and reasoning even more so.

But it's no easy feat, sometimes you face cockroach code. cockroach code is code written nuke style. The fire and forget code that you shouldn't forget.

cockroach code's easy to spot. you can't know what cockroach code does without reading it's comments. roach code is fat, roach code retro feeds from different spots of macaroni. it does IO and everything else all bundled together.

roach code isn't easy to scratch out its async version. in fact, thats a property of roach code. If you can't make it async without a rewrite, you've got roach code.