I am a senior software engineer. I refer to my current project as a chain of side quests.
All I wanted was to optimize a batch operation in our system. That needed a feature of a new version of our database. So I upgraded the database. But to utilize this, I needed to use a newer version of the db driver/sdk. The one we use is tightly coupled to the object mapper. So I needed to start upgrading the object mapper first. That is a major version change which breaks a few different spots in our system I then tackled one by one. I am still not done.
And this is why temporary fixes live in production databases for decades.
We had a similar issue with batch management, and the quick & dirty fix was to export the relevant db entries to .csv, run it through a parser, apply the necessary modifications, export to .sql with all new column labels, and then change the front-end to display the value of the new fields only.
Ran that through a cron-job every 5 minutes and done.
End users complained about the “nil” in the field initially right after inputting new data. The quick fix to the quick fix? Set a default value to “calculating, please stand by” instead of nil. They’d be frantically reloading, but never again blame IT.
Gamifying is a great idea that can help a lot of people. Unfortunately, it is also becoming part of some people’s official jobs, which I am not a big fan of.
I am a senior software engineer. I refer to my current project as a chain of side quests.
All I wanted was to optimize a batch operation in our system. That needed a feature of a new version of our database. So I upgraded the database. But to utilize this, I needed to use a newer version of the db driver/sdk. The one we use is tightly coupled to the object mapper. So I needed to start upgrading the object mapper first. That is a major version change which breaks a few different spots in our system I then tackled one by one. I am still not done.
And this is why temporary fixes live in production databases for decades.
We had a similar issue with batch management, and the quick & dirty fix was to export the relevant db entries to .csv, run it through a parser, apply the necessary modifications, export to .sql with all new column labels, and then change the front-end to display the value of the new fields only.
Ran that through a cron-job every 5 minutes and done.
End users complained about the “nil” in the field initially right after inputting new data. The quick fix to the quick fix? Set a default value to “calculating, please stand by” instead of nil. They’d be frantically reloading, but never again blame IT.
This is peak Hal_fixing_lightbulb.avi
Gamifying is a great idea that can help a lot of people. Unfortunately, it is also becoming part of some people’s official jobs, which I am not a big fan of.
https://www.theverge.com/2021/3/15/22331502/amazon-warehouse-gamification-program-expand-fc-games