One thing that came to me as news is that the command which — which is the de-facto tool
to find the path of an executable — is not POSIX compliant. The recent Debian debacle1
around which brought it to my attention. The POSIX-compliant way of finding an executable
program is command -v, which is usually built into most of the shells.
So, instead of doing this:
which python3.12
Do this:
command -v which python3.12
~~~
Recent posts
- Revisiting interface segregation in Go
- Avoiding collisions in Go context keys
- Organizing Go tests
- Subtest grouping in Go
- Let the domain guide your application structure
- Test state, not interactions
- Early return and goroutine leak
- Lifecycle management in Go tests
- Gateway pattern for external service calls
- Flags for discoverable test config in Go