This is inspired by A half-hour to learn Rust and Zig in 30 minutes.
Your first Go program as a classical "Hello World" is pretty simple:
First we create a workspace for our project:
$fs=0.2; | |
$fa=0.2; | |
headNum = 2; | |
phillipsDrive(headNum); | |
//phillipsDemo(headNum); | |
module phillipsDemo(num) { | |
difference() { |
This is inspired by A half-hour to learn Rust and Zig in 30 minutes.
Your first Go program as a classical "Hello World" is pretty simple:
First we create a workspace for our project:
blueprint: | |
name: Low battery level detection & notification for all battery sensors | |
description: Regularly test all sensors with 'battery' device-class for crossing | |
a certain battery level threshold and if so execute an action. | |
domain: automation | |
input: | |
threshold: | |
name: Battery warning level threshold | |
description: Battery sensors below threshold are assumed to be low-battery (as | |
well as binary battery sensors with value 'on'). |
#!/usr/bin/bash | |
# Volume notification: Pulseaudio and dunst | |
# inspired by gist.github.com/sebastiencs/5d7227f388d93374cebdf72e783fbd6a | |
icon_path=/usr/share/icons/Adwaita/64x64/status/ | |
notify_id=506 | |
sink_nr=1 # use `pacmd list-sinks` to find out sink_nr |
See how a minor change to your commit message style can make a difference.
Tip
Take a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs
# Credit for this: Nicholas Swift | |
# as found at https://medium.com/@nicholas.w.swift/easy-a-star-pathfinding-7e6689c7f7b2 | |
from warnings import warn | |
import heapq | |
class Node: | |
""" | |
A node class for A* Pathfinding | |
""" |