Details
-
AboutLearning Computer Science from Vellore Institute of Technology, India.
-
SkillsPython, Machine Learning, JS, React JS, Node
-
LocationVIT Vellore, Tamil Nadu, India
-
Website
-
Github
Joined devRant on 6/11/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
-
I worked with a good dev at one of my previous jobs, but one of his faults was that he was a bit scattered and would sometimes forget things.
The story goes that one day we had this massive bug on our web app and we had a large portion of our dev team trying to figure it out. We thought we narrowed down the issue to a very specific part of the code, but something weird happened. No matter how often we looked at the piece of code where we all knew the problem had to be, no one could see any problem with it. And there want anything close to explaining how we could be seeing the issue we were in production.
We spent hours going through this. It was driving everyone crazy. All of a sudden, my co-worker (one referenced above) gasps “oh shit.” And we’re all like, what’s up? He proceeds to tell us that he thinks he might have been testing a line of code on one of our prod servers and left it in there by accident and never committed it into the actual codebase. Just to explain this - we had a great deploy process at this company but every so often a dev would need to test something quickly on a prod machine so we’d allow it as long as they did it and removed it quickly. It was meant for being for a select few tasks that required a prod server and was just going to be a single line to test something. Bad practice, but was fine because everyone had been extremely careful with it.
Until this guy came along. After he said he thought he might have left a line change in the code on a prod server, we had to manually go in to 12 web servers and check. Eventually, we found the one that had the change and finally, the issue at hand made sense. We never thought for a second that the committed code in the git repo that we were looking at would be inaccurate.
Needless to say, he was never allowed to touch code on a prod server ever again.8 -
Just like basketball player need good shoes, programmer deserve a better keyboard.
Definitely not show off. Just wanna say I'm a big fun of Cherry MX mechanical keyboard.17 -
Python: let me manage those packages for you.
Node: here's the whole post office. You're welcome.
c: Write the packages yourself.
Luarocks: What the fuck is a package13 -
Dijkstra 1988: "Unfathomed misunderstanding is further revealed by the term 'software maintenance', as a result of which many people continue to believe that programs —and even programming languages themselves— are subject to wear and tear. Your car needs maintenance too, doesn't it?"
npm 2018: "Naaaah!" -
I'm actually making something for someone now. That means I have to make sure it works in IE. Which means no ES6. I die a little inside every time I type 'var'. 😫4
-
That’s fucking insane.... Probably a double post; sorry in advance... I just have to express my anger and amazement for a second.
Angry that they didn’t use such a high powered DDoS attack against say... Facebook or some shit like that, amazed at the sheer size of that attack...
I kinda wanna touch it.22 -
Dev: Microsoft is shit
VS Code: (ಥ⌣ಥ)
Dev: Oh not you dear! You're not like the other guys
VS Code: (。◕‿◕。)45