4 ms·
How is that the job of a programmer and not tech support? And how is this being done by so many people that the average of 5.6 hours makes sense?
by WilliamEdward 8y ago
How is that the job of a programmer and not tech support? And how is this being done by so many people that the average of 5.6 hours makes sense?
- hyperpape 8y agoAt my company, there is an list where problems that can't be handled by tech support or customer facing people get raised. Cases where the documentation is unclear or absent, things that can't be obviously classified as bugs, etc. Making a habit of answering those is a great way to learn about the system you're working on. That said, I don't spend hours on it.
- BeetleB 8y agoTech support? What's that? Most software is written for internal company use. In my last job, the software we wrote was used by hundreds of users in my company. No way is the company going to hire tech support people for internal software. We were very aggressive in ensuring we don't get support questions all the time. We made some of the customers our tech support. Every "domain" of our software had experts amongst our users. So if any user had a question about performing X with our libraries, they were to contact the customer who was an expert in doing X. If he couldn't help, then that expert would contact us. Direct questions to us from new users were just replied to with "Check with the experts first". This helped a lot in cutting down requests. But most companies/orgs, in my experience, will not be supportive of that type of tech support. We had to be very aggressive in it, and we had the backing of our and the users' department heads.