Details
Joined devRant on 7/9/2016
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
As to the request of two devRanters, I just did https://systemof.thedown.website
On my way to south Germany in the car and was bored and I've got two ssh clients on my phone ;P
Credits for the idea: @Codex404 and @xorith12 -
!dev
It was late night after work I went into Macdonald's take-away:
Me: Can I have a Maharaja Mac Medium Meal with extra regular fries?
Guy: Yes sir, that will XX.XX amt.
Me: Gives him my card.
Guys: So what's the pin?
Me: What??
Guys: The Pin sir.
Me: Are you ok? Who the hell shares a pin with you?
Guy: Sir, we don't have a wireless swipe machine.
Me: So why is it a take-away if I have to come inside and drop my pin anyways?
*Guy looks awkwardly at other employees. :/
I had to finally get out of the vehicle and I took another 15 mins seperately explaining him why cards have a security pin and that the word security isn't a joke before the pin. With this, I might have also slipped in some GDPR cookie policy along with it. and why Microsoft bought GitHub. Good Lad. He will learn.16 -
Asus introduces dual screen laptop with touchscreen instead of keyboard. Just imaging programming with that
DISCLAIMER: it’s just a concept39 -
* Selects text to copy *
* Ctrl + C to copy *
* Selects text to be replaced with copied text *
* Ctrl + C again instead of Ctrl + V *
Instant rage.36 -
At Job interview.
Interviewer: Where do you see yourself in 10 years?
Me: I see myself as the leader of a raider group, robbing and scavenging together pieces of what is left of the civilization in hopes to build a weapon powerful enough to take the world back from a rogue AI, which I built myself few years earlier.
Interviewer: What!?
Me: What?15 -
Just found this website for Regular Expressions:
https://regex101.com/
In-case anyone struggles like I do10 -
Spent fucking 11 hrs on fixing a stupid bug in Laravel that caused all my unit tests to fail. Just because that unit testing method has no unit test...
-
1. Buy boxes of orange juice, almost past their expiry date.
2. Put boxes on the hot office windowsill for a few weeks.
3. Cool down juice in fridge.
4. "Hey dear coworker, would you like a refreshing juice box on this hot spring day?"
5. Watch coworker retch and vomit, spitting blue-grayish juice over his desk, crying: "Why would you give me old moldy juice without checking the date?"
6. "Do you remember when you told me you didn't have time for unit tests? THIS IS WHAT HAPPENS, DAVE, THIS IS WHAT FUCKING HAPPENS WHEN YOU DEPLOY UNTESTED CODE.... NOW FINISH YOUR JUICE!"32 -
Steps to writing more readable and cleaner code:
1) write shitty code that gets the job done
2) take a screenshot of set code
3) post it on devRant and blame it on a coworker
4) someone will reply with a clean solution within a couple hours
5) copy and paste that solution then push to repo11 -
When you have something in your clipboard but then press Ctrl+C instead of Ctrl+V and end up with a blank line.27
-
Hey everyone! @trogus and I are headed to TechDay New York tomorrow (May 10) and there will be a devRant booth in the social network section. If any devRanters are attending, you should definitely stop by our booth! There will be free swag and we’d love to meet some fellow ranters!37
-
"You gave us bad code! We ran it and now production is DOWN! Join this bridgeline now and help us fix this!"
So, as the author of the code in question, I join the bridge... And what happens next, I will simply never forget.
First, a little backstory... Another team within our company needed some vendor client software installed and maintained across the enterprise. Multiple OSes (Linux, AIX, Solaris, HPUX, etc.), so packaging and consistent update methods were a a challenge. I wrote an entire set of utilities to install, update and generally maintain the software; intending all the time that this other team would eventually own the process and code. With this in mind, I wrote extensive documentation, and conducted a formal turnover / training season with the other team.
So, fast forward to when the other team now owns my code, has been trained on how to use it, including (perhaps most importantly) how to send out updates when the vendor released upgrades to the agent software.
Now, this other team had the responsibility of releasing their first update since I gave them the process. Very simple upgrade process, already fully automated. What could have gone so horribly wrong? Did something the vendor supplied break their client?
I asked for the log files from the upgrade process. They sent them, and they looked... wrong. Very, very wrong.
Did you run the code I gave you to do this update?
"Yes, your code is broken - fix it! Production is down! Rabble, rabble, rabble!"
So, I go into our code management tool and review the _actual_ script they ran. Sure enough, it is my code... But something is very wrong.
More than 2/3rds of my code... has been commented out. The code is "there"... but has been commented out so it is not being executed. WT-actual-F?!
I question this on the bridge line. Silence. I insist someone explain what is going on. Is this a joke? Is this some kind of work version of candid camera?
Finally someone breaks the silence and explains.
And this, my friends, is the part I will never forget.
"We wanted to look through your code before we ran the update. When we looked at it, there was some stuff we didn't understand, so we commented that stuff out."
You... you didn't... understand... my some of the code... so you... you didn't ask me about it... you didn't try to actually figure out what it did... you... commented it OUT?!
"Right, we figured it was better to only run the parts we understood... But now we ran it and everything is broken and you need to fix your code."
I cannot repeat the things I said next, even here on devRant. Let's just say that call did not go well.
So, lesson learned? If you don't know what some code does? Just comment that shit out. Then blame the original author when it doesn't work.
You just cannot make this kind of stuff up.105 -
How to become cool in a developer community:
- try javascript for the first time
- pretend to use it like your favorite programming language (99% C)
- notice it is different
- rant about how stupid is javascript and its users7 -
FML. All those "train your own object detection" articles can go burn in hell. Not even TFs pertained models work!10
-
Dev: Microsoft is shit
VS Code: (ಥ⌣ಥ)
Dev: Oh not you dear! You're not like the other guys
VS Code: (。◕‿◕。)45