Today's frustration… I really wish people who are raising and training service dogs from puppyhood really understood that the more work they do with the dog when it is young, the less they will have to do with it when it is older in most cases. But there's always an excuse for why they are allowing behaviors like walking with a tight leash, not stopping at changes in elevation, etc. You are only hurting yourself in the end and making more work. Both of the dogs I raised from puppyhood were walking on a loose leash and stopping at all changes in elevation by the time they were six or seven months old. This made it much easier when it came time to teach the actual concepts of guide work and obstacle avoidance. Same with naming of objects. If you start when they are young and you consistently ask for behaviors, you are going to be much better off and far less frustrated. Also, it is far easier to reinforce these things with a 20 pound puppy than a 90 pound dog.
I'd like to request a favor from #MastodonCanada. Please share and boost our recent announcement of our Proselytizing for Plushtodons campaign and contest. Yes, it's a tongue twister but hopefully memorable. Help us build a community that can have an impact on #SocialMedia and #DigitalSovereignty in Canada.
Everyday this week we will add encouragement and info in an effort to build momentum. But we need more Canadians to join our campaign.
#ProselytizingforPlushtodons
https://elbowsupdigital.ca/news/proselytizing-for-plushtodons/
@deersyrup They really dropped the ball on the <template> tag. The over emphasis on the shadow dom made us miss out on getting something generally useful.
🚨 Emergency DevSec Station Drop
There's an active npm supply chain attack happening right now. Compromised packages are stealing SSH keys, AWS credentials, GitHub tokens, browser passwords, and crypto wallets on install. Then using your publish token to infect every package you maintain.
One command can protect you immediately: npm config set ignore-scripts true
1/2
Fun #JavaScript bug with "default parameters".
`null` values are considered "defined" so they won't be replaced with defaults unlike values set to `undefined`.
```
function example({something='default'}) { return something }
example({}) === 'default'
example({something: undefined}) === 'default'
example({something: null}) === null
```
I developed an AI model that is so dangerous to the plumbing industry that I am not going to be able to release it to the public.
Occult Enby that's making local-first software with peer to peer protocols, mesh networks, and the web.
Yap with me and send me cool links relating to my interests. 👍