**Farley’s Developer Stack: Evolving Toward Decentralization and Redundancy**
As a **hobbyist developer**, my tools and processes are continuously adapting to align with my principles of independence, resilience, and innovation. Here’s an inside look at my current stack and how it’s transforming:
### **Editing and Coding**
I rely on **VS Code**, an extensible and feature-rich code editor, to manage and edit my source code. Its flexibility and robust integrations allow me to stay efficient across diverse projects, whether building decentralized solutions or backend systems.
### **Version Control and Redundancy**
At the heart of my workflow is a **Gitea server**, which I self-host and fully control. My Gitea server serves as the primary repository, maintaining the authoritative version of my projects.
To ensure redundancy and provide a public-facing repository for collaboration, my Gitea server is configured to **push updates to GitHub** and can also **pull changes for syncing**. This setup combines the best of both worlds:
- **Full Ownership**: By hosting my own Gitea server, I maintain control over my code and workflows.
- **Global Reach**: By mirroring to GitHub, I leverage its ecosystem for visibility, collaboration, and integration with third-party tools.
### **How This Is Transforming My Workflow**
1. **Primary Control**: Gitea ensures I own and control the authoritative version of my projects, minimizing reliance on centralized platforms.
2. **Redundancy and Reliability**: Mirroring to GitHub adds a layer of resilience, protecting my work from potential downtime or data loss.
3. **Value Alignment**: This decentralized and redundant approach mirrors my broader belief in systems that empower individuals to take ownership of their resources—whether it’s code or currency.
This stack isn’t just about tools—it’s a reflection of my philosophy. It’s about crafting systems that are robust, independent, and future-proof.
How does your dev stack reflect your principles? Let me know in the comments!