My Current Tech Stack in 2026
Introduction
While we're currently in December with one month remaining in 2026, I'm confident in sharing my current technology stack as I have no immediate plans to change these tools. This represents my established comfort zone in development workflows, though I acknowledge that the rapidly evolving tech landscape might bring changes by 2027.
In this overview, I'll detail my current software stack and explain why each component has become integral to my development process.
Primary Programming Language: Go
Go (often referred to as Golang) serves as my primary programming language for most software development projects.
Why Go Works for Me:
- Performance Characteristics: Combines low-level control similar to Rust with approachable syntax
- Simplicity: Maintains Python-like readability while delivering robust performance
- Execution Speed: Compares favorably with C++ for many use cases
- Concurrency Model: Exceptionally well-designed and straightforward to implement
- Comprehensive Standard Library: Most development needs are covered without external dependencies
- Compilation Benefits: Error detection during editing rather than runtime
- Static Typing: Provides type safety and better code intelligence
Areas for Improvement:
- Repetitive error checking with
if err != nilpatterns - Occasional rigidity from static typing in rapid prototyping scenarios
- Capitalization conventions for exported identifiers
Wails Framework
Wails represents the Go equivalent of Tauri, enabling desktop application development with frontend technologies. I've covered this framework in detail in previous blog posts and appreciate its seamless integration between Go backend logic and modern frontend interfaces.
Secondary Programming Language: MiniScript
Despite its niche status, MiniScript has secured a permanent place in my programming toolkit this year.
Advantages:
- Accessibility: Even more approachable than Python for beginners
- Supportive Community: Active and helpful, though relatively small
- Mini Micro Integration: Tightly coupled with an excellent development environment
- Rapid Prototyping: Ideal for quick implementation and testing
Limitations:
- Limited Resources: Fewer tutorials and learning materials available compared to mainstream languages
Mini Micro Environment
Mini Micro provides what I consider the most accessible environment for creating simple games and prototypes. As I've mentioned in previous posts, it serves as an exceptional starting point for game development beginners and remains my preferred choice for game jam projects due to its rapid iteration capabilities.
Game Development: Godot
While my focus has shifted toward software development using Go and Wails, Godot remains my engine of choice for game projects.
Strengths:
- Lightweight: Minimal resource requirements
- Performance: Responsive even on modest hardware
- Open Source: Complete transparency and community-driven development
- Comprehensive Features: Well-rounded out-of-the-box experience
- GD Script: Purpose-built scripting language optimized for game development
Considerations:
- 3D Performance: While improving, still trails dedicated 3D engines in some scenarios
- Asset Pipeline: Occasionally requires additional configuration compared to Unity
Development Tools and Software
Daily Drivers:
- Brave: Primary web browser for development and browsing
- Zed: Code editor of choice for its speed and minimal resource usage
- Notepad++: Lightweight text editor for quick notes and file edits
- Aseprite: Specialized pixel art creation and editing
- Knowledge Management: Currently evaluating Logseq after extensive Obsidian use
- Version Control: Git with GitHub for all project management
- Audio Processing: Audacity for editing and format conversion
- Screen Recording: Streamlabs despite OBS's lighter footprint, for specific workflow advantages
- Device Mirroring: ScrCpy for seamless phone-to-computer connectivity
Android Applications:
- Pie Launcher: Minimal, open-source app launcher that revitalizes older devices
- Termux: Powerful terminal environment for mobile development tasks
Conclusion
This technology stack represents my current equilibrium between performance, productivity, and personal preference. Each tool has earned its place through extensive use and demonstrated value in my daily workflow.
While technology preferences remain highly personal, this configuration has proven exceptionally effective for my specific needs across software development, content creation, and game development projects.
As the tech landscape continues to evolve, I remain open to exploring new tools that might enhance my workflow, but for now, this stack provides the perfect balance of capability and comfort.
Resource Links
- Brave Browser: https://brave.com/
- Zed Editor: https://zed.dev/
- Mini Micro: https://miniscript.org/MiniMicro/index.html#about
- Wails Framework: https://wails.io/
- Godot Engine: https://godotengine.org/
- Aseprite: https://www.aseprite.org/
- Scrcpy: https://github.com/Genymobile/scrcpy
- Streamlabs: https://streamlabs.com/
- Audacity: https://www.audacityteam.org/
- Notepad++: https://notepad-plus-plus.org/
- Pie Launcher: https://f-droid.org/en/packages/de.markusfisch.android.pielauncher/
- GitHub: https://github.com/
Detailed Written Reviews:
- EXPERIENCE: MINI MICRO: My Experience With Mini Micro
- EXPERIENCE: ZED CODE EDITOR: My Experience With Zed Code Editor
Video Experiences:
- EXPERIENCE: BRAVE: The Brave Browser Experience
- EXPERIENCE: MINI MICRO: The Mini Micro Experience
Connect With Me:
- YouTube Channel: DatonedevYT
- Discord Community: Join our development discussions
This post is part of my Experience Series, documenting my journey with various development tools and technologies.

