Lodra

Well I am only able to offer some lame answers. Mostly because quality answers would take a very long time to construct. But here you go

• This really depends on what your building. Maybe find a n established project that's similar to yours and mimick its structure. There are many patterns available.
• Google it, try it, repeat. Python is loaded with "syntactic sugar". That leaves you with lots of options for how to structure and format your code. Which leads to many varying opinions. This is extra noteworthy for larger dev teams because of varying experience levels. You might be able to write a short, clear but of code that some devs won't understand. Lots of good options leads to a lack of clear choices. Opinions will vary.
• Again, lots of options. I like using the Black formatter because it gives you very few options and forces you into some style choices. Even the ones I don't like 🙂
• Oh boy. Google it. Extensively. Google it for several hours and then read some source code. Do this every time you start a new project 😂.
• I don't have a specific tutorial unfortunately. But the idea is that your "pyenv" directory will contain the packages your project depends on. Maybe the python installation too. And every one of these items will be a specific version. Because this is all installed in a single directory for each project, you can easily have different projects use and rely on different versions of the same dependency. This avoids all sorts of problems where you accidentally build and test locally using the wrong package version. I think a common practice is to create the "env" folder in the root of your git repo. And add "env/" to your gut ignore. Don't trust that exact syntax btw 😅

Well I definitely disagree on the extinction bit. That would be bad and should be avoided. Sanctuaries are a good point though. Great alternative!

On a phone, yes it's a bit annoying. Enough for me to read comments for a clockwork link

Apparently, someone else posted the same solution that I did while I typed it out. Sorry for the duplicate but at least weagree on the solution! A warning on this one though. You want to use a feature branch too. Otherwise you'll mix your changes for cool-stuff with new changes for and from even-cooler-stuff. It may become more confusing and difficult to merge.

Create a new branch on your fork. You need it to be synced with the other fork so there are a few extra tricky steps. On your new branch, you need to delete the latest commits that aren't merged yet so that it matches the original repo. Then add a remote for the other fork and pull. Now you can build against the other fork and submit a PR to it.

git checkout -b even-cooler-stuff
# Remove the last 8 commits. Change this number as needed. Increasing it "too high" is just fine 
git reset HEAD~8 --hard
git remote add even-cooler-stuff https://github.com/more-of-url/even-cooler-stuff
git pull even-cooler-stuff

You should now have a branch that matches the other fork. Make your changes, commit, and push normally. When you build the PR, you want to merge into the other fork.

Disclaimer: I wrote this on my phone and from memory. There are probably typos and possibly other mistakes. Good luck!

Apparently I need to try that. Looks tasty!

Is that syrup? What kind of syrup do they use in Japan?

Oh sure, very possibly or even likely. But what's the alternative? As far as I can see, it's either these animals being butchered for profit or basically going extinct. All bad options

Edit: I went back to read the title from the image. The "vegan" label on there is very pointed. Seems derogatory.

I Googled for it quickly and found two hits that look promising

https://marketplace.visualstudio.com/items?itemName=bierner.speech

https://github.com/olefjaerestad/vscode-speech-to-text

I have no idea if these are good quality though as I don't use tts. But hopefully one of them works out!

One of the supplied commands is to commit and push. So it can definitely be made fast and easy. "Automated" may or may not be simple.

One idea comes to my mind pretty quick. If you're not using qwerty or have an unusual layout, keybinds for certain apps turns into a sudden project. It would definitely affect gamers who frequently switch games and rely heavily on default keybinds and standard keyboard layouts. Just switching to a basic qwerty layout for gaming would simplify that quite a lot

Partial profiles management 😎