Please see Raymond Hettinger's keynote on efficiently handling bugs[0]. He makes the case that static type checking is a boon for Python except for in specific programs that make extensive use of covariant and/or contravariant types.
I'm aware that I'm abusing the tool, but I wrote a htmx extension that overrides the mimetype and JSON encodes all the parameters. The JSON is decoded into a data bag on the back end. Basically I can do "fuck it over HTTP"[0] with needing close to zero JS. HTMX has been a god-send to me.
We wouldn't think of doing it. This is the kind of thing your auditors would see from outer space. If you're doing this and you don't have auditors, you're lying on your self-assessment questionnaire. Either way your merchant status is in jeopardy.
It seems to me that the average person around me remembers more than the ancients had the ability to even know. To your point of "pointless essays teach children how to write to an audience", there are entire populations of people who, as a matter of survival, learn how to modulate their communication based on the recipient. Those children learn this skill well before they write any essays about "How X influenced 19th century England".
"For this invention will produce forgetfulness in the minds of those who learn to use it, because they will not practice their memory. Their trust in writing, produced by external characters which are no part of themselves, will discourage the use of their own memory within them."
All my friends who think neoliberalism = "placing one's head in one's ass" call themselves "socialists". You are correct that they're ridiculed, though.
This only convinces me dealerships should be gotten rid of. That's a lot of money sucked out of the car buying process. I'd rather pay less to a manufacturer than pay for a dealer to own a town in PA.
People really seem to miss that complaining about the kind of content on one of the biggest social media platforms on the planet that algorithmically shows you more of what you watch is a huge self-report.
Automated checking of potential bugs in f-strings is hard. There are lots of false positives. You can see some discussion around this kind of rule in pylint [0]. At the end of the day, the choice to run automated linting tools on a repo is up to the maintainers. Autogenerating PRs like this is incredibly noisy and comes off to me as a blatant advertisement for their "code review doctor" product.
Thank you for the clarification. I definitely agree with you. Unfortunately for me, I still dislike using the declarative frameworks that happen to be in JS.
I'm not sure I understand your point here. I would say I "hate writing javascript", but I think the point you're making is I "hate DOM manipulation". These days I use htmx[0] wherever possible. Notably htmx is still javascript; I just don't have to write it. htmx should still count as DOM manipulation and I love it. I just hate all the other methods of DOM manipulation that required me to write javascript. So what is the difference in the distinction you're making?
I'm switching from using docker-compose + docker-sync[0] to using mutagen-compose and am recommending my coworkers across Windows, Intel Mac, and Apple Silicon Mac all do the same. For me mutagen-compose is solving the same performance file mount performance problems I was using docker-sync to solve, but mutagen is doing it much more reliably. I would have to restart the docker-sync (and sometimes the docker daemon) multiple times a day. So far mutagen "just works".
Things like automating manual workflows, building small infrastructure debugging tools, or providing infrastructure consultation to an engineer trying to decouple two parts of a legacy code base.
Very similar experience here. I work on a two person "DevOps" team. Without AWS ECS we would have to have a much higher headcount. I get to spend most of my time solving real problems for the engineers on the product team rather than sysadmin work.
My point was that you can have a conversation with a candidate instead of using arbitrary trivia that is irrelevant to the job and potentially irrelevant to the human you’re interviewing. If you want to find out about someone’s diversity of knowledge, I think “what’s the most esoteric tech you’ve worked with” or “tell me about a project that taught you the most” are vastly superior conversation starters than meta-tag trivia.
If you want to know how curious I am, ask me. If you want to know how disparate my knowledge is, ask me. If you want to know how good I am at guessing from context, ask me. If you're asking about meta-tag trivia, all you're going to find out is if I know meta-tag trivia. I know myself way better than any interviewer possibly can. If you don't trust me to evaluate myself, then you shouldn't be hiring me into a creative, professional, self-directed position.
The only language (other than English) taught in my local school district is Spanish. How do you expect US students to learn a language to emigrate somewhere else?
I also read it as "baked into PinePhone".
As to why, well the headline didn't include the fact that the PinePhone ships with no software. So that's not information I had at the time.