168 karma · joined December 28, 2013
Collective bargaining is OK and not usually conflictual outside down cycles or downsizing legacy industries. The conflict narratives appeal far more to general consumers. Working class hero is huge in American history for both good and ill.
Where many unions go bad is running interference on liability, incompetency or even criminality. That is not unique to unions but suffers embarrassing large scale instances (cops? teachers? auto workers who stole tools).
These are tough things to get right. The battles for enough and fair (predictable is a giant issue for service workers) overlap with battles that should never be waged and mostly lose.
Linux has virtues that end up conflicting. An occupational hazard of Linux as a tool and OS innovation platform are disruptions, disappointments, instability and dropped balls.
Other people are goofing off without enduring responsibility for a large user base. We confuse design criteria we inherit from the commercial world. Easy to use, easy to remember, easy to diagnose problems and "quick to getting going" are not the same always compatible design targets. The Window Manager wars took up tons of Linux desktop attention. Gaming is naturally an arena for hardware churn and 1-upmanship.
I have great hope for Linux desktop stability with government deployments and thus a global tug for stability against rushing breaking changes. The Linux platform and package manager contents are remarkable achievements.
Workaday environments suffer impediments to SE application not solvable by tooling. Many large organizations run de jure or de facto Need-to-Know (NtK) departments. I have witnessed Functional or Class Decomposition and Module Hiding repurposed for NtK atomized development teams not knowing shared OUTCOME semantics. Organizations and people turn SE abstraction boundaries into NtK semantic ASYMMETRIES, i.e., SECRECIES.
That does not work well, efficiently, or predictably. Anyone can rightfully detect motivations for both FSF/OSS and Skunkworks structured "startup" teams where all wood is behind the same arrow.
Other problems are lack of SE training. There are big tugs in finite training days between reading/writing skills, problem domain maths, tool churn, machine models, scheduling techniques and so on. Many HN Skunkworks styles teams are in VERY good shape compared to 20 years ago or contemporary organizations trying to turn SE into contract management.
Algorithms are really great foundation for learning anything. I prefer outcome goals driving new learning experiences.
My latest project is optimizing a homemade $10/day food regimen optimized for 1) gut immune health, 2) inflammation and 3) common North American seasonal allergies. I call it OSL - Open Source Longevity for retirees. I recently learned Wholefoods gives away premium fish heads for free around 10AM. I have never eaten better cost accounting for homemade tahini, yogurt and peanut butter.
Couchsurfing And Meetup make in-person local group formation and related discussions possible. DC here is a town where people talk for money, but many communities of Americans are very shy about meeting any strangers.
Masses of people burdened by kids and long commutes or old age mostly seek distraction. Those are yesterday's TV ad audiences ordering more pizza cheese.
I ignore my phone. Some nerdier people have "auditory agoraphobia" and tune in to music, podcasts or books on tape in lieu of chewing cud. I think that is good compared to listening to Howard Stern in a car.
Other people are just remarkably bored. I bothered to spend a few weeks asking people what they were they doing on their phones outside offices. I was surprised to learn how most women I asked were constantly catalog shopping. I was surprised because I use Amazon like preppies used LL Bean to avoid wasting time in retail shopping. Visually obsessed shoppers are problems few will pay engineers to solve.
But why would anyone care? we suffer fools dumping taxpayer dollars into ludicrous athletic programs for lesser colleges and mostly empty new stadium sky boxes for corporate lobbyists.
Passive viewing of sports and entertainment is dull. Attentions and dollars are better devoted to efficient live musical performance. So many of my fellow DC software engineers turned out to be talented instrumental musicians. I presume that early ambidextrous and symbolic training cultivating skilled code slinging applied mathematicians is not coincidental.
My consulting firm did some work in drug discovery. We were already tapped out on brute force discovery by the 1990's. Elective medicine seems indefensible feeding kids synthetic food and leaded water.
Encouraging kids to suffer supersized heroes on drugs beating dogs and women is unwise. My own mathlete kid watches ZERO TV And loves Aikido.
Has demographic crisis, boredom and research attentions wasted on militaries driven good people mad?
I studied Russell, Godel, Tarski and Quine and then compiler and runtime logic (as a Philosophy major). Back then CS was mostly a realm of 3-Page proofs on alpha renaming or newfangled Skip List speed/space utility.
As an old VAX/Sun or 512K/DOS C programmer working in DC for decades around lots of TC, datacenter and transaction processing folks, an SE MUST have basic speed/space, set theoretic, programming by contract, data integrity and MTBF abstractions in their heads while they plan and develop. Both accuracy and performance against test and measure just matter for the business cases 24/7.
Content software developers patching together framework components on 2 day schedules for consumer Web bloatware rarely understand something like data integrity needs of billing system logic embedding in redundant switches failing over on rough schedules. Typing commands is not even Software Engineering.
Software Engineering is not an individual identity phenomenon. SE is how groups show responsibility for stakeholder outcomes unrelated to paychecks. First rule of SE is everyone on the team passes the bus test. Nobody is essential. Unless we seek luck, we can't improve what we don't measure. Learning how and what to measure takes real training and group method application. So many out there never know what they are missing.
Business competition minus lucky windfalls is largely based on COST ACCOUNTING. Successful operations will discover heat dissipation costs challenges. Basic CS speed/space, contract covenant assertions, data integrity and MTBF logic in Software Engineers translates very easily into understanding business innovation problems.