Here's the oh-my-posh GH issue[0] in case your problem is similar but not solvable with a simple package update.

[0]: https://github.com/JanDeDobbeleer/oh-my-posh/issues/7029

Alcohol is an _extremely_ harmful drug.

Take, for example, a software engineering opinion that I hold dearly: “Good commit titles and descriptions, with sufficient description of why a change was made and notes on any non-obvious implementation decisions, are valuable and necessary.” This arises from my experiences trying to debug code in repos filled with commits titles ‘wip’ and ‘address feedback’ and ‘changes’ which inexplicably touch 5k LoC. I simply despise trying to divine what some past developer intended without any clue as to why; it is an epistemological impossibility even when sometimes the past developer is me. More over I am convinced this is necessary because I also have the experience of doing all the work to understand some spaghetti—using old issue tickets and git blame to slowly build a mental model of the codebase—finding the bug, changing it, and having the whole system violently reject my fix because what appears to the naive observer to be a bug is, in fact, intended behavior the system depends on.

What would convince me otherwise that spending time on writing good commits is not worth the time and effort? Either an impossible-to-execute-without-confounding-variables longitudinal study that measures developer happiness over time in code bases that do/do not emphasize commit message quality. Or I could have different experiences that lead me to not care. Like if I never had to maintain legacy code or if everywhere I ever worked had issue trackers filled with explicit technical details and motivations then maybe I wouldn’t care; but that’s not my experience so I do care.

I don’t know how you hack your way past the reality that there is not one perfect way to write maintainable software and even if there was nobody actually has time for that. So you have to chose what to prioritize and some of those priorities may become your personal cargo cult.

This assumes worker pipelines are fixed which, practically, they aren't. You can increase flows to the pipeline by increasing outreach or incentivizing attainable qualifications. You can also seek trainees rather than day 1 contributors, which admittedly _is_ "relax[ing] qualification requirements" but has the trade-off of providing more purpose-fit employees when they do start contributing.

https://www.nytimes.com/2022/05/13/business/china-zero-covid...

[0](https://github.com/PyCQA/isort)

[1](https://github.com/PyCQA/autoflake)

Note, I'm not trying to side with either AWS or Elastic here and I fully recognize that both Elastic re-licensing and AWS forking are within each org's rights. I really just think it is funny how beside the point AWS's press release is here.

EDIT: an apostrophe

It is one thing for an individual in the organization to have a nuanced view of the issue and another thing entirely for the organization to have backed off a maximalist view of the right. I encourage you to read the ACLU's position (which interestingly includes "We’ve called on big social media companies to resist calls for censorship.").

The Constitution itself states the role of the Federal government is to prevent mass turmoil and to help the general public. In fact, it lists both of those objectives before it mentions the securing freedoms and liberty; it is generally believed that the preamble is ordered in terms of the priority of its objectives. I understand that there is a very real argument that the Federal government should not be responsible for the well-being of every single citizen but a safety net in times of pandemic is, in my opinion, nowhere close to a Constitutional overreach based on how these objectives have been interpreted.

Comments URL: https://news.ycombinator.com/item?id=21985358

Points: 4

# Comments: 0