361–368 of 368 posts
Earlier quoted context omitted.
Wow, I did the exact same thing, for exactly the same reason. My dad called me a few hours later and said, "I finished the 38000 word article you sent.". I checked and he wasn't far off; it's around 29000 words.
The certificate of participation at the end claims it's 38,000 words...
Earlier quoted context omitted.
> There was a thread a while back where software developers told me I was unreasonable to expect them to know who the vice president of the country they lived in was. It is absolutely unreasonable. The average person has no clue who the vice president happens to be ... so why should software developers? We can complain about how clueless average people are, sure, but there's no reason to apply a higher standard to so…
Wait, what? The average person doesn't know who the vice president of their own country is? I'm Canadian and I still know who the US vice president is. Surely most American adults do too.
One thing I noticed though is that the author is definitely stuck in the old "Microsoft is the great Satan" mindset. If he ever finds out about all the open-source stuff MS is doing these days under Satya Nadella, I think his head would probably explode.
He doesn't know what to say to a C# developer (nothing in common), but automatically trusts a Python developer? Really? sigh
Earlier quoted context omitted.
What? I imagine there are many, many auto manufacturing VP's who think, "I don't know anything about engines and drivetrains and all that technical stuff [– and I don't need to]." Why should the VP of Human Resources need to know how a drivetrain works? Or the CTO? Or the CFO? They are experts in their area focus. It's ridiculous to expect every manager to understand everything about their business. Would you expect…
"When meeting with the VP, TMitTB should talk about the business impact of options." I don't think he even knows what the business impacts are. TMitTB is just a tech guy who works for the new CTO. Presumably, the CTO (being an executive in charge of technology) can speak both the language of tech and the language of business and could make a business case to the VP, in terms he understands, as to why the company need…
Yet at the end of all this, "TMitTB will get his bonus."
WHAT!?
What's the message here? Big companies are hard and inefficient places? Programmers and techies are confusing and dress funny?
Other than being technically illiterate, the VP seems to be the hero of this story. Not recognized as such, of course ("Money? Hours? Due date? Value? Bah!").
The CTO ("who has several projects on roughly the same footing [e.g., horribly mismanged] scattered across the organization") and TMitTB should have been fired long before the 30,000 words came to a close.