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
![](/static/devrant/img/pipeless-devrant-banner-white.png)
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Do you work for a big company? Normally, when you develop a script/tool that will affect the main product, it will need to be verified to hell and back by your testers, then package the test results into a company approved document before sending it back to you/your boss to be discussed in your daily/weekly/whatever standup meeting. Since that process will cost your company $$$, your manager probably just wants to stick to the stuff that works. lmao
-
nitnip18155yI remember a small-ish company I used to work for. All our project had separate git repositories but migrating to a dev or prod server was hell because boss was paranoid. He wanted to do it himself by downloading the project's tarball, extracting it to a folder on the server and then install the dependencies.
When I told him he could just cd into the project and just run a git pull instead of doing all that work he was afraid changes would break everything. Even in the dev server.
Running SQL queries directly in prod server though? He was all for it. -
I doubt that there's office politics, as my boss is the one who has to answer to our clients (all parts of the same parent company) when things don't work.
She just wants to play things safe, although the worst my scripts can do is fix our indexing issues and improve the performance of the system
Why dont people trust you?
I was hired to be an SQL developer, I don't actually get to do much development, normally doing something involving copying and pasting in Excel.
Some of our databases were running slow and we noticed some (a few hundred) indexes were in shit state.
I knocked up a couple of scripts, one to reorganise indexes that were up to a certain amount of fragmentation and one to rebuild the indexes
My boss wants them tested (they were several times in dev) we've had these for over 3 weeks, but she doesn't want to run them.
Instead of fixing hundred of indexes she decided I should contrate on fixing some historic data issues that are preventing 10 indexes from being rebuilt.
Now there are serious issues and the CTO is asking why the indexes haven't been fixed.
I could have done this nearly a month ago, but now it's turned into a huge fucki g deal, and no doubt they'll try and push it back on me
rant