2,137 karma · joined September 11, 2016
One of the root causes of these failures is viewing the actual software development as a mere afterthought once all the high level boxes are drawn and power point slides created. Tremendous resources are spent on everything ancillary to the software and insuring proper adherence to process is kept no matter how orthogonal that process may be to maximizing the delivery of quality software in a timely manner. It’s really quite amazing.
https://www.foxnews.com/media/biden-admin-accused-intimidati...
There is no line that's weird. What's weird is expecting there to be a line like %50.7% female or %14.2 black.
> (I’m assuming you’re male) how many times have you had to disengage from a professional group conversation because one person is just constantly hitting on you? Ask your women coworkers how often this happens.
If this is happening at work it sounds like an unprofessional work environment in which case you have recourse. If the problem persists after making the unprofessional behavior known to leadership then there's probably systemic issues with that organization that go beyond just sexual harassment. As an aside, I've had to disengage from professional group conversations a number of times because of my political and religious beliefs, which also should not be a problem at work.
> Everyone is different and should be judged as such, but I’ve been in community events where this sort of behavior isn’t rampant and it’s a million times better. And yeah, turns out that having a more representative organizational community does wonders for that.
This sounds like you choosing how to spend your free time and if you think the "quality" of an event is effected by how many different skin colors and the percentage of gender participate, great. It also sounds like nothing is stopping you from doing that so I don't see an issue here.
The early straw man was that downloading apps was too daunting a task for users and yet some how they managed to download and update email clients, word processors, iTunes and ironically browsers themselves.
Since I began my career in 1995 I’ve seen application architecture pundits proclaim the correct way to develop applications go from thick client native to thin client native to thin client web to thick client web back to thick client native (iOS & Android) and now, according to the article back to thin client web. I’ll submit the best model is thick client native using the “web” as a communication backbone for networked features.