Details
Joined devRant on 2/22/2024
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
-
here's a shoutout to 90% of websites today:
NO, I DO NOT WANT YOUR F*CKING NEWSLETTER! STOP ASKING!
NO, I DO NOT WANT YOUR F*CKING NOTIFICATION! STOP ASKING!
NO, I DO NOT WANT TO SHARE MY F*CKING LOCATION! STOP ASKING!
NO, I DO NOT WANT ANY F*CKING COOKIES! STOP ASKING!
website publishers ary whining about adblockers, but keep shoving so much shit down our throats that even a dozen browser addons can't make the web usable. the internet was such a great place once, where did we go wrong?
(rhetorical question. it's when we made access to the internet so easy, that every 100% tech-illiterate idiot could get online.)14 -
customer: "hey, feature X is broken!"
me: *asks for details
customer, one week later: "feature X contains information about Y, that *must not* be"
me: *looks at code, at git-history, at related tickets
customer, one year ago: "hey, feature X *must* contain information about Y"
me, all the time: :-|4 -
is "drunk coding" really a thing? i can't imagine how.
i prefer working code, so when i'm writing code, i need my brain to be working. the "benefits" of alcohol, like reducing social inhibitions, don't benefit source code.8 -
a "landing page", that was just any and all features of the application forced into one huge, unbearably slow, indeniably confusing page.
which took months of work. which i said beforehand "nobody will use it". which now, through the magic of user tracking, is proven to be used by nobody.3 -
analysing a database problem and writing a 4-line fix: 5 minutes.
preparing a foolproof manual for the manager on how to apply the fix: 15 minutes
writing a manager-level explanation what the fix does: 30 minutes.
explaining it to the manager: 30 minutes.
writing a _detailled_ explanation why we need the fix: 60 minutes.
explaining it to the manager again: 30 minutes.
figuring out why our progress is slow:
_priceless_6 -
* break it into elementary steps, small enough to fit into your "estimation time unit", e.g. days or hours.
* estimate those steps for "developing at a leisurely pace" if nothing goes wrong.
* think about "what could go wrong" (list everything!) and adjust values accordingly.
* adjust total amount with experience values, like:
* times 1.2 for every manager
* times 1 to 4 based on which legacy projects i have to touch
and finally:
* multiply with `1+log(t/u,2)`, with `u` being the amount of useful data in the requirement description and `t` being the total amount of data in the requirement description
* sample: with our current "favourite" customer, about 90% of all tickets is garbage, so t/u = 100/10 = 10 => log(10,2) = 3.3 => multiply everything with 4.34 -
fucking piece of garbage postman!
WHY THE HELL do you auto-update yourself when i explicitly DISABLED updates?
why the hell is it just a "minor" update to switch to a version that FORCES you to have an account, even if all you do is use offline features?
and why is there no option to disable syncing your data to their server, even if it's not needed at all? YALL EVER HEARD OF A THING CALLED PRIVACY?
and why the fucking fuck of all fucked fucks DO YOU DELETE MY PREVIOUS OFFLINE DATA SO I CAN'T EVEN CONTINUE WORKING BY INSTALLING AN OLDER VERSION?!?
some dumb-piece-of-garbage-waste-of-oxygen managers decision to screw their userbase cost me several HOURS(!) of work already and probably will cost some more due to the lost collections.10 -
'the epitome of weak-willed and pathetic in the first place."
This bitch (@tosensei and his little friends) have been telling me those awful shit for MONTHS. And then they call me crazy when I dare to answer those disgusting abuse.
I HATE YOU. DIE.57