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
Search - "oki"
-
Me: "Delete this folder"
Windows: "Oki, done."
Me: "How is it still there, F5. Still there! Hey, you forgot to delete this one file. Fix it."
Windows: "Nope."
Me: "Why?"
Windows: "Requires permissions."
Me: "Eh, it was my file, but here you are, my admin credentials."
Windows: "None shall pass."
Me: "Wtf, this is my computer. Who owns this file?"
Windows: "No one."
Me: "What do you mean? Oh, time for your reboot pills, ms. Wandows."
Windows: "Noooooo... ... ... Welcome."
Me: "Ha, the file is gone. Glorious victory."
Windows: "It's just a flash wound."
Credit for style: https://mobile.twitter.com/cmurator...4 -
IF ONLY DOCUMENTATION WAS IN ENGLISH
In the past I've seen documentation that is great, and documentation that is conspicuous by it's absence.
Over the last decade, I've noticed documentation is getting WORSE.
I believe the reason for this is that those tasked with creating documentation have become so accustomed to the jargon in their own heads that they have LOST THE ABILITY TO COMMUNICATE IN ENGLISH, and as a consequence simply don't bother.
New terms such as "ThingamyJig" are defined as "A Collection of ThingamyJigs" — so you end up going round in circles and get back to square one.
They make little or no effort to provide simple examples.
If only companies who create languages understood that those who wrote the language may not be the best people to write the documentation.3 -
This is true I swear... I once worked on part of a project "optimization" that required, running a job on sidekiq in the background that spawns multiple threaded RPC calls on RabbitMQ (and be I/O blocking) till the jobs are done (or failed) so that it updates the status of the master object (that has the associated objects processed) and sends an email to the ops manager (just a summary email)... instead of using database locks... or dropping the email requirement...
I did it without arguing because I've already quit the job a while ago... -
My colleague once wrote 160 lines of ruby code that violated rubocop in 102 lines (and he thinks he is a "clever" senior)2