3 ms·
> As a developer I’ve often had trouble figuring out if a job would be Snow Crashy or not, and been seduced by promises of engaging work only to find myself fer
by dahart 9y ago
> As a developer I’ve often had trouble figuring out if a job would be Snow Crashy or not, and been seduced by promises of engaging work only to find myself ferreting out bugs on some enterprise CMS.
Some jobs are more engaging and some are less. In my experience, all dev jobs involve some time spent doing things that I don't consider fun, but the company needs done. Employers do usually sell the work as interesting and engaging for the person with the right skills.
Companies do tend to value the people that willingly take on the ugly stuff and get it done. Sometimes (but not always) those people are paid more. I think there are ways to make it more engaging, by studying the value of the less fun work and working to fix it. This might mean developing interests in and spending time doing some non-coding skills. And certainly there are also some jobs that don't have much to redeem them.
Does anyone have advice for identifying what portion of the work will be engaging during hiring interviews?
- starik36 9y ago> ferreting out bugs on some enterprise CMS. Yikes, that hits close to home. The job was sold to me as helping improve performance of a website with 1 million + daily visitors. Which I took care of in the first month. Now I ferret out bugs on an enterprise CMS.