Have you ever seen the joke of the wheel that's in the shape of a square? This kind of reminds me of that. Then my mind drifts to the whole the circle peg goes in the circle hole and then what you're not supposed to do... is the circle peg doesn't go in the square hole. Wait a second no no no no no no. So at the end of the day, there's nothing new under the sun.

And just started cleaning up their GitHub account…

My brother in Christ TailwindCSS just gives classes that let you do inline styling in a shorter syntax! (and theme configuration, but mostly inline styling) Replace width: ...px with w-..., margin-left: ... with ml-... and margin-right: ... with mr-.... Setting both horizontal margins is mx-... and both vertical margins is my-.... If you can do inline styling, TW just makes the syntax a bit shorter, but that's it, really.

Well they all have their own web service, that's how they can deliver the interface. Of course there are a lot of applications that know they will run aside with others because they complement each other and will set a default port that won't interfere with them, but it can still happen and that's why you can change the port. 8080 (and 8008) are just the official alternative ports for HTTP traffic and thus still often set as default in the configuration of many applications.

Yep! I've tried and it doest work. Either it's because I have mixed unit types (service mount service service and another case is service path service serviceX2), or I really just forgot something. At this point I have to build a simplified version of my services with echo's and shit to be able to debug, because otherwise I'll just drop it and return whenever I find the motivation again. Anti Commercial-AI license

Yeah the poster talking about "coding" is talking a bit of nonsense. "Coding" here is slang for "code blue" which is an American medical euphemism for cardiac arrest or medical emergency. Code blue is partially used to not cause alarm with patients (for example if tanoyed or if people overheard staff) and medical staff are familiar with it because its common in the US system. "Coding" is just a slang that medical staff say to each other and is a quasi medical term; its not an official term and would not be written in peoples notes for example. And it is not an universal term. In the UK we call a cardiac arrest a cardiac arrest and put out an "arrest call". It is unambiguous and doesnt fall into a trap of creating other "codes" that become confusing. Similarly we have Trauma Calls for trauma teams and so on. Some US hospitals apparently use a range of codes like code purple, code white, code gray etc. To my knowledge its not even standardised in the US or often between nearby hospitals (although code blue wouldn't have other meanings). I wouldn't be surprised if some US hospitals also don't use code blue at all anymore because it is unnecessarily ambiguous.

I asked ChatGPT and it says he still needs his glasses while not in costume. So that settles this debate. [image: dccjmg.jpg] /s

Really? You never use the occasional   or something? Edit: my client actually parses the space lol

It was in between the two extremes. It was like four hours a day on average of active hunting/gathering for some members of a group, others spent like 4 hours a day cooking/making clothes/building shelter. They had extended periods where they were sheltered from the weather, celebrating holidays, etc. Hell, most animals only spend a limited number of hours per day actively surviving and have a significant amount of time resting or sheltering from weather. And life expectancy was skewed by infant deaths. Sure, injury and death weren't uncommon in their 30s but that is when humans are at their peak physical condition and most people who survived childhood made it to their 50s even if they had some lifelong injuries.

I think the image assumes that the viewer is familiar with merge sort, which is something you will learn in basically every undegraduate CS program, then never use. To answer your first question, it helps to have something to compare it against. I think the most obvious way of sorting a list would be "insertion sort", where you look through the unsorted list, find the smallest element, put that in the sorted list, then repeat for the second smallest element. If the list has N elements, this requires you to loop through it N times. Since every loop involves looking at N elements, this means you end up taking N * N time to sort the list. With merge sort, the critical observation is that if you have 2 sublists that are sorted you know the smallest element is at the start of one of the two input lists, so you can skip the inner loop where you would search for the smallest element. The means that each layer in merge sort takes only about N operations. However, each layer halves the number of lists, so you only need about log_2(N) layers, so the entire sort can be done in around N * log(N) time. Since NlogN is smaller then N^2, this makes merge sort theoretically better.

I can share my experience with college, which it took me a while to appreciate but eventually I realized that while it wasn't apparent at the time, it did make a difference. But of course, your mileage may wary, it's just my personal experience. I felt like I'm forced to go through a lot of bloat I'll probably never need - why do I have to learn stuff like Prolog, Lisp, Smalltalk and other obscure languages that I'll realistically never need? Why force so much in-depth math, I'll probably never need to be able to formally prove the Big O of a Hashtable... After spending few years working after/during college in offensive cybersecurity, where most of my colleagues did not have a degree, I've eventually realized what was the point of all these classes. I noticed that people kept reffering to programming as in "I'm a python programmer", or "I'm a java programmer", but I never really felt like that - when someone asked me if I can write something in any language, it didn't matter what it is, I can just relatively quickly pick up the syntax and write anything I need in whatever you need, and I eventually realized that that's exactly thanks to the college - the point was not to make me a Smalltalk or Prolog programmer, but to give me a PTSD from every different style of languages, from OOP through functional to whatever Prolog is, and while I do not remember almost anything, I still have the basic understanding of how does that style works, and when I look up any new language I need to use for the job, I've already seen and was forced to once learn and understand (well enough to pass exams) something with similar concepts. And that's a really big advantage that people without degrees don't usually have (at least from my experience with my colleagues). It will teach you how to relatively quickly pick up different technologies and use new things, and that is a really valuable thing. And it's the same about data structures and other math - you will probably not remember it, but the feeling that "wait a minute, this problem sounds familiar, isn't there like a obscure tree-thing structure that solves exactly this efficiently?" or "wasn't there some magic with stacking trig coeficients for this?" will stay with you, and give you a headstart in looking up the concrete details that would be pretty hard to find otherwise. So I'm really glad I went to college. And in addition to that, it was amazing for networking - I had a masters in Gamedev and while that didn't teach me almost anything new, it gave me a lot of friends and an amazing community of passionate people that I keep on making games with.

For some languages gender-neutral pronouns aren't possible or aren't appropriate. It's really only in English and maybe five other languages that gender-neutral pronouns are a real thing and even in these languages if you're not used to using neutral pronouns or reading them in common writing sounds like a mistake to begin with. It's generally just easier to automate the task based on names, and the library itself comes from a time when that wasn't a controversial thought. Lol