To my great sadness, I have known too many people who I consider to be addicts and abusers of drugs, both illegal and prescription.
Except I've never met anyone with an abusive or addictive relationship to psilocybin. I just haven't seen it. Seriously, when was the last time you heard of a family giving someone a mushroom intervention?
I wrote my company's git wrapper. It was meant to standardize our workflow and to be communal memory for every lesson learned and sharpened edge shaved.
It's now 6000 lines of bash.
(Ok, I'm a little proud of it.
I'll open source it as soon as I rewrite it in Python.)
How do you reconcile this with the fact that the vast majority of git users, both at small and large scales, do not need to do this? Now you have a massive, proprietary to your company, system for committing code that every person that joins the company has to learn and maintain.
That's a good question. My wrapper isn't meant to insulate the users from git, it's meant to teach git. It shows every git command it runs and gives the user an easier on-ramp.
> I'll open source it as soon as I rewrite it in Python.
Realistically speaking, will that happen? Why not throw up the bash code as a separate repository from the python one anyways? As an example. Could throw it into archived mode right after or something perhaps.
I suppose. I'm bitter because I worked at a company where they wanted git used a certain way, which is fine, manage the main repo however you want. The main repo should have some standards and I will follow them. (Preferably this will be automated to for consistency and to keep egos out of the process.)
However, they overstepped and gave me a hard time when they learned I was managing my own local repo how I wanted. I'm relatively good with git and would clean up my pull requests to meet the standards before submitting them to the main repo, but they still hassled me over the naming of my local branches and doing local rebases, etc.
The jury is still out re: the efficacy of Kinzhal missiles. Ukraine reports it's been able to intercept them with old-fashion Patriot anti-missile systems.
I agree with parts of the authors commentary, but I was disappointed that he didn't mention the LCS debacle as one of the reasons American shipbuilding is taking a beating.
This sounds like a good solution to me for the hordes of workers I have known who have set their families up in communities like Livermore or Gilroy, and commute TWO HOURS EACH WAY to the valley. These commuters often end up crashing on friend's sofas during the work week, and return home on weekends.
Really, this low-impact housing solution solves so many problems (traffic, pollution, displacement, sleepy commuters crashing their cars, lost productivity). It's shame it's not being done right (unlock-to-exit makes my teeth grind).
With that said, "take away something that's clean and free and then sell it back to you wrapped in plastic" is pretty much late stage capitalism's primary MO.
The author gave up the game with the bald-faced assertion that "The reason why it was decided to make it voluntary is because all homeless people according to them are victims of capitalism and would not be fair to have any expectations of them."
This is a nonsense straw dog. The author bemoans the lack of "metrics" while neglecting to mention that metrics have shown that Housing First approaches have had a higher success rate than the alternatives.
I think the author's treatment at the hands of activists is deplorable but the arguments in the article don't hold water.
I only have one anecdote. At my previous job, I vividly recall my office mate being bullied and ordered about by a more junior peer. After said peer left, he would breathe a deep sigh and turn to me and say: "Brahmin motherf*cker."
"I'm going to do something terrible." "OMG wow you're the best hon!"