Hacker News Reader

As the lone IT guy, I built a new database to upgrade/replace the production system, it would have saved hundreds of hours of labor, but couldn't get buy in from management.

I had conversion scripts that worked, a reasonable plan for recovery if it didn't work.

I tried a few other projects, but eventually settled in to just showing up and waiting for things to break. It broke my spirit.

View on HN

There are a lot of risks to a rewrite of software. Doubly so when created in a silo. It pays to see it from the perspective of the company.

Additionally, you either worked on your own time to do so or you worked during company time. If you did this on your time, you should take that as a lesson to use your time for yourself, including looking for a new job if the situation isn't rectified. If you worked on this during working hours, then you may have wasted your employer's time and money. Be wary of doing that type of thing.

I did it on company time. The thing is, he wouldn't even look at it. He was so afraid of making a decision that any process change wasn't going to happen.

Unsurprisingly, the person who didn't want to change anything eventually ended up leaving.

Things are very weird in small companies.

That's pretty depressing

Reply on news.ycombinator.com