- Joined
- Oct 31, 2022
- Messages
- 1,744
- Reaction score
- 1,196
- Location
- Southern Tier NY
- Resorts Owned
-
HGVC Seaworld
Wyndham Smoky Mountains
Foxrun Lake Lure
Gatlinburg Town Square
I still maintain a big problem is web programmers always going for the minimum viable product to launch and the fixing it slowly afterwards. Well, that and restarting from scratch every time there's a major upgrade. And management not insisting that there be a checklist of KNOWN potential issues to be worked on and tested before launch.
I still remember when at work we updated from a somewhat dated command line system that read in a CSV to make accounts (i.e. using CSV as an API basically) to a shiny new web one. I told the programmer there were data sanatization concerns and showed the source to the existing system that showed all the logic and checks that we'd worked out over the last 10 years or so. Does the programmer use any of those or ask for clarification on what checks were needed (or review the documentation)? Nope - we got to spend the next 6 months re-finding all the issues from scratch and convincing the programmer to fix them in the new system.
I'm not going to comment on the management decision to go from an older system but one that no less than 4 or 5 people in the IT department could debug, update, and deploy changes to over to the web one that as far as I can tell, one person, the programmer, can edit or fix so there's LOTS of waiting for anything cause they're working on other stuff most of the time.
Anyway, there are benefits to being web based (less training needed to use it), I just think we should have been able to use the existing logic or at least gotchas rather than ignore that and figure out from scratch.
But I wouldn't be surprised if that's what's happening - there's no info from the existing systems getting to the creators of the new systems, so all the edge cases etc get to be re-found out! What fun!
I still remember when at work we updated from a somewhat dated command line system that read in a CSV to make accounts (i.e. using CSV as an API basically) to a shiny new web one. I told the programmer there were data sanatization concerns and showed the source to the existing system that showed all the logic and checks that we'd worked out over the last 10 years or so. Does the programmer use any of those or ask for clarification on what checks were needed (or review the documentation)? Nope - we got to spend the next 6 months re-finding all the issues from scratch and convincing the programmer to fix them in the new system.
I'm not going to comment on the management decision to go from an older system but one that no less than 4 or 5 people in the IT department could debug, update, and deploy changes to over to the web one that as far as I can tell, one person, the programmer, can edit or fix so there's LOTS of waiting for anything cause they're working on other stuff most of the time.
Anyway, there are benefits to being web based (less training needed to use it), I just think we should have been able to use the existing logic or at least gotchas rather than ignore that and figure out from scratch.
But I wouldn't be surprised if that's what's happening - there's no info from the existing systems getting to the creators of the new systems, so all the edge cases etc get to be re-found out! What fun!
