Being able to question the judgement of an authority figure / decision maker is a privilege. A squeaky wheel gets the grease but a raised nail gets the hammer. Engineers generally lean more nail than wheel in most orgs, and being a minority or otherwise less respected subset of that group makes you feel even more like a nail.
Dotting I's and crossing T's is exactly the kind of behavior one would expect from a person who is smart enough to recognize something is a stupid idea, knows that they lack the authority to make any changes, and will bear the bunt of the inevitable failure.
You're right about this. Indian work culture tends toward rigid hierarchical structures, and expects employees to be much more deferent to authority than you would find in a typical Silicon Valley startup. However, even after bringing our startup culture out there (unlimited PTO, stock options, choose your own hours, don't call me "sir"), I still find this test-taking mentality to be what dominates an engineer's decision making.
Because of this, I know to be extremely specific on exact deliverables and tickets. The "rockstar developer" who can think deeply about the end user's needs is an extremely rare thing to find out there. The dominant mentality among developers is to expect a detailed specification that can be treated as the exact boundary of the problem.
To give a concrete example - I recently got quite frustrated when a simple CRUD feature shipped without a delete button, since the specification failed to explicitly mention where the button should go. Out of 30 developers and a full QA team, not one person thought critically about the specification or tried using the app from a user's perspective.
I come from a manufacturing background and have moved into software. In manufacturing, if there actually are issues with the specification, you raise those through engineering change notices. If you start changing the spec on your own, that’s a big time no.
Do you have a formal process for spec changes or are you expecting the team to raise these issues independently and unprompted?
If someone has actually raised concerns with you about the spec or offered up changes, how did you respond to those? I work with people who always say, “why doesn’t anyone challenge me on my ideas?” This happens at the end of a meeting where these people will have shot down everyone else and their ideas. In reality they want “yes people” who tell them there is no disagreement because their idea is best.
I’m not saying this is you, but they may have been through these experiences and might need permission or direct instruction to show them speaking up is valued.
Maybe? But it makes them useless for my purposes. Which requires them to think for themselves.
What I think you mean to is you want a person who will take action. And that's down to company culture. If you want employees who act empowered, you have to give them power.
Now if someone could only help me locate that speech.
When you complete a course there's an exam, and labs and assignments typically have a set of instructions to get started and a list of requirements.
And there is always a domain expert (TA) not far. Now they are learning to become the domain expert in their own (limited) area.
No student enters IIT declaring a CS major like an American university - they have to first excel at test-taking within IIT across a range of subjects (chemistry, physics, etc), so they can be part of the top cohort within IIT that is allowed to enroll in CS classes. Based on a couple Youtube video lectures I watched, these courses tend to be lecture-based and tested based on printing the correct output (not on software architecture or code quality).
Some of our younger IIT developers say the system is modernizing to be more like other higher education programs, so I might be totally wrong here.
Which is of course nonsense. The same test-based education system also produced leaders such as the CEO of Google, CEO of IBM and the CEO of Albertsons. If you have been able to hire some to close "JIRA tickets" you scraped the bottom of the barrel and maybe you shouldn't be making generalized conclusions based on your observations!
[1] https://www.atlassian.com/software/jira/service-management/t...
I don't mean to say that IIT graduates lack creativity - there are many well-known examples to the contrary. My point is that an academic system where success is predicated on test-taking ability will produce great test-takers who function quite well as cogs in the machine. The system does not cultivate enough creative thinkers who can imagine the machines that have not yet been built.