Some backstory, this asshole is a software architect who got "dumped" into our team after the prior team rage quite and informally got rid of him. We can't really fire him since firing is not something anyone on our team can do, best we can do is shuffle him around. He came to me today with a small issue. His data grid was reflecting a to string instead of a property. It stumped him alright. He had no idea what to do. I pulled his code and fixed his riddling issue in no time. His properties were being intentionally set to private and should have been public. In the absence of a valid property, the datagrid reflected a stringify call to the object. Hence the error he was seeing. It took me a whomping 5 seconds to figure this out.
I did some digging on the rest of the code he wrote, and I nearly had a heart attack. He started with multiple lists being fed to the data grid from an API (this was written by someone competent so no complaints there). This complete fucking idiot was re duplicating 4 lists into local variables. Upon figuring out why someone would do something so stupid, it had to do with a complete misunderstanding of the datagrid. The datagrid gets fed a datasource, and can be constructed from anything. This moron was recreating a custom object for the data source, doing a bunch of move constructors into the data grid to recreate a new data source. Now the code has 10 data sources: the 4 API ones, 4 new clones, one new clone of the 4 clones, and a property that is a clone of the clone of the 4 clones.
On a data grid that should hold 10,000 records, this guy is creating 60,000 EXTRA, completely useless memory records to load the grid!!! Needless to say, the performance was complete dog shit and Whitey is gonna have go to in and fix this fucking mess, as is tradition
I’m glad you guys exist because I wouldn't want to do whatever the fuck you’re talking about. A truly valuable trade skill indeed. Thank you for doing the needful.
Tried mentioning it and they say its because he's new to the team, and needs some up time. Most of the team has just resorted to giving up and dumping his shit problems onto someone else. They tried rotating him to a different part of the project until he got dumped back to general dev work
Each one implies incompetent (life) within competent (inception towards death) aka a competent force (loss) and those with-IN COMPETENT force (growth).
Others suggest employment by qualification to tempt one into a conflict of reason (competent vs incompetent), which distracts those within with fighting each other, while permitting those outside to control both sides of every conflict.
software architect
a) being form (life) within flow (inception towards death) implies being hard (solid form) within soft (liquid flow).
b) being partial (perception) within whole (perceivable) implies centered aWAREness of surrounding.
c) Architect (maker of form) implies flow (inception towards death) making form (life). Form implies RE (responding to) MAKE (being made of).
The incompetence issues are designed to keep the majority occupied against one another. Planned obsolesce within products also implies within those producing them. Civilization itself is designed for the planned obsolesce of its participants.
[ + ] bobdole9
[ - ] bobdole9 0 points 1.6 yearsOct 13, 2023 23:24:11 ago (+0/-0)
Dude probably has zero idea he can just use the original object.
What language do you code for? PHP is awful, but its hard to be retarded when writing in .NET
[ + ] Trope
[ - ] Trope 0 points 1.6 yearsOct 13, 2023 19:11:48 ago (+0/-0)
I’m glad you guys exist because I wouldn't want to do whatever the fuck you’re talking about. A truly valuable trade skill indeed. Thank you for doing the needful.
[ + ] Anus_Expander
[ - ] Anus_Expander 0 points 1.6 yearsOct 13, 2023 11:46:37 ago (+0/-0)
[ + ] heytheremyfriends
[ - ] heytheremyfriends [op] 0 points 1.6 yearsOct 13, 2023 11:48:18 ago (+0/-0)
[ + ] ImplicationOverReason
[ - ] ImplicationOverReason -2 points 1.6 yearsOct 13, 2023 11:54:02 ago (+0/-2)
Each one implies incompetent (life) within competent (inception towards death) aka a competent force (loss) and those with-IN COMPETENT force (growth).
Others suggest employment by qualification to tempt one into a conflict of reason (competent vs incompetent), which distracts those within with fighting each other, while permitting those outside to control both sides of every conflict.
a) being form (life) within flow (inception towards death) implies being hard (solid form) within soft (liquid flow).
b) being partial (perception) within whole (perceivable) implies centered aWAREness of surrounding.
c) Architect (maker of form) implies flow (inception towards death) making form (life). Form implies RE (responding to) MAKE (being made of).
[ + ] Not_a_redfugee
[ - ] Not_a_redfugee 0 points 1.6 yearsOct 13, 2023 12:23:46 ago (+0/-0)
[ + ] ImplicationOverReason
[ - ] ImplicationOverReason 0 points 1.6 yearsOct 13, 2023 12:41:52 ago (+0/-0)