Bartholomew L. Bartholomew
masqueandspectacle.com
masqueandspectacle.com
The ambiguity of it all is what really makes the story sound true to life.
This rewrite differs considerably from the original. Bartholomew is sinister and parasitic in a way that Bartleby was not. Less absurdist Kafka than Orwellian nightmare. Both versions have virtues.
But ...
The grey text on the black background is horrible for those of us with "older eyes". It needs more contrast and/or a heavier font. It's especially bad that, when scrolling, the font's contrast dims even more (making it very difficult to see where I am).
I agree. But I also feel that this battle has been lost a long time ago. So when I read the article in Firefox and hated the background, I just did View -> Page Style -> No Style.
In the same vein, I have min font size 18 and I also have Lucida Grande set as my font, and don't allow pages to choose their own. I also have JavaScript turned off by default.
If I feel I'm missing something on a particular page or site I'll view it in Safari or Chrome. But 99% of the time I don't need to do that.
When these hipster web designers are sixty years old, they will say "WTF was I thinking when I did that???" But until then, it's the arrogance of youth. Absolutely nothing someone older says to them will make any of them care about the accessibility features of their websites.
Clearly the manager was wrong, but so was the employee. The issue here is that the employee is doing everything "right" from their perspective, without understanding the negative impact it has on the rest of the team. I'll spare my theories on how to "resolve" the situation, but suffice it to say, toxic employees can destroy companies; especially startups.
Actually, the story comes across as the kind of 'incomplete, subjective account' I'd hear from both sides in the past, somehow mashed together into one. Maybe that's what makes it interesting?
In this case, we see a supervisor who is still close enough to the code to have the engineer's hat on, but whenever they interact with their own superiors they get the same refrain of "I don't understand this" -- so those people are managers. The problem is that the risk decision of keeping or firing the troublesome team member (as well as other decisions like whether the team's methodology should be agile or not etc.) has been usurped by management.
Normally this decision-making takes a more-concrete form like the 90s-era "And the code absolutely must be written in Java" ... "do you know what Java is?" ... "Yes, it is the software that enterprise businesses like ours use! We must use it!" ... "But this will be faster and more maintainable in another language" ... "Don't care, we need Java", or whatever. In this case I find it interesting that the issue exists one level up in hierarchy, sort of the same problem at a higher abstraction.
Is there any similar sort of stories(both fiction and non fiction). Esp related to dealing with bad hiring, toxic employees and frustrated managers.
Run Forrest, Run!