- #DOTBOT FISHERMAN HOW TO#
- #DOTBOT FISHERMAN INSTALL#
- #DOTBOT FISHERMAN DRIVERS#
- #DOTBOT FISHERMAN SOFTWARE#
This is why I always search "How to X using PowerShell" to get smarter non-fragile solutions.
#DOTBOT FISHERMAN HOW TO#
How-to tutorials can be quite out-of-date, as the sorts of Windows admins that google how to do things are the sort that need Wizards, and Microsoft seems to change these super frequently.
Obviously, there are rough spots in Windows. mother-flipping Hackintosh kernel extensions) to try to run an operating system that your computer wasn't designed and tested for.
#DOTBOT FISHERMAN DRIVERS#
You don't need to download hacked together drivers (or worse. You don't need to stress about resolution and aspect ratios when plugging into projectors. You aren't forced to buy devices with touchbars or keyboards you don't like. You can slap together beastly gaming rigs using parts of your choice, and things generally just work. You can get Mac-like ultrabooks from a ton of manufacturers. I like Windows because it's an open ecosystem with a huge variety of devices, strong drivers, and support for games. Why a Unix Hacker might want to use Windows However, I expect that WSL's net GPU passthrough feature may eliminate this use case. The most recent thing I've has to use this for was neural network stuff that required CUDA and direct access to the GPU. One of those systems happens to be a native Debian "escape hatch" on a separate partition just in case I have to do something that seems to require native Linux.
#DOTBOT FISHERMAN INSTALL#
While I generally use this repo to quickly standup my dev stack using Windows and a Debian-based WSL distro, it's organized so I can also install my tools on a native Debian-based system (typically a beefy remote dev server). Tooling for a wide variety of development stacks.VSCode as the main code editor, using the WSL Remote extension.WSL2 and Ubuntu 20 LTS as my dev environment.winget for native Windows package management.Here is what my toolchain currently looks like:
#DOTBOT FISHERMAN SOFTWARE#
Additionally, I don't view having a highly customized operating system as pragmatic or time-efficient, which is where I differ from the many software craftsmen using Arch Linux. 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. Elseif (!preg_match('# (.*)404(.*)#i', $my_content) & !preg_match('#(.*)not found(.*)#i', $my_content)) (document.A developer's toolchain is like a lightsaber.
0 kommentar(er)
