I have this same situation where I work. The reason for the gaslighting obviously is that the ahole *wants* me to quit. That is the whole point. So everyone here saying "Quit! Quit!" is just playing into the hopes of the gaslighter. However, finding a job is not so easy anymore, so just giving up because it sucks is not entirely an option. Especially since it tends to happen at every job. (I am a female engineer). What I find works best is just stick to your guns as best you can, diplomatically and logically (What would Spock do?), but since he is in a superior position (lead engineer), I frequently have to 'Disagree but Commit' in the interest of getting things done. If he truly is an ahole - it's not happening only to you. In my case, the ahole has made enemies of all the other teams and departments we interact with. He's a moron who is driving us over a cliff, IMO, but I gotta make a living. I point out the errors in the plans he makes, he pretends he didn't hear or can't understand the reasoning. Eventually I will quit, probably after I hit the two year mark (6 months to go) and then go to another job where another ahole awaits. Or maybe, maybe there is a job with no aholes. I pray for this my entire life, hasn't happened yet. Best of luck.
Agree. The console doesn't show you everything. And the "eventual consistency" aspect bites hard when you check the console one moment and see certain values, come back again, the values are way way up, come back again, they are back down to almost nil. The company seems to have adopted the "eventual consistency" notion as an over-arching theme of how they do everything. I am guessing the problem is that the system is too vast and complex and no one really knows how it all works and tracking down charges is difficult with so many moving parts. There seems to be no way to drill down and account for the charges accurately. It's all very fuzzy and the effect on the user experience is that the logic behind how they charge you is very dodgy and no one can explain it.
If farm workers were paid more, food would cost more, etc in an endless spiral of inflation. The system is inherently broken. We need to think of a new system.
This happens with every presidency, regardless of party. Near the end of their potential term, they cave in to pressures from the military forces within and start deploying the war machine. It makes you wonder what pressures they were put under to discard their ideals.
But I am a middle aged white female software engineer. No one wants an old white lady on their team of 26 year old guys.
This career is like modelling - at some point your brain is considered too old.
It's a nerd meme that has become tired and overdone to the point of becoming a wearisome cliche. It's a positive sign that you have noticed it and called it into question here on slashdot.
As I grew in my abilities and my confidence, though, I was more likely to run into conflicts and differences with some of those same women managers. Communication was less direct than it needed to be, personality differences became more of an issue than they were with male managers, and occasionally, problems would escalate to a passive-aggressive undermining. Conversely, men in management seemed more likely to recognize and acknowledge my increasing competence, and when corrective communication was needed it was short, direct, and efficient.
passive-aggressive undermining... Insightful, you've definitely nailed something there. I'll help you improve as long as you continue to acknowledge me as the leader/wiser one.... don't become smarter than me... I've seen this from both sexes though,... bosses and coworkers, parents.... it almost defines the most basic problem with corporate office culture... primadonnas, managers, kings, queens and other sorts of egos must all be paid tribute to... possibly the defining purpose of the invention of diplomacy...
Yep. Code reviews work best when there is an agreed upon coding standard and maybe even some sort of Czar to weigh in with ultimate authority. There are some people who will waste everyone's time niggling pettily about spacing before and after the parens and such. Code reviews can also bog down indefinitely as different reviewers weigh in with a demand for a complete refactoring that differs fundamentally from another reviewer's outrageous time consuming refactoring request. You are then stuck in the position of trying to please two parties who are engaged in a philosophical power struggle and not being able to. I have seen code languish in limbo this way for weeks because no one had time to sort it out and no one would approve the code review.
Nevertheless despite such occasional abuses, I still believe code reviews are essential.
I was doing well on a phone interview with Google until I casually revealed that CS was my second career (e.g. I'm "old"). The interviewer almost hung up on me right then, and scrambled to end the call quickly. If you happen to go to their campus, you'll be hard pressed to find any bald heads or silver hair anywhere. The vast majority of them are under 30, seriously.
Google is getting in everybody's space, which is ticking off most the industry. Google's products are not generally better, (often flakey or worse (consider google docs and gmail - so what? the only advantage they offer is that they are free (for now) ) ), they just have amazing brand name recognition. The buyers of these products are buying buzz, not quality.
Google is becoming an octopus. Go out and try to set up a lemonade stand, Google will set up a competing stand down the street and give lemonade away for free! Just because they can. It doesn't mean they should. They have already destroyed the search market because only crazy people would start up a search company and go up against them. They are busily destroying most other markets too.
Yes, at my last software engineering job, the architect for my project said with a straight face and total seriousness: "I don't think women should be doing this sort of work. They should be at home making babies." That is a direct quote.
You are a hater here to do some hating - focusing only on negatives. If it's not your problem, why not bugger off? I think you should
I have this same situation where I work. The reason for the gaslighting obviously is that the ahole *wants* me to quit. That is the whole point. So everyone here saying "Quit! Quit!" is just playing into the hopes of the gaslighter. However, finding a job is not so easy anymore, so just giving up because it sucks is not entirely an option. Especially since it tends to happen at every job. (I am a female engineer). What I find works best is just stick to your guns as best you can, diplomatically and logically (What would Spock do?), but since he is in a superior position (lead engineer), I frequently have to 'Disagree but Commit' in the interest of getting things done. If he truly is an ahole - it's not happening only to you. In my case, the ahole has made enemies of all the other teams and departments we interact with. He's a moron who is driving us over a cliff, IMO, but I gotta make a living. I point out the errors in the plans he makes, he pretends he didn't hear or can't understand the reasoning. Eventually I will quit, probably after I hit the two year mark (6 months to go) and then go to another job where another ahole awaits. Or maybe, maybe there is a job with no aholes. I pray for this my entire life, hasn't happened yet. Best of luck.
https://www.youtube.com/watch?...
Don't bite the hand that charges you
Agree. The console doesn't show you everything. And the "eventual consistency" aspect bites hard when you check the console one moment and see certain values, come back again, the values are way way up, come back again, they are back down to almost nil. The company seems to have adopted the "eventual consistency" notion as an over-arching theme of how they do everything. I am guessing the problem is that the system is too vast and complex and no one really knows how it all works and tracking down charges is difficult with so many moving parts. There seems to be no way to drill down and account for the charges accurately. It's all very fuzzy and the effect on the user experience is that the logic behind how they charge you is very dodgy and no one can explain it.
I am so tired of the CEO as Pharoah mentality that has evolved. Let's just stop doing that.
I wonder why there are no mirrors of wikipedia? Seems like someone could just resprout a read only copy without pledge nags?
If farm workers were paid more, food would cost more, etc in an endless spiral of inflation. The system is inherently broken. We need to think of a new system.
lately
This happens with every presidency, regardless of party. Near the end of their potential term, they cave in to pressures from the military forces within and start deploying the war machine. It makes you wonder what pressures they were put under to discard their ideals.
But I am a middle aged white female software engineer. No one wants an old white lady on their team of 26 year old guys. This career is like modelling - at some point your brain is considered too old.
Any job that can be done from home can be outsourced.
Somebody photoshop a top hat, goggles and pocketwatch for the first steampunk insect! http://i.livescience.com/images/i/000/056/820/i02/planthopper-insect-leg-gears.jpg?1379008166
http://www.amazon.com/JL421-Badonkadonk-Land-Cruiser-Tank/dp/B00067F1CE/ref=cm_cr_pr_pb_t
http://flic.kr/p/efUuQR
It's a nerd meme that has become tired and overdone to the point of becoming a wearisome cliche. It's a positive sign that you have noticed it and called it into question here on slashdot.
very weird and fun intro to programming in ruby - heavily illustrated with quirky cartoons
also: http://web.archive.org/web/20090627004409/http://poignantguide.net/ruby/chapter-1.html
As I grew in my abilities and my confidence, though, I was more likely to run into conflicts and differences with some of those same women managers. Communication was less direct than it needed to be, personality differences became more of an issue than they were with male managers, and occasionally, problems would escalate to a passive-aggressive undermining. Conversely, men in management seemed more likely to recognize and acknowledge my increasing competence, and when corrective communication was needed it was short, direct, and efficient.
passive-aggressive undermining ... Insightful, you've definitely nailed something there. I'll help you improve as long as you continue to acknowledge me as the leader/wiser one .... don't become smarter than me... I've seen this from both sexes though, ... bosses and coworkers, parents .... it almost defines the most basic problem with corporate office culture ... primadonnas, managers, kings, queens and other sorts of egos must all be paid tribute to ... possibly the defining purpose of the invention of diplomacy...
Someone with brains AND A VOICE finally speaks up against Slashdot's miserable organization
spoken like a true Goo-guzzler
Yep. Code reviews work best when there is an agreed upon coding standard and maybe even some sort of Czar to weigh in with ultimate authority. There are some people who will waste everyone's time niggling pettily about spacing before and after the parens and such. Code reviews can also bog down indefinitely as different reviewers weigh in with a demand for a complete refactoring that differs fundamentally from another reviewer's outrageous time consuming refactoring request. You are then stuck in the position of trying to please two parties who are engaged in a philosophical power struggle and not being able to. I have seen code languish in limbo this way for weeks because no one had time to sort it out and no one would approve the code review. Nevertheless despite such occasional abuses, I still believe code reviews are essential.
I was doing well on a phone interview with Google until I casually revealed that CS was my second career (e.g. I'm "old"). The interviewer almost hung up on me right then, and scrambled to end the call quickly. If you happen to go to their campus, you'll be hard pressed to find any bald heads or silver hair anywhere. The vast majority of them are under 30, seriously.
there will no doubt be a good number of heads rolling down halls there within a day or so
it fills me with joy. I wonder if other birds will attack it.
Google is getting in everybody's space, which is ticking off most the industry. Google's products are not generally better, (often flakey or worse (consider google docs and gmail - so what? the only advantage they offer is that they are free (for now) ) ), they just have amazing brand name recognition. The buyers of these products are buying buzz, not quality. Google is becoming an octopus. Go out and try to set up a lemonade stand, Google will set up a competing stand down the street and give lemonade away for free! Just because they can. It doesn't mean they should. They have already destroyed the search market because only crazy people would start up a search company and go up against them. They are busily destroying most other markets too.
Yes, at my last software engineering job, the architect for my project said with a straight face and total seriousness: "I don't think women should be doing this sort of work. They should be at home making babies." That is a direct quote.