From what I recall, particularly the younger generations that exclusively use mobile devices (though of course this is not limited to them) actually have terrible tech literacy across the board, primarily related to spending all of their time in apps that basically spoon-feed functionality in a closed ecosystem. In particular, these groups are particularly vulnerable to very basic scams and phishing attacks.
Common Lisp isn't a functional programming language. Guile being based on Scheme is closer, but I'd still argue that opting into OOP is diverging from the essence of FP.
Gross. Yeah, no. You should definitely be asking for consent if nothing explicit has been said. I've done it many times and it was always appreciated (including by my now wife on our second date when I asked her if I could kiss her), but more importantly, it was the right thing to do. If for some reason there's a person that is put off by asking, that's kind of a red flag to be honest. Good communication in relationships and sex is essential and the foundation of any healthy relationship.
There are many ways of asking, too. It doesn't have to be some stitled "Would you like to have sex with me right now?" Also just generally communicating a lot before and during sex acts as consent and helps to build trust.
A lot of women have had truly awful experiences with men. Good communication and obtaining consent is not only treating women with the kindness and respect they deserve, but it also makes you stand out among the many men with poor social skills that make unwanted advances all the time.
Never understood why people keep trying to use proprietary tools for this, especially when curl is so good.
I have a directory of shell scripts I use to test out endpoints. I persist request/response data either with environment variables or regular files. Oh and since these are just shell scripts, it's pretty trivial to do stuff like iterate over a CSV (or JSON array) and make a request for each row, conditionally make requests, or whatever else you want.
Oh and honorable mention goes to jo and jq for making it super easy to make/process JSON data.
Yeah that's what I was referring to by "archaic". Pretty much anything using the LAMP stack falls in that category. I don't generally see new things using it.
To answer your question about MySQL: in my experience it's rarely used outside of classrooms or archaic systems. Postgres is a much better general-purpose option for SQL. Sqlite is also nice for different use cases (such as a database on a mobile device).
I dunno, at my last job with unlimited PTO I took as much as I wanted. Obviously you want to make sure things can run without you, but that's manageable.
Unless you work someplace truly shitty that has unlimited PTO in name only, I think it's by and large how you approach it. Most people do themselves dirty with it for no real reason. For me, I generally just took time off for planned vacations and a couple other things, typically taking off 4-6 weeks a year, which worked for me and I found pretty reasonable. Was absolutely never an issue.
My current job accrues 18 days paid off over the year (increasing with time on the job to 24 or something like that), and it's mostly fine though honestly if I've used it all and I end up needing more time off, I'm probably just gonna take it off anyway. I'm still not 100% sure if it's gonna be enough since I'm taking a week off next week to pack up my house to move.
I used to work for a company that made software built on VMware. The biggest customer was using hundreds of thousands of VMs. Pretty sure they're working on moving off VMware now because of all this bullshit.
But yeah, it's gonna take a long time to move off.
If you mean for programming specifically, I... don't, really. At most it would be for a quick sanity check on syntax in a language I don't write often, for which Google is fine. But otherwise I rely on documentation and search features of the various language/tool-specific websites.
The issues are primarily with Azure, I believe.