Github says it is C, C++, and Starland.

What is Starland ?

Just clean the floor and give them the mat you would put on the box. This is also a more robust and less wasteful method. They could instead make shelving and that would beore.usefull in a shelter

I couldn't get "designing data intensive applications" to explain to me how to design a graph database (from scratch, without using existing graph frameworks or technologies), but it only suggested reasons why graph databases are useful and the properties I have to keep in mind while designing it. I want to know how I can build one in practice.

Using a prompt like "Tell me how to build a graph database from scratch. Specifically, how to design the data model, implement the data storage layer, and design the query language." only gives a very vague answer. Sometimes it suggests using existing technologies.

Anyone know what I'm missing?

Opinions vary. Certainly many people, not just conservatives would think that sex work is immoral. I don't believe I've ever met someone that believes sex workers are subhuman, that reeks of hyperbole. The perception of sex work as a threat to community is probably wider spread still, in its current form it certainly isn't conducive to safety for anyone involved.

Overall, you're simply setting up a strawman that poorly characterizes your opponents. There are many reasons why someone would oppose sex work, including concern over the safety of the sex workers. Even if it were fully legalized and regulated there would still be significant risk when you have two people who don't know each other well in a room alone together and questions of sex and money are money are involved. Especially if it is a physically stronger man with a woman. The more cogent arguments take that into consideration along with the other effects such as sex workers becoming trapped in the occupation, the poor prospects for aging workers to earn an income or be able to retire, the second order effects on the community which are poorly understood but could be far reaching, economic effects of making the occupation more available to the working age population who might otherwise pursue other careers, etc. All of that generally lines up with the conservative take on any change which is to ask "Are you sure you have considered all of the consequences?" and "Do the benefits outweigh the costs both short term and long term?".

On a side note, I forgot to mention that my inspiration for starting to write my own was reading the 1980's journals of Jordan Mechner, the creator of Prince of Persia. Still to this day if feels like there's something magic about them.

I was a sceptic, when I first saw 'blameless' post mortem used. Our sister group wiped out our production database and put together a lovely GIT issues template on how this was mostly not their fault. Great...

However... this has become one of the most powerful changes in our extended group's engineering culture. The focus on what happened and how, rather than the who. Each time, it is a chance to examine how things went kittywampus and how we can break that chain in the future. For the most part, I don't even think we include the names of the people involved. The process grew on me, the more we used it. Folks would fess up, rather than hide it and creating a snipe hunt for root cause. We were able to categorize where our pain point were and what we could do to stop it - and it worked. It really made the folks who could analyze what happened and how we could do better with what we have, shine.