|
You are here |
codeinthehole.com | ||
| | | | |
di.nmfay.com
|
|
| | | | | analyzing the organization-wide impact of database schema changes, as a service | |
| | | | |
popey.com
|
|
| | | | | This is a bit of a dayjob post, but as I maintain a bunch of snaps in my own time, I figured its not out of place here. Typically when I (or indeed any developer) uses snapcraft to build a snap, a snapcraft.yaml drives the process. Ill integrate some kind of CI or build system, and start publishing to the Snap Store. Usually, once created, the yaml doesnt need much in the way of changes. | |
| | | | |
ricardolopes.net
|
|
| | | | | How using existing processes and tools can massively improve documentation and give you debugging superpowers. | |
| | | | |
gaurav.koley.in
|
|
| | | [AI summary] The article details how to set up a development environment on Windows using WSL 2, including installing WSL 2, Docker, and VS Code with the Remote WSL extension for seamless Linux-based development. | ||