Software Engineers aim to make things more efficient. They are all about innovation. You want and you need a lazy engineer, someone who does not want to do repetitive tasks – her or his mantra should be: “this is time-consuming and boring, will make it slick and fast”. Most folks would not even bother, they would accept the fate and would continue to do the same thing over and over… Yet, software engineers keep cutting corners and making things easier… Anyhow, a good software engineer is needs to be lazy by default, that trait drives innovation…
7 replies (most recent on top)
Doesn't imply that lazy SW engineers are always good, though...they usually end up managing programs instead. " Hey write up that status and send it to me"
Daily status updates are the headache of Q. Daily 'scrums' are a huge symptom of major mismanagement and utter chaos. I see so much covering a-- going on. More covering and ducking than actual work oftentimes.
Qcom then must have the worst SW engineers. When I was there, there'd be so many repetitive tasks. People took pride in having repetitive tasks as it made them seem important. You had QUIC proxies that'd just propagate things all day. There was so much brain dead button clicking involved in that, and there was no interest in automating it. Of course, you had to write a status report in a templated Word file which was rolled all the way it seemed up to the CEO level.
Daily status updates? Wow. That bad, huh?
I have to run around and collect status from a bunch of folks everyday. The lazy ones are the worst. Why can't they just do the job, report status? It's not rocket science.
Because they work for Qualcomm?
Sherlock, hmmm