To be honest (and a bit ashamed) it was just a macro on a Rumba terminal that automated the payment routine on my first job some decades ago. It was truly a hack, for my job was quite apart from coding and neither was I authorized to mess with the mainframe nor my boss knew it. Later on I told him why we got such an extra capacity for the small team and he had my back.
Payments were a problem. Several little invoices from many providers every week and a slow mainframe connection took 3,5 men days/week to be processed, every week, from a team of 3 people. I made some macros for the accountancy codes, several screens and provider's codes and the job was then successfully done in 1h.
It's good for me to remember the importance of front-end needs as well as good basic usability. The very beginning of what is now UX.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
To be honest (and a bit ashamed) it was just a macro on a Rumba terminal that automated the payment routine on my first job some decades ago. It was truly a hack, for my job was quite apart from coding and neither was I authorized to mess with the mainframe nor my boss knew it. Later on I told him why we got such an extra capacity for the small team and he had my back.
Payments were a problem. Several little invoices from many providers every week and a slow mainframe connection took 3,5 men days/week to be processed, every week, from a team of 3 people. I made some macros for the accountancy codes, several screens and provider's codes and the job was then successfully done in 1h.
It's good for me to remember the importance of front-end needs as well as good basic usability. The very beginning of what is now UX.