Tazzi wrote:Tre-Cool wrote:I'd start out with something innocent like before going all passive aggressive on them, so um what sort of skillset do you guys look for in your software engineer's?
because from i can tell they appear to be a bunch of subgrade, shit throwing monkeys.
"Where do I sign up for fucking up technicians day? Just over here? Excellent, I have a great idea about stopping mid way for no reason!"
The employment roster is already overflowing with those who hold that particular qualification..
Got an email yesterday, for 2023 models they're planning on incorporating RPO filtering into SI... 2023 is only some modules, 2024 is supposed to be every vehicle..
They can't get RPO filtering inside tlc to work worth a shit and now they're going to throw it into SI.. Bunch of fucking idiots throwing new shit that doesn't even function into something that we NEED to work..
Did I call them fucking idiots yet, oh ya, fucking morons...
I've called them out many times with tlc fuckups, they don't respond to me anymore..
When I connect to a truck and it then asks me if the 12th digit of the vin is a 7.. what the fuck.. The god damn vin is in the popup that is asking the fucking question.. It's also in the dashboard of tlc.. Answer the fucking question yourself fucktards..
Connecting a 2021 equinox and it asks me if it has I19.. That's the letter I with 19 after it.. It's for 2020 model vehicles with 2019 engineering... a 2021 cannot have I19.. fucking idiots..
Can't stand now how when your using sps 90% of the current calibrations say unknown.. fuck you, what's in it?? Now we're programming modules that may or may not already have the current calibrations.. I was told this is because they handle it differently and they cannot ask the module to identify the calibrations.. bullshit. It's still a couple of 1a requests dipshit.. Why can GDS2 pull the cal info if I ask it, yet sps2 cannot.. It's fucking broken asshat..
I could go on..
