I started using git-secret 2 years ago. It’s nice for making secrets part of the repo, while not being readable by anyone that isn’t explicitely allowed to do so (using GPG).
I started using git-secret 2 years ago. It’s nice for making secrets part of the repo, while not being readable by anyone that isn’t explicitely allowed to do so (using GPG).
Coincidentally, I happen to have been reading into SEO more in depth this week. Specifically official SEO docs by google:
https://developers.google.com/search/docs/fundamentals/seo-starter-guide
To be clear, SEO isn’t about tricking search engines per se. First and foremost it’s about optimizing a given website so that the crawling and indexing of the website’s content is working well.
It’s just that various websites have tried various “tricks” over time to mislead the crawling, indexing and ultimately the search engine ranking, just so their website comes up higher and more often than it should based on its content’s quality and relevancy.
Tricks like:
Those docs linked above (that link is just part of much more docs) even mention many of those “tricks” and explicitely advise against them, as it will cause websites to be penalized in their ranking.
Well, at least that’s what the docs say. In the end it’s an “arms race” between search engines and trickery using websites.
Depends on the specific plugin. I’ve been doing music production on Linux for several years now. Back then things looked a lot worse than now. Most popular bridge solution for Windows plugins on Linux is yabridge atm. The README is well worth a closer read, cause it will answer many questions on how to get even more modern plugins to display correctly (i.e. JUCE based ones).
Have you ever learned about the following in VIM:
H
,M
,L
,22H
, …,: vertical cursor placementzt
,z0
,zb
: vertical scroll positioning0
,$
,gm
,gM
: horizontal cursor placementw
,e
,b
: word based cursor movementSimply holding
j
ork
at times also works, even more so with a decently high key repeat rate.Of course there’s a lot more: https://vimhelp.org/motion.txt.html
The trick is to only learn a couple new movement mappings at a time and use them during one’s workflow for a while, up until they feel ingrained. Then repeat, iteratively building up one’s movement skills in VIM.
One can say many things about VIM, but not that learning it’s movement mappings will make your required APM (let alone mouse clicks) go up to “get stuff done”. Honestly, once a basic set of these movements has been learned, any other editor without them will feel like a drag.