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
-
@cjhowald Unfortunatelty, a policy that requires every new feature to implement an on/off switch (if it's applicable) that defaults to off, seems like a good enough reason for me ;)
Those are the joys of working for a large companies that have lots of policies and require lots of signatures to do anything... -
@tnnn that is an unfortunate policy.
-
@KiteZilla While I smiled widely when I read your suggestion (I've daydremed for a while :D), there are a few problems with the idea:
1. I wrote that code while being employed and during my work hours. That means that this code belongs to the company that paid for it. I strongly respect that.
2. The idea and requirements for that feature came from the aforementioned company. It's theirs and I also respect that.
3. That feature makes absolutely no sense outside the aplication it was designed to work with.
Still, it was a nice one - thanks :) -
@KiteZilla The fact is that it was their idea. I just turned that idea into (virtual) reality ;) Even if it was technically feasible to create an app based on that idea, my ethics subroutine wouldn't allow me to that.
I just keep some fond memories of it and lots of experience I've earned during it's creation :)
I found this gem today.
It perfectly generated ~5 GBs of useless log in the past 2 years.
Years ago, when I was a young developer, I was asked to design and implement a complex but usefull feature. It took me some time, but I was really proud of my creation. It passed all the tests and was approved for production deployment. However, while the code was deployed, the customer asked for it to remain disabled for a while.
Months passed, other features were added often breaking the one I created. But I was relentless. I've fixed it every time. I've kept it ready for great launch...
After a few years, when I was already working on a different project, I received an email about my feature. It turned out that everyone simply forgot about it. You might expect that it was finally turned on... Nope, that email was a kind request to remove that feature from code.
undefined
painful goodbyes
dead code