Ranter
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
Comments
-
d00td00t276302di work at a corp and it sucks
- we dont have master data
- we buy expensive licenses/support and do not use the software
- we develop scripts and webapps, then abandon the project after 2-3 years
- there are network engineers calling themselves the programming god, all they do is write spaghetti code and copy paste from some website found on google
- we develop the same webapp 100 times, because we do not know eachothers shit
Oh and the architects draw some circles and boxes, then present it to the higher ups. I've seen a few diagrams that are very similar. -
asgs11563302dWhat the fuck does Keyuser mean? Hope it is not "key user"
People fucking up shit repeatedly should be treated differently. They are doing good for none. Mistakes are done and can be done. But doing them time and again inspite of providing clear documentation is simply unacceptable. You can try to change such people but the sad fact is the change will be forced down your own throat -
MoboTheHobo3026301d@ars1 like you got a field price. The supplier who gives you the Data goes from 2$ to 6$. Thats entirely possible.
But not when the supplier has a system error and pushes all prices multiplied by 2. Its something we cant really check back. The key user fucked up then and didnt control the Data before and just imported it. -
MoboTheHobo3026301d@asgs yes I meant Key-User. Sorry english is not my native language.
And the saying is true. If you are a 3rd-Level Dev, the fuckups and problems of your Users becomes your problem.
Sure you can build in checks, but even that can fail or be to over engineered (efficiency/cost/reliability). And if it's the responsibility of the Key-User to check Data before a import and he fudges, you cant do much. Even implementing percentage rules with a additional check workflow wouldnt help, make the work more tedious and would end in a request to revert back. -
MoboTheHobo3026301d@d00td00t I feel you man, always same shit different day 💀
We got way to less engineers in our large corpo and to much business people.
Related Rants
I was wondering if anybody working for a larger Company in 3rd-Level faces the same personal problems as me?
We got alot of our own developed software and process. Regulary some Keyuser fucks something up by importing something wrong, which skews the master data. Its intended to be managed by the Keyuser.
Fast Forward, my Keyusers are so dumb, that they fuck up the master data import wrongfully. The process behind that then have wrong Data to operate (a numeric value neeeds to be set).
The Enduser then opens a Ticket for problem XYZ. Then the Keyuser forwards us the issue.
We already had that same issue X amount of times and its always the same reply. I made a FAQ, Knowledgebase entry, etc.
Nothing works, 2 weeks pass and a similiar tickets comes in...
Memory Capacity of the User exceeded after 1 Day. FML
Anybody facing the same shit?
rant
corpo
3rd-level
larg corporation