- rehevkor5There's no diagnostic test for it. So is it real?
- It seems to be an extension of aspects that he talked about in his speech https://www.war.gov/News/Transcripts/Transcript/Article/4318... Specifically:
> allow me a few words to talk about toxic leaders. > The definition of toxic has been turned upside down, and we're correcting that. That's why today, at my direction we're undertaking a full review of the department's definitions of so-called toxic leadership, bullying and hazing, to empower leaders to enforce standards without fear of retribution or second guessing. > We're talking about words like bullying and hazing and toxic. They've been weaponized and bastardized inside our formations, undercutting commanders and NCOs. No more.
> Third, we are attacking and ending the walking on eggshells and zero defect command culture. > A blemish free record is what peacetime leaders covet the most, which is the worst of all incentives. You, we as senior leaders, need to end the poisonous culture of risk aversion and empower our NCOs at all levels to enforce standards. > I call it the no more walking on eggshells policy. We are liberating commanders and NCOs. We are liberating you. We are overhauling an inspector general process, the IG, that has been weaponized, putting complainers, ideologues and poor performers in the driver's seat.
> No more frivolous complaints. No more anonymous complaints. No more repeat complainants. No more smearing reputations. No more endless waiting. No more legal limbo. No more sidetracking careers. No more walking on eggshells.
> we know mistakes will be made. It's the nature of leadership. But you should not pay for earnest mistakes for your entire career. And that's why today, at my direction, we're making changes to the retention of adverse information on personnel records that will allow leaders with forgivable earnest or minor infractions to not be encumbered by those infractions in perpetuity.
> People make honest mistakes, and our mistakes should not define an entire career. Otherwise, we only try not to make mistakes, and that's not the business we're in. We need risk takers and aggressive leaders and a culture that supports you.
That makes his view of complaints, and his preference that people "take risks" and don't worry about "not being perfect", pretty clear. He thinks those things are "debris" that have been "weaponized" and that he's "liberating" people from. Maybe that seems great if you're in the military. Not so great if you're on the receiving end of those "risks", or if you or your family becomes the broken "eggshells".
- The documentation leaves a lot to be desired. Especially regarding custom node development. But also on the user side, for example the kaka trigger node has zero info on its doc page.
- +1 thought they had caught an image of a Spirit airlines plane...
- It also syncs modifications, so it's not really a backup solution.
- Yeah that confused me at first too. They seem to be treating send() as if it has the same behavior as a setTimeout() call. If you think of it that way, it starts to make sense.
- Their "proper implementation" lacks sufficient error/exception handling around the callback() call. It'll become permanently broken if it throws anything.
- Imperative would be appropriate for things like tutorials and howto pages.
- YouTube really needs to provide an option in their mobile app to disable shorts.
- https://diataxis.fr/ is newer/more fleshed out
- Yeah, DOGE is going to fix the government? Um, wut...
- Calling Redis a database is a generous generalization. For example, Redis does not necessarily provide the same kind of durability as a database does, nor the capabilities one would expect from an RDBMS. In many cases, depending on configuration, it might be more appropriate to instead refer to Redis as a cache, an in-memory database, or a NoSQL database.
- I don't see how it's embedded if it relies on nonlocal services... on the contrary it says specifically, "no local state". It appears to be more analogous to a "lakehouse architecture" implementation (similar to, for example, Apache Iceberg), where your app includes a library that knows how to interact with the data in cloud object storage.
- Their website has a recall notice on it now: https://diamondshruumz.com/
- Relevant: this video with some info about dangers/safety especially related to non-pressure-rated PVC: https://www.youtube.com/watch?v=KqstP9ics2A
- If you want to keep the information secret, you need a way to store it. Assuming number generation must be coordinated centrally (to prevent collisions), that does not seem like an impossible task. A system that involves a cryptographic hash could divide the id space up into different segments without being dectpherable from the outside world unless the cryptography is broken. A periodic key rotation system could reduce the impact of a compromise.
To me, the real question is why embed that information in the passport number at all? Even if driven by cryptography, it seems to represent a risk for which i don't understand the benefit.
- Looking at you, Confluence.
- I'm wondering what happy mediums might exist between the note-taking world, the wiki world, and the collaborative office document world.
Office-oriented tools like Nextcloud or Collabora seem to be oriented to classic Microsoft Word / Google Docs style documents... not as simple as Markdown or as web-friendly as a wiki page.
The note taking tools everyone's talking about don't seem to support collaborative editing. If they're file-based without a server, then you either have to lock the file for editing, or you have to always remember to sync first to avoid conflicts. Syncthing can't really handle that scenario very well.
Also, wikis usually aren't file-based... they require a database. Plus they don't seem to be as lovingly designed as the note-taking tools... they seem to have a very retro MediaWiki style.
Does anyone know of a self-hosted solution that checks all those boxes? File-based (perhaps aided by database driven indexing) with real collaborative editing, more web-oriented than Word-oriented?
- This Speak & Spell simulator: https://sha.nnoncarey.com/
The only one I've found that's as accurate is the emulated version at https://archive.org/details/hh_snspell But mine also has two expansion modules to choose from :)