Experimenting with developer tools should not risk destabilizing my Desktop environment or apps. My personal opinion is that the highest velocity way to customize your toolchain is to have a clean bimodal separation between a highly customized environment that evolves quickly (perhaps WSL or a Docker container) running on top of a stable foundation (via Windows or perhaps Ubuntu LTS). However, you shouldn't just clone other folks' automation, as that likely means that you won't understand how things work, so your automation will quickly became a fragile and unmaintainable stack of black boxes. In the spirit of the software craftsmanship movement, I suggest that you build and maintain similar dotfiles for your infrastructure. By all means, take a look and copy anything you might find useful, but this repo is designed and intended for me and me alone. The important thing is that these are MY dotfiles automating MY toolchain based on MY opinions. Some of you might consider this a bit of a contradiction, and that's fine! You can also potentially discover tools you can used to improve your own toolchain.įor example, looking at my dotfiles, you can see I'm a pragmatic polyglot software craftsman with a UNIX mentality and an affinity for Microsoft tools. You can tell a lot about a developer by looking at their dotfiles. Different fighting styles suit different lightsabers just as different toolchains suit different development styles.ĭotfiles are an automation tool used by software craftsman to achieve stabile and repeatable builds of their custom toolchains across one or more machines. Just as Jedi quest across the galaxy, get Khyber crystals and other components, and assemble their weapon, developers experiment with shells, compilers, debuggers, etc., develop opinions, and assemble a custom toolchain. A developer's toolchain is like a lightsaber.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |