543 karma · joined December 16, 2014
The #1 rule I try to abide by when coding is "Be empathetic" (to others and my future self.)
In practice, this means things like valuing clarity over cleverness (unless I can manage to be both!) and documenting unless I can really justify not (i.e., is it realistically "self-documenting"), but of course also extends to empathy for the user—I'm a front-end dev so much of my work is UI.
You may read this and think "duh" but trust me when I say that in the 20+ years of doing this professionally, those are very clearly not obvious guidelines (even for myself.)
He's one of the most public figures in the world right now, with hours of video "evidence" widely and easily available. Asking someone to prove he did an obvious thing in public is demanding unpaid labor.
This is not the same as expecting someone to back up a claim of a homeopathic treatment for brain cancer.
So often many will invariably end up letting the place where they predominant publish to dictate what and how they produce whatever it is they output. (I was fighting hard not to say the word "content"...)
Which I despise but also understand: you do what anyone with a job does to keep the money flowing until someone in the relationship decides to end the arrangement.
(Now that I think about it, self-publishing is hardly immune to that. It just means perhaps the creator's motives could be more varied and fluid?)
Are some of these things normal SOP for a regime change? Sure. But to normalize everything under that blanket assumption is just foolish.
Unless you are an exceedingly (liquid) wealthy white male, you are entirely disposable to the incoming administration. You are less than nothing. If anything, you are an inconvenience buried deep in the calculations that needs to be factored out of the equation because your existence hinders the "progress" being sought.
All these pragmatic or, worse, so-called "libertarian" views demonstrate a supremely naïve, if not outright harmful (to yourself and countless others), understanding of what is going to be aggressively pursued these next few years.
Do you think they wouldn't if they had viable options??
This isn't even controversial.
Many simply choose to think it's acceptable, even preferable, through whatever twisted justifications.
I can imagine the 7 people who used Netscape on Linux were very annoyed every so often.
(You do realize we did this before without them, right?)
I'm sorry, but comparing modern Safari to the worst software ever widely used is just not remotely reasonable.
I'm not justifying badly-optimized sites/apps but frankly I don't expect an entry level 4 cylinder gas-powered car to perform the same as a high-end EV.
Second, minimum reqs are/were a thing. I'm not necessarily arguing for or against anything, but at some point... ¯\_(ツ)_/¯
Lastly, people using badly performing devices (not always inherently a hardware issue) are probably accustomed to things not working smoothly. You can only do so much.
Seems a little odd to be surprised when a business that (by the author's own admission in this case) seems to have an established history of customer hostile actions.
If your company is needing to have conversations like this more than rarely—let alone experiencing the actual issue being discussed—then that's a fundamental problem with leadership.
All else being equal, a TV (i.e., TV-sized) unit generally has a broader set of use cases and longer useful lifecycle than a computer monitor for the original purchaser†, which could be argued makes good economical sense.
† in my experience, computer monitors can have a long useful life when factoring in the potentially long tail of "donor/hand-me-down" cases...
Seems like an interesting project and I can see the appeal to markdown aficionados (me among them, although I don't currently have much need to do presentations)!
These are the sort of ideas that, at best, seem like they should be explored with an isolated R&D approach, or simply left to academics.
And, if they are executed realtime with a companies mainline workforce and somehow succeed, it should be clearly stated and understood that it was—like much "success"—by no small amount of sheer luck (or happenstance via uncontrolled factors, if you prefer), force of will, and patience by the team as a whole, rather than the usual narrative which is the inspired actions of single prescient individual (who will then go on to write a book and give TED Talks about an approach that absolutely cannot be applied anywhere else and does not scale.)