HN user
My view is that nihilistic tendencies create the feeling of pointlessness in occupation.
A job is a means to an end.
These discussions regarding which jobs are pointless vs meaningful don't do anything to address that people lacking purpose are more likely to call their job pointless.
There is an overwhelming level of nihilism in society. It's even more apparent since most have decided to use their occupation to define their purpose in life.
I don't see how we can continue down this path and see positive results.
Speech is free. Reach isn't.
The problem from my point of view is conflating ongoing healthcare with catastrophic coverage. Outpatient care should absolutely be a free market (prescriptions, lab tests, specialist visits etc.). Catastrophic incidents/diagnoses should be a simple lump sum payout (Cancer, Hear Attack, Stroke, etc.).
Alternative options I've seen being offered for ongoing healthcare is Direct Primary Care where essentially you pay a membership fee to have unlimited access to a primary care physician.
I think the root of the problem is subsidization and the patch work of legislation that gets piled on year after year to "fix" the issue. The entire price function is completely out of wack and as long as the patient is stuck between the provider, insurance carrier, and government debating who has to pay, they will lose.
I agree, I picked up Scala a bit over a year ago and have loved it. I believe there is a happy medium between the functional and OO aspects. Finding this sweet spot is where the language outshines others. Using classes as decomposition components and then using Scala's functional aspects such as immutability and the large offerings of classic functions (map, reduce, fold) give you a powerful and productive language.
I think software architecture is the wrong word for this. It’s module structure, architecture to me includes all the surrounding bits concerning the “ilities”. (Availability, Interoperability, Modifiability, Usability, Testability, Security, Performance). I say this because getting the module structure right is important but not the only factor to a successful application.
My favorites in regard to the topic of module structure are David Parnas and Juval Lowy
Agreed, I joined a consulting company earlier in the year for this exact purpose. I believe technologist have to be more willing to get out of their comfort zone in order to apply their skills to underserved industries. It's a risk and a great outcome isn't guaranteed but they have to be taken at some point.
I had an epiphany the other day. These books offer expansive references to where the author found or sourced their material. Looking through there is a great place to start once the standard books have been completed.