[watwut]

I see chasing weird bugs as part of development job, not something separate. As long as it has weird bugs, the feature is not really done. As a side note, developers who do "only development" and offload all weird bugs to someone else tend to create less maintainable software overtime - they lack feedback and tend to favor whatever makes them produce new stuff faster over what makes us all avoid those weird bugs.

As for infrastructure and first line support, lobbying management for more people continuously is just about the only long term solution.

The other thing is planning and transparency which helps the above. Keep plan with realistic estimates to show it management each time you talk with them. Do your best work, definitely dont slack etc, but dont skip corners to make something look like done when it is not. Instead, move dates in plan and send it to management again. The point is to convince them that there is really more overall work then possible by one person. (If they get offended over that or treat you badly over that, find a new job.)

[Kuraj]

> As a side note, developers who do "only development" and offload all weird bugs to someone else tend to create less maintainable software overtime

My problem is that I have become that someone else.