14
Where should I start? Absolute newb with a kit
(lemmy.dbzer0.com)
That joke was dangerously cheesy.... +1
My partner and I refer to them as Caws and Gronks respectively based on the usual noise
I always read it as "et-c" to get that pronunciation
Have a look at the Pinout guides, and you should get in the habit of reading datasheets. They usually will have reference designs for the power delivery (pins like vcc, vsys, etc). Also most gpio pins will have multiple functions depending on the use case, and some pins may have more or different features. Sounds like with your particular setup, you'll just need basic digital pins, but if you wanted to add features like RGB backlights or an analog input of some kind like for volume control, you may need to take advantage of either a high speed data pin (for the LEDs) or an ADC pin for the analog sensing.
https://datasheets.raspberrypi.com/pico/Pico-R3-A4-Pinout.pdf
Alright so just go talk to my local brewer supply for what I need ๐๐ผ
Ok so that leaves it up for some artistic license like
- dickcheese
- dickbrain
- dickgobbler
... I could keep going
Home automation using geofencing, and my partner likes to get a notification when I'm heading home from the office
Hello Anxiety, my old friend...
Anyone who uses Oracle DB or virtualbox in a corporate environment
It allows users to run the script on any installation of Python no matter where it's located, as well as allowing a user to set up specific Python package versions separate from the system-native ones.
Basically for flexibility and easy setup
Try a venv or miniconda and use the universal shebang:
#!/usr/bin/env python
Edit: you've activated my brain shrimp, so I'll be back with an interactive setup script in a bit
Edit2:
Sorry I know it's GitHub but codeberg doesn't support gists yet and I can't fully test this by myself. Seems to work fine on Linux mint. I'll do some testing on Windows later
https://gist.github.com/pyr0ball/c6a608fbdd401903f1ff6faf14a065ce
view more: next โบ
pyr0ball
joined 9 months ago
You read the commits before pushing, and test before committing. I also find it helpful to have a reference for any dev tickets you have in your git tracker