When the fuck???

!rant

Somebody is having fun today 👍

This is my collection of geeky stickers! Do you like it? :)

alias such=git
alias very=git
alias wow='git status'

$ wow
$ such commit
$ very push

Don't you just hate it when you have some of the best programmers in the office with you, but none of them can fucking spell! Imagine having to spend more time decoding comments than actual code

Look here Mr Senior Tech if you don’t know 100% what you’re doing, don’t fucking touch the goddamn firewall with your fucking sausage fingers and you overblown call center team lead. I mean you need to have the confidence you would have if you were eating a banana and some one told you it was a poisonous berry, you’d laugh and eat it anyway, cause it’s obviously a banana. That’s the kind of confidence you need to have when fucking with the entire goddamn network configurations. I just went thru a 7 hour shit show because you THOUGHT you knew what you were doing. Not a damn thing was broken there. One service needed a hole in the firewall and you fucked all this beyond an easy fix. Now I’ll admit I don’t have that much confidence working with the firewall, that’s why I would fucking cal one of the companies that set it up even though we don’t necessarily have a support contract, it would have cost a lot damn less to have them work on it than for the whole company to be down and for me to have to stress over every fucking thing going (or not going) on.

I was working on a website for a client and he wanted an illegal (breaking TOS) functionality and I refused to implement that part so he paid me $800 less than what he owed me. Unfortunately there was no real contract besides some emails detailing the specs and payment, and if I pushed it any further he would've charged back the money he already paid me. Basically I'm screwed :/

I guess now I know how important it is to get those contracts and detailed specs written out from the very beginning.

Have you ever felt that you're being overrated by your employer ?

For our front end projects we use Cloud9 IDE

Now the business have around 100k+ files.

So Cloud9 is becoming slower and slower with every new project created.

So I was tasked to build a code editor where a new instance of that code editor will be created per project ( so, the new editor doesn't need to handle a huge file tree), so I "git clone" ACE editor and add to it GoldenLayout.js , FancyTree.js and some other plugins.

Now they think I'm a genius, and I'm like ... Eh? Should I tell them.. ? Will it backfire later ?

I kinda like the feeling.

What's the best thing to do in this case?

One thing I hate about documentation and tutorials is they always seem to use the simplest examples they can think of. They show you how easy it is, but if you want to use it in the real world start digging further.

Frustration is real... 100% since one hour

I love the feeling of closing a ton of tabs after finally fixing a bug.

Probably isn't a righteous rant... But there's a new guy who shakes his leg... All day... Makes my screen wobble... All day... Trying to think about about my code... But thoughts being shaken to the floor... All. Goddamn. Day.
*sigh*

"Could you please send a PSD or EPS for vectors, I only have the PDF."

-________-""""

If all you have is a hammer, everything looks like a nail!

This was something which my tech lead used to tell me when I was so obsessed with nosql databases a few years back. I would try to find problems to solve that has a use case for nosql databases or even try to convince me(I didn’t realise it back then) that I need to use nosql db for this new idea that I have, without really thinking deep enough whether the data in question is better represented using an sql schema or not.

Now, leading a team of young developers, I come across similar suggestions from few of my team members who just discovered this new and shiny tech and want to use it in production projects.

While I am not against new and shiny, it’s not a good practice to jump right in to it without exploring it deep enough or considering all the shortcomings. The most important question to ask is, whether some of the problems you are trying to solve can be solved with the current stack.

Modifying your stack requires more than just a week’s experience of playing around with the getting started guide and stack overflow replies. This is something which need to be carefully considered after taking inputs from the people who would be supporting it, that include operations, sysadmins and teams that are gonna interface with your stack indirectly.

I am not talking about delaying adoption by waiting for long list of approvals to get some thing that would bring immediate value, but a carefully orchestrated plan for why and how to migrate to a new stack.

Just because one of the tech giants made a move to a new stack and wrote about it in their engineering blog doesn’t mean that you need to make a switch in the same direction. Take a moment to analyse the possible reasons that motivated them to do it, ask yourself if your organisation is struggling with the exact same problems, observe how others facing the same issue are addressing it, and then make an informed decision.
Collect enough data to support your proposal.
Ask yourself again if you are the one holding the hammer.
If the answer is no, forge ahead!

I love devRant. But the people constantly saying "Python is shit" OR "Windows is for idiots" OR "Never use C it's ancient" OR "Microsoft sucks" OR any other fucking subjective opinion that's absolutely worthless drive me crazy.

I see many people here asking "Should I do [option1] or [option2]?" And the only responses are "[option3 which is not a fucking option you degraded fuck who thinks his/her opinions somehow matter in this discussion while they are clearly NOT helping]"

Sorry but this place has "Rant" in it's name so I thought this would be appropriate.

C: application not working
Me: k. What changed?
C: we didn't make changes
Me: k... *gets a tech team (W) on the phone*
W: Hey, what's broken?
Me: C's application. How do things look?
W: running healthy. I'll check logs.
Me: thanks. *gets tech team (S) on the line*
S: hey, everything clear on our end, will check logs.
Me: thanks *gets tech team (U)*
U: hey! They asked us to deploy their new version today during normal deployment time. Is it acting up?
Me: C, what did you change?
C: nothing major, just how we connect to W and S...
W&S: are you shitting me???
Me: U, will you please roll it back?
C: no! Must stay on this version, you need to fix your side!!
Me: nope. *calls U boss (UG)*
UG: U, you have my permission to roll back, they need to fix. C, if your boss doesn't like it, have them call me.
*rollback fixes problem*

IF I FUCKING ASK YOU WHAT THE FUCK YOU CHANGED, YOU BETTER TELL ME THE TRUTH, OR I WILL STRIP YOUR CODE OFF OUR FUCKING SYSTEMS AND SHOVE IT DOWN YOUR THROAT. MY JOB IS TO HELP YOU AND YOU NEED TO BACK TO FUCK UP AND NOT GET IN THE WAY OF MY JOB OR YOU WON'T HAVE ONE ANYMORE.

Dear people who complain about spending a whole night to find a tiny syntax error; Every time I read one of your rants, I feel like a part of me dies.

As a developer, your job is to create elegant optimized rivers of data, to puzzle with interesting algorithmic problems, to craft beautiful mappings from user input to computer storage and back.

You should strive to write code like a Michelangelo, not like a house painter.

You're arguing about indentation or getting annoyed by a project with braces on the same line as the method name. You're struggling with semicolons, misplaced braces or wrongly spelled keywords.

You're bitching about the medium of your paint, about the hardness of the marble -- when you should be lamenting the absence of your muse or the struggle to capture the essence of elegance in your work.

In other words:

Fix your fucking mindset, and fix your fucking tools. Don't fucking rant about your tabs and spaces. Stop fucking screaming how your bloated swiss-army-knife text editor is soooo much better than a purpose-built IDE, if it fails to draw something red and obnoxious around your fuck ups.

Thanks.

Having to do all programming exams with pen and paper.

On my first dev job ever, I got sent to the client's office after studying CSS on my own for 2 weeks.
Client: "So, you're the great expert your manager told me about?"

Javascript is wild

I'm just here sitting quietly, using tabs that convert to spaces. Tab users are scary and angry.

Can a person who just likes tech and isn't actually a dev be allowed on devRant?

I did a fucking scientific study about fucking rants and found a fucking high correlation between the usage of "fuck" and the number of fucking upvotes.

Best way to handle exceptions..

How to know a review was written by an american...

Repost: I like how a lot of code has the word 'forgive me' in it... Oh forgive me angular gods

Even as a developer, there is still a brief number when I look at an app's version, see something like 1.9, and think, "Ooh! Version 2 must be coming soon!"

I'm not particularly proud.

When I slice the head off a list I usually call the rest decapitated.

const [head, ...decapitated] = myList

"Look it's people"

Just doing my own projects all day, and actually be able to live of it