1. The Environment: Linux ## 2. The Physicality: Split Keyboards & Touch Typing ## 3. The Tooling: Shortcuts & Flow ## Bonus: My VS Code Navigation Toolkit ## Using F-Keys (via Fn layer) ## Without F-Keys (The Essentials) ## Typical Workflow ## Useful Additions ## Conclusion In this post, I want to briefly talk about how your environment (Linux), your hardware (keyboard & touch typing), and your tooling (shortcuts) form the three pillars of Software Craftsmanship. Let’s be clear: these are not the most important skills for a developer, nor are they the primary way to evaluate a grade. They won’t replace business domain knowledge, solid architectural decisions, or problem-solving abilities. However, "Mastership is not just about WHAT you create, but also HOW you create it." By removing the friction between your mind and the screen, you free up space for pure creativity. Here are my three pillars: Switching to Linux is more than just changing an OS; it’s a transition from being a "consumer of interfaces" to a "creator of systems." In Linux, the boundary between you and the running code fades away. You start to understand how the file system, processes, and networks actually work just by living in the environment. For me, moving to Linux was a massive skill bump, even though many friends told me at the start that "the OS doesn't matter." The journey from being afraid of the terminal to confident mastery is incredibly rewarding. This is about removing physical bottlenecks. When you don't have to look at your hands, code flows directly from your brain to the editor. Shortcuts are all about the Flow State. Every time you reach for the mouse, you create a micro-interruption in your train of thought. A quick disclaimer: Don't be a fanatic. If you get frustrated every time you touch a mouse, or if you insist on reading raw Markdown in a terminal just to look "pro"—that’s probably too much. I use VS Code, I don’t mind using the mouse when it makes sense, and I read my emails in a browser. Balance is key. As a bonus, here is a snippet from my personal cheat sheet for VS Code navigation: Ctrl + P (Open File) → Ctrl + Shift + O (Find Function) → F12 (Go to Definition) → Alt + ← (Go Back). Craftsmanship is a journey. These tools won't make you a Senior developer overnight, but they will make the road there much more enjoyable and efficient. *What does your "craftsman" setup look like? * Templates let you quickly answer FAQs or store snippets for re-use. Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink. Hide child comments as well For further actions, you may consider blocking this person and/or reporting abuse CODE_BLOCK:
Ctrl + Fn + = CODE_BLOCK:
Ctrl + Shift + O CODE_BLOCK:
Ctrl + Shift + P CODE_BLOCK:
Ctrl + Shift + \ CODE_BLOCK:
Ctrl + Shift + O CODE_BLOCK:
Ctrl + Shift + F CODE_BLOCK:
Ctrl + Shift + H CODE_BLOCK:
Ctrl + Space CODE_BLOCK:
Ctrl + Shift + Space - The Rule: Anything you can do in a GUI (and many things you can't) can be done via the terminal—often much faster.
- The Base: Terminal skills are "evergreen." They are portable and don't become obsolete when a new fancy app comes out.
- The Perks: Native containers, Btrfs snapshots, and total control. Once you go Linux, you’ll only keep Windows around for the games that won't run elsewhere! - The Health Factor: A split keyboard is about longevity. Avoiding wrist pain is a professional necessity, not a luxury.
- Touch Typing vs. "Hunt & Peck": An office "hunter" might peak at 50 WPM, while the average is closer to 20-30 WPM. A decent touch typist easily hits 60–80 WPM, and pros go well beyond 130–160+ WPM.
- The Joy: Honestly, the biggest win isn't just speed—it's the feel. You start enjoying the process of typing itself. Even 40-50 WPM for plain text makes work remarkably comfortable.
