-
Asked by ChewyLewy0128 to Ollie, Iulia, Katie, Mateusz, Siobhan on 12 Mar 2017. This question was also asked by Mia.
-
Ollie Morris answered on 12 Mar 2017:
oooh good question.
I would say probably about 20% if not less. Normally we try not to have problems.
A lot of my working day is spent keeping equipment clean maintained and making sure we have enough spare parts in case something goes wrong.
-
-
anon answered on 13 Mar 2017:
This really depends on the day and the current project.
Back when I helped architecture students with their exhibition – most of the day was spent debugging and looking for workarounds – not everything worked as good as we expected.
My next project with re-programming will probably have me spend most of my day looking to solve technical and software problems as well (especially since new robots often have problems even when you do everything right – they themselves are just not developed properly).
For now, though, it’s less about solving tech problems and more about seeing how people think the tech should work in the first place.
-
Iulia Motoc answered on 13 Mar 2017:
It actually depends. As you advance in your project, you will spend less and less time to solve technical problems. Not because you will not have any problems, but because you will be more familiar with the project and you will be able to fix the problems faster.
I don’t think the time you spend on fixing problems can actually be measured, as this depends on the type of problem as well, and you have to consider the fact that you will not have problems every day.
At the moment, if I do experience a technical problem, I would say it takes me maximum 10% of my day (assuming that I work 8 hours a day) to fix it. But, for example, when I was in my first few month of PhD, I spent a whole night in the lab, trying to fix a problem.
Comments