

Ouch. My company was just about to start moving over to GitLab off of Atlassian.


Ouch. My company was just about to start moving over to GitLab off of Atlassian.


The truth is; a lot of us feel like we need more internet accounts about as much as we need genital warts.
You are confusing decentralized and fragmented (or self hosted). The promise of fragmented software (like Lemmy) is that there are many instances but an agreed upon protocol. You create one account on one site and then use it to pull and push data to any other site that uses the same communication protocol. Like you and I for example. You created an account on lemmy.zip, I created one on lemmy.world, and we are both discussing a post created by a user on lemmy.nocturnal.garden (an instance I have never heard of).
One of my irritations is that we do not have good language to talk about non-binary people.
For example, instead of a brother or sister, you talk about a “sibling”. It just sounds so impersonal. Instead of saying something that shows your love for a family member while acknowledging the fact that the person does not cleanly fit into either of the gender boxes, it sounds like gender erasure. Like the person is too concerned with social pressure to refer to their relative by an incorrect gender but too proud to use the correct gender. Or maybe it is similar to a gay person talking about his “partner” to leave a little bit of ambiguity about his sexuality.
I am not saying that people should hide their gender identity, just that the English speaking community needs to find better terminology to use when talking about them.
You missed the joke. Obviously, a man is only going to have 0 or (rarely) 1 woman interested in him, but the woman is assuming that he is talking to many women, which is physically impossible.


With prescriptions, it is not about what the customer wants, it is about what brands the insurance wants to cover (and getting a doctor that does not write a brand specific prescription). If an insurance company only covers a weird brand of a common (but expensive) medicine, the customer either has to hunt for a pharmacy that has it in stock, wait for their local pharmacy to order it (in either case delaying when the insurance company has to pay for it), or buy the in-stock brand without any insurance coverage. The insurance can still claim they cover the drug while paying less for it.
At one point, I was on a medicine that had a very high co-pay for the brand name and would not cover the generic. It was so high that it was cheaper for me to buy the generic uninsured instead of paying the co-pay.


The issue is that you went to a fast food store location in a city. I have never gotten edible food at an urban location of a fast food chain, even in the 90’s.


The biggest issue with it was the branding. It should have been called the “Vision Dev Kit”. It was too expensive for most customers and did not have a killer app. They should have only been selling to industry partners or at least only to registered developers.
Then cut the price with the same (or even worse) specs and call that the initial public release.


A Short Hike lives up to its name. It is a sandbox platformer about a kid exploring a mountain to try to find the one place with cellphone reception. The story seems a bit shallow at the start, but the ending is quite touching.
I beat it in one morning, while stuck in an endless conference call. I did not 100% all of the mini games or complete all of the side quests, but I did finish the main story and (I think) I explored the whole mountain.
Job searches benefit from understanding industry specific synonyms and reading between the lines. That should be something a large language model could be good at.
For example, if I am searching for “senior front end web developer”, it may return a listing for “experienced software engineer” because it lists “5-7 years experience with JavaScript”. It could also list adjacent fields the user may want to consider like Project Management or being a Technical Account Manager for the right type of company.
Also, the risk of AI slop is fairly harmless. If done right, the AI should not be hallucinating job listings. At worst, it can show irrelevant listings while hiding good ones, but that is always a risk with search engines. The developers can mitigate this by mixing results from both the AI and conventional search engine and let the user provide feedback if a listing is relevant or not.