top | item 39477373

(no title)

DamnableNook | 2 years ago

Out of curiosity, what was the argument against it?

discuss

order

dirtybirdnj|2 years ago

I had a proof of concept for us to migrate sites to a static / low / no cost hosting option.

They were unwilling to spend time "training" the team to learn react (in 2020).

They were unwilling to let their senior FE dev spend any time with me to correct the CSS issues I was struggling with.

They used this deception and dishonesty to say "it didn't work" and wasn't worth any more time. I build a prototype in a week. It's not like I spent month(s) on it without any ROI. They just wouldn't look at it because that would mean acknowledging I and or / my ideas had value.

The closest thing I got to an answer is that the CMS they preferred, which was chosen 10 years ago by people no longer working there... was the only way they could support client sites. Because that's what they've been using. Turnover means it's so hard for us to support anything new because we have no time...

Basically they Brawndo'd me.

It was hard to stomach getting fired by the incompetent people driving the business into the ground when I was literally pleading with them to implement money saving measures.

The horse sometimes would rather kill itself than drink the clean water you've found... that's just life. It's hard to accept.

https://i.redd.it/h2lmsdwqtci81.jpg

mobilefriendly|2 years ago

The old content can become a liability. Maybe the brand has shifted, or norms have shifted and the old content is off-key.

dirtybirdnj|2 years ago

It was not an issue of refining the content on one site, you make a good point though.

It was more of an issue that they had a bunch of clients on an old CMS system, and they did not want to make any changes the way that the sites were built or hosted.

I can make arguments for and against either side of this idea, it all depends how you want to run your business.