I found the article so wordy and emotional that I could barely read it.
“...so wordy and emotional that I could barely read it...”
Same reaction here. It was too much - I have noticed this is the way most bloggers write: they are so certain of their own specialness and full of themselves that every sentence/word is polluted with ego.
This is why I tend to not read blogs - self important and overwritten is inherent to the genre. It reminds me of a bad actor mugging on stage.
She used the word, “cute” almost as much as another author uses the words, “holy cow”.
I read about 3/4 through and had to skim after that.
The bottom line is that she reminds me of a lot of the queen bees I worked with. Perfectionist to a fault. They try to turn a Yugo factory into a Rolls Royce factory, forgetting the company’s vision and why Yugos are cheaper than a rolls.
That being said, I always went for the highest quality attainable within budget. But the reality of SUCCESSFUL business is that there is always a budget.
Same here.
Sometimes he says wrong things, and then I have to explain why those things are wrong .... Bless his little heart
I read this, and thought, "What an arrogant B*tch.". There's usually a reason why people aren't successful, and she may be looking in the wrong places.
The Author chasing a clue reminds me of a kid chasing butterflies, lots of running around and jumping and grabbing, but nothing to show for it in the end.
Agreed. So saccharine!
I've been in IT for 20 years. IT is brutal. It is logical. It doesn't care that you have feelings. When you sit down to troubleshoot a particularly difficult issue, you start at the bottom of the OSI stack and work your way up; it is plugged in?
Coding, I understand, is a different beast, but you HAVE to fail. I spent months troubleshooting a PowerShell script I wrote that worked for 90% of its intended purpose, but one stupid function wouldn't give me what I needed. It came down to a misspelled variable. I don't make that mistake anymore. I learned from my failure.
Coders seem to fall into one of two categories: "I don't care" or "I care so much." The "I don't care" coders puke out code and turn it in when it compiles and passes regression testing. The "I care so much" coders have a nervous breakdown when they submit their code and start to cry when they're criticized. As much as I despise the "I don't care" coders for their cavalier attitudes, I know I can go back to them to fix something without a maudlin display.
I gave up at the third paragraph. Life is too short to read drivel like this. Get this person some help or just lock her up and forget the help..