spit2wind
Joined 4 years ago
Joined 4 years ago
That all sounds nice and logical, but by the same reasoning weren't Epstein's victims getting in and remaining by choice?
I assume you commented as gesture of gratitude. I comment to emphasize the importance of not assuming and as a reminder to project authors to include information, like what their project is and does, in their documentation. Such information should be included per common sense, but alas, it often isn't.
So, same end result (cost exceeds hiring a new engineer), but achieved differently.
The counter, I suppose, is the managers have to deal less with engineers telling them their ideas aren't good or well thought out.
It's always about cheaper, better, faster. And when the thing being built extends beyond a single person, and still when working alone, conflict shows up in balancing the risks between these. The Strawman of Perfection is just that.
"It doesn't need to be perfect" is incredibly dismissive of the reality of the situation. Ignoring reality seems like a poor problem solving strategy.
Obviously that's going to take some figuring out for queries and aliases. But it seems doable to me.
Awkward, yes, but doable. AFAICT, they've provided a way to do things that go against their philosophy should anyone be inclined.
The argument made by the Fossil project, AFAIU, is that it has a better log view than git and has better traceability through SQL based search in addition t the cli and web interface.
What kind of note are you using? There are several and, if I recall correctly, that affects the view a bit. See the "Auxiliary notes attached to check-ins or branches" https://fossil-scm.org/home/doc/trunk/www/wikitheory.wiki
To me, associating a wiki page to a commit makes way more sense than as a commit message that's part of the commit. This way the message can give a summary and then the detail is given in full-fledged markup file that has its own version history.
Totally fair if that's not something that works for you, though.
“We want the bureaucrats to be traumatically affected,” he said. “When they wake up in the morning, we want them to not want to go to work because they are increasingly viewed as the villains. We want their funding to be shut down so that the EPA can’t do all of the rules against our energy industry because they have no bandwidth financially to do so.
We want to put them in trauma.”
That was Russel Vought, head of the Office of Management and Budget and key author or Project 2025.
Trump also said, "a whole civilization will die tonight".
Presumably performance matters above all else (although it likely doesn't in such a place). If Emacs actually makes a meaningful difference, then just use it to do your work more efficiently.
You can run a batch/shell script, right? Of course you can. Would you ask for permission to write and run a script? If not (and presumably you wouldn't because that would be silly) then you shouldn't ask to run Emacs. You "own" both and take on all the "risk". There's really no difference.
But really, truly ask yourself, is whatever cause you're working towards (that is, the mission of the company) worth sacrificing your dignity for?
Tip for learners: find an early edition of a book. They're often vastly cheaper and much better written. It stands that if a book warrants a 12th edition, then the 1st edition must have been decent enough to get wide adoption. Often revisions are bloat or, when they're not, it's educational to see the difference between then and now (eg Andre Tanenbaum's OS books)