Hacker News Reader

Agree, with DBA or system administration it's possible. Not so with UI/frontend development, for some reason that's always a rush.

I would probably differentiate by work visibility: good work in DBA/sysadmin/security/accounting/quality is invisible, you only notice those folks when they have screwed up.

With product/UX/new features it's the other way around, coasting is not possible.

View on HN

> With product/UX/new features it's the other way around, coasting is not possible.

That very much depends on the application. I maintain some enterprise solutions for customers. Clients get upset if UI has flow changes. Also, changes don't make me money unless they are required for a new customer. I will do it on request and invoice for the work but no one is interested in change for the most part. I think this is VERY common in enterprise software.

Reply on news.ycombinator.com