Morgenmuffel

RE: https://void.rehab/notes/alwrpupmz2cv2d0k

This actually happened today

@fallenhitokiri@social.screamingatmyscreen.com These documents might as well have been written in assembly.

AGENTS.MD, PROMPTS.MD, and SKILLS.MD are the COBOL of AI age. Voluminous pieces of textual garbage that humans wouldn't read, wouldn't be able to read entirely, and/or cannot read.

I seriously wonder who looks at these markdown files and thinks "WOW!!! So much documentation......this is my wet dream"

I am willing to bet that over 90% of the text is AI generated and not human written.

#LLM #agentic #AI

@fallenhitokiri@social.screamingatmyscreen.com @krinkle@fosstodon.org I have a sneaking suspicion that the engineer was "told" to do this. The engineer is not at fault here, but the organization

@fallenhitokiri@social.screamingatmyscreen.com HA HA HA HA HAAAAAA https://github.com/microsoft/vscode/pull/313931

To quote the inimitable Mr. T I pity the foo, who works for github

@carlton@chaos.social and Inow I wait for the feckless Niall Ferguson to spout faux outrage at calling his overlords pieces of shits. The #LRB review is a stinging rebuke and a good one. https://www.lrb.co.uk/the-paper/v48/n02/iza-ding/studying-is-harmful

IT: Well, we do not have Azure WriteBack to AD so your password that gets set in M365 does not synchronize to AD Me: Build a Self Service Portal and an app to do the sync IT: That would highly insecure and risky. We may fail HIPAA audits Me: What is stopping you from getting Azure Writeback implemented? IT: Budget I hang up immediately to stop the IT person from hearing me scream. This is a security nightmare #security

This is how my conversation goes Me: Why? IT: It is more secure to share passwords over SMS / iMessage instead of teams/slack I AM IN SHOCK and have a minor swelling when I banged my forehead on the table. Seriously Me: That's not my question. My question is why am I not allowed to change my own password. #security

A client I am working with has a fucked up IT policy for changing/setting passwords

A user cannot change their M365 email's password in a self-serve fashion. Instead below are the steps

1. Call the specific IT support person.
2. Do a screen-share and open notepad
3. Type your password in your notepad
4. The IT person then sets the password on M365 and AD
5. If you cannot share your screen because you are on your personal laptop, then you need to send your password by SMS/iMessage

#security

https://deadline.com/2026/03/kash-patel-ufc-fighters-train-fbi-agents-1236750897/
This is not a joke....and I wish it was

#uspolitics #politics #news

There is nothing gentle about sending a "gentle reminder". It is passive aggressive, with threatening undertones like "Next time, my reminder won't be gentle"

A straightforward "Reminder that......" is direct and simple.

#email #etiquette

@mdiluz@mastodon.gamedev.place for folks thinking of considering Matrix, please stay away. It has the most unusable UX, and I have a running list of companies/clients who have moved away from Matrix (Element) back to Teams/Slack/Mattermost. Usability is an issue that Matrix has willfully chosen to ignore under the garb of "Decentralized and secure messaging". Additional reference: https://shkspr.mobi/blog/2025/07/im-never-going-back-to-matrix/

@mdiluz@mastodon.gamedev.place Mattermost has essentially given the OSS community the middle finger. To make matters worse, they have a 10k message team edition (self hosted as well) https://github.com/mattermost/mattermost/issues/34271#issuecomment-3601919951

@davidrevoy Add Grok as the AI model and the bird will spout spicy shit. 😜

@billseitz@toolsforthought.rocks Good choice on the stack. I'm doing something similar, but using FastAPI. I'm not phobic about Javascript, but despise its presence on the server side. The ecosystem (and culture) has caused so much damage to the tech landscape that only Blockchain/CryptoCurrency has beaten.

@billseitz@toolsforthought.rocks do tell......we're waiting. :)

@chrisg@fosstodon.org Neo4J is not nearly as revolutionary in terms of foundation-shaking as people claim it to be. IDMS has existed before Emil Eifrem was born. There is a reason why alternatives have not replaced RDBMS+SQL, it is not for lack of trying from the alternatives. Simplicity, comprehension, and strong fundamentals are reasons why SQL+RDBMS are here to stay and grow.

@chrisg@fosstodon.org You want to look at something that traverses an object model which does not have complicated joins, look no further than SOQL. IMO, this does a good job of balancing SQL familiarity, and object traversal necessity

@chrisg@fosstodon.org Look at Hive. It has query hints to tell the optimizer how to transport data closer to where it is being processed. This is ala Oracle hints.

@chrisg@fosstodon.org I was in the room at a JavaOne conference when Gavin King foaming spittle from his mouth said "SQL is for idiots. Hibernate will make SQL obsolete". I'm hoping he held his breath for that to happen. SQL is not an all-emcompassing solution and has its flaws, which is why there are so many attempts to replace it. But it is disingenuous to say "SQL is going nowhere because it doesn't work for complex cases". The opposite is true. SQL does work for the most complex data model traversals

@chrisg@fosstodon.org Then the NoSQL crowd claims "RDFs are great. Spark solves processing without need for SQL". Then there are translators which run "map-reduce" from SQL. SQL can represent the most complex query patterns in human digestable form (not necessarily simple). Phoenix is built to run SQL on HBase, ElasticQL is an SQL clone, and Cassandra has CQL.

@chrisg@fosstodon.org The reason for SQL's ubiquity has to do with the strengths of its foundations - built on top of relational algebra. Every attempt to get rid of SQL has fallen flat. GraphQL crows that "SQL is for wimps", and when traversing large data sets it croaks. Malloy claims to to solve all of SQL's ills. I'm waiting. If anything, SQL is here to stay for good, and is growing in usage.

@chrisg@fosstodon.org Can we do better? Absolutely yes. Malloy comes to mind in one of the recent forays. I do not understand when you say "I don't see it going anywhere". If anything it is growing. There are more SQL projects in NOSQL databases than SQL databases. History is rife with people crowing "SQL is dead", and then embarrassed with having to do a "mea culpa, here is another SQL-like" project.

@chrisg@fosstodon.org why do you say that "SQL's time is past" ? If anything usage is growing, and even in recent past (pun unintended), new products have been cropping up e.g. SingleStore, and Snowflake to start with.

@fallenhitokiri@social.screamingatmyscreen.com @billseitz@toolsforthought.rocks I've spent enough time agonizing over such seemingly trivial needs that React claims to solve seamlessly. FWIW, Flutter does a better job overall in the *Native space.

@fallenhitokiri@social.screamingatmyscreen.com @billseitz@toolsforthought.rocks Simple.... use Turbo. #sarcasm

@fallenhitokiri@social.screamingatmyscreen.com

1. Databases are for wimps. GraphQL FTW
2. The size of the code is 20 times larger than the size of data
3. And service discovery.