It's sad that some Indians leaders and followers ignore these achievement and just try to claim they had hi-tech internet
in ancient days .https://www.theatlantic.com/technology/archive/2018/04/india...
598 karma · joined November 20, 2013
1. It only uses a narrow column for content. 2. No code highlighting or snippets embedding support
On a serious note 400 USD us probably good enough for a fresher (to be honest its way more than average) but its quite less for a mid-level engineer.
But unfortunately in this case above scripted behaviour is being shown by middle management (Engineering manager with not much coding background ). This is because they are mostly under fire if there is a "Spill Over" . The engineer playing scrum master role can easily get away with it because the probably did their part in the coding front and just threaten to step down from the role. But managers don't add much to anything else in the delivery process, so they are forced to be accountable for everything. (C'mmon we all know appraisals are also pretty much scripted) .
Every other day our local newspapers mention the word "techy" to describe someone work in IT, he could be a product manager or an operations manager in facilities, just because he is in Silicon Valley of India.
The agile example is great. We enforced something which works for assembly line where things are repetitive and we know how much time it takes exactly to assemble two parts of a car. Software Development is could not be more different than this. We want iterative development yet we need to have fixed deadline.
We don't trust the developer, we hire a scrum master who in most cases just moves stories in Jira if a developer forgets to do it religiously. In that process, we (read middle management ) are happy to have stories in "done" section but have a problem with "in progress" section tough later is likely to have higher quality. Because earlier one looks good on paper.
I have seen when scrum master/co-ordinators / middle managers when getting a tech-related question from other teams or execs, they loop the engineers saying "rookie question".Really just say "I don't know anything about engineering that my team does"
Also the "IC track" for engineers? Seriously if someone works in teams that is engineering teams. Why should they be called "Individual contributor"?
IMHO, if engineers were little more disciplined we did not need middle managers or these dedicated agile coaches, scrum masters who neither has any tech skill nor has any vision, unlike the leadership / executives.
The worst part is that when we did post morterm and asked Google why the support resolution was so slow despite being "the privileged" customer, their answer was that the P1 SLA was only to respond within 15 minutes there is no SLA for resolution. Most of the "response" that were getting was that a new support guy has taken over in a new time zone which is the most useless information for us.
We are seriously thinking of moving to another cloud vendor.