Details
Joined devRant on 9/16/2020
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
-
@AlmondSauce @iiii @010001111 yeah, sorry about that. I reflected myself and noticed that I was not in such a good mood, to put it lightly.
State during ranting:
* I felt the urge to harass him in some way. What I, myself, consider plain toxic (yes, ik, obvious contradiction; emotions are illogical).
* Frustrated over the fact that I cannot confidently classify whether he is a troll.
* Angry at myself for being emotionally invested into some random online thread.
* The frustration you felt while you read the thread/argued with him.
To Do:
* Among other things, get my toxic side in check.
In retrospective, I consider this rant more or less spam. Again, sorry for posting this and contributing to the toxic side of devRant. Should I delete the rant or leave it up? I'll leave that choice up2you. -
@IntrusionCM fair point, but it's not always that easy. In my case, it silently crashed without an error in sight. The developer had to play the old "guess where it is" game across several components, each written in different languages (yes—glued together in one project), whilst questioning whether the JVM is the one silently crashing (niche field; don't ask). Not gonna lie, I still feel sorry for him. Poor guy debugged that beast of a project.
-
> Why do you keep shit that might unleash complete havoc cause it hasn't been touched since years and noone knows id it still works?
That happens when you don't write test (we don't do that here; no idea why). It's the fear to brick ancient depends.
Story time: I once refactored old af code and everything seemed to work fine at first. Unfortunately, I fucked an unused internal API, causing issues later on when someone used it.
Did I introduce a bug in the core? No, but I did change some logic. I largely refactored small "findX" methods which basically, instead of returning null if it doesn't find anything, returned a new object based on the search input. This obviously invited a "Test the application manually and fix NullPointerExceptions on demand" situation.
Truly a shit show. -
@N00bPancakes true. Although I assume that an additional law for situations like this is more convenient for lawyers, as they do not have to string together unrelated/loose laws. Well... at least for one side.
-
Source: https://devrant.com/rants/2944169/...
Backup: https://web.archive.org/web/...
