I think calling this "lazy" is cute and has its history, but really it's about not wanting to do manual work, like copy/pasting, or manual testing etc., where you could instead automate it.
That said, it would be nice if this really was widespread, because it seems to me organizations and leaders of orgs, put so much value on appearance. People want to hear the good news, and forget that in fact, the status is just a reflection of where things are at and not predictions of where things will be. Optimizing for appearance and sounding nice, in my experience, takes away from this "lazy" mentality, and creates process-driven programmers that take days to add a simple feature like a button.
Agree. I have worked with large consulting companies that had big banks or big telco as clients and it has been an awful experience.
Not only there is a appearance culture, but also a lot of politics is involved. It's like you are not trying to do your best for you clients, but mainly trying to take the biggest share for you. I know that companies must be profitable, but there should be some sort of Ethics behind.
Once, a few years ago, I told to one of the top managers in a company I've worked with that the requirements were wrong because it was clear that the client wanted something different; he replied me that it was even better, since this way the customer would have payed us to do the job and payed us again to fix it. I felt a terrible way of behaving. That day I started looking for another job.
Then I was lucky enough to land in a place where the culture is the complete opposite (to the point that they literally write in they job description that they look for "lazy javascript developers"), and I felt happy again. BTW, they are still searching for some, so if anyone is lazy enough and wants an introduction, just drop me a message at <dave> <at> <saasform.dev> and I'll be happy to help :-).
2 comments
[ 3.1 ms ] story [ 18.1 ms ] threadThat said, it would be nice if this really was widespread, because it seems to me organizations and leaders of orgs, put so much value on appearance. People want to hear the good news, and forget that in fact, the status is just a reflection of where things are at and not predictions of where things will be. Optimizing for appearance and sounding nice, in my experience, takes away from this "lazy" mentality, and creates process-driven programmers that take days to add a simple feature like a button.
Not only there is a appearance culture, but also a lot of politics is involved. It's like you are not trying to do your best for you clients, but mainly trying to take the biggest share for you. I know that companies must be profitable, but there should be some sort of Ethics behind.
Once, a few years ago, I told to one of the top managers in a company I've worked with that the requirements were wrong because it was clear that the client wanted something different; he replied me that it was even better, since this way the customer would have payed us to do the job and payed us again to fix it. I felt a terrible way of behaving. That day I started looking for another job.
Then I was lucky enough to land in a place where the culture is the complete opposite (to the point that they literally write in they job description that they look for "lazy javascript developers"), and I felt happy again. BTW, they are still searching for some, so if anyone is lazy enough and wants an introduction, just drop me a message at <dave> <at> <saasform.dev> and I'll be happy to help :-).