In a perfect world you could get paid to automate stuff with AHK. I wonder if you could market yourself as an AHK consultant where you basically shadow someone’s job for a week and then start figuring out how to automate the tedious stuff.
Personally I like the functionality of AHK but I can’t stand the syntax compared to Python and C. I start with such great plans of what I want to automate but get sick of fighting with the language after about an hour and settle for something simple.
And you can continue typing it that way for as long as you want if you set up autohotkey to automatically fix your typos.
It’s basically like you check out the destination branch and cherry pick your changes on top of it.
I don’t know if there is a functional difference between a merge and a rebase assuming your git history is reasonable, but rebasing makes the history so much easier to follow. Every commit only has a single ancestor, commits are generally better structured because devs where I work tend to squash and rebase.
The obvious solution is to use Rust’s upcoming “spaghetti checker” feature. Once the compiler decides that your code is too messy to be maintainable, it refuses to compile.
I remember Zune did not play well with Linux at all. One time I plugged my Zune into a Linux laptop just hoping to charge it. From that point on, until I plugged it back into a Windows PC, the Zune would play one song then skip the next two. As in track 1, 4, 7, then roll over to 2, 5, 8, etc.
That was the only problem I had with my Zune though, RIP Zune, you were the best.
Oh wait except for the leap year glitch. Microsoft apparently didn’t think people would still use Zune in 2008 so all the Zunes stopped working for the duration of the leap day lol.
If someone else has to debug the problems caused by a parent naming their child with a special character, does that make the parent the bugger? 🤔
To be fair they tried posting it on the Linux community on .ml and there were so many upvotes and positive feedback that it crashed the server. So they had to post it again somewhere more balanced to limit the impact.