[luckyandroid]

There's a balance needed with smaller companies. I, for a long time, chose not to care about the company's goals and just hit the daily tasks, and for a while it worked and I did very well. But eventually the management had a build up of stress, realising that THEIR choices of assigned tasks were not taking us properly to the goals, and let out the stress on the development team to a point where a few of us quit.

This isn't an objection to "not caring about employer's goals", far from it, it's clearly an issue with management teething problems as they try to expand a relatively small company and don't know how to do it. But I've found that caring a little bit about the goals, trying to see what they're aiming for and having that inside view of why we aren't getting there, allows me to bridge that gap, offer better advice to management and help the entire team have a less stress filled day, at the expense of some of my own peace of mind.

It'd be easy for me to say "well that's managements issue" but I can't ignore that management issues trickle down to the rest of us, which is much more obvious in smaller companies.

[luckyandroid]

Oh, and a mention on 'saying no' - it's very hard to convince an employer to start saying no to customer demands even when they agree with all the reasons set out in front of them, especially when they've had a decade of doing nothing but bespoke work for them. It's taken a year but we're finally at the point we can firmly stand our ground as a dev team and say "no we're not working on that", or "push to Q4", and ignore the "we need this done TODAY" type of demands that have plagued us for years.