Support and Maintenance en Jeddah
How we work in Jeddah
An error that appears once a year is forgotten for eleven months
Somebody fixes it in a rush, it never gets written down, and next time round it costs half a day again to work out what was going on. Every incident of this kind goes into a log with the cause, the fix and the date to look at it again.
The tests move the clock, they do not wait for the day
Freezing the system time on the critical date and running the whole suite is what turns an annual failure into something reproducible in ten seconds. Without that, the only way to check the fix works is to wait twelve months and hope.
The loaded calendar has an end, and it is worth flagging
The table feeding deadlines and alerts runs up to a specific day, and from there the system improvises without saying so. A check that looks at how far it reaches and warns with margin turns that into a fifteen-minute task instead of a phone call.
The year change is a date in the maintenance plan
Rather than waiting for something to break, there is a review noted down in advance: the table is checked, the tests are run with the clock moved forward and the reports comparing periods are gone over. Half a planned day and an emergency are nothing alike.
Answering your questions
What people ask us about Support and Maintenance in Jeddah.
If your question is not here, tell us about the project and we will answer with real context.
Ask us directlyReal work
Projects we have built
Full service · All the detail
Support and Maintenance: stack, process, use cases and FAQs