Way of Work
Let's break down how we as the Vinkil team work.
Culture
The devleopment team of Vinkil lives by the mentality of think simple, implement well, accept feedback, strive for better. By keeping to that ethos we will always bring the best code, features, ideas and energy to every piece of Vinkil we engage with.
Toolset
| Tool | Purpose | Notes |
|---|---|---|
| Github | Version Control | For managing code versions |
| Cloudflare | Hosting | Static Web App Hosting |
| Digital Ocean | Hosting | Backend and Database Hosting |
| Discord | Communication | For team collaboration |
| JIRA | Project Management | For tracking tasks and issues |
| Github Actions | Continuous Integration | For automated builds and tests |
Development Patterns
| What | Why |
|---|---|
| Trunk Based Development | Allowing multiple features to be developed at the same time |
| Data Driven | Start at the data, then work your way up. This will make us think, dev and achieve objectives in the same way |
| A Day Worked is a Day Checked In | If you work on something for the day, it will be checked in that day |
| Feature Flags | Everything we do is behind a feature flag. This helps with the checkin daily |
| Test first, thank me later | All features need testing with them. This allows us to push without worry |
| Continous Deployment | Using the methodology of every commit goes straight to production making sure flags and tests are right makes us move fast |
| Do The Right Thing | Being a good developer means being good at the admin. making sure our teams boards etc are always 100% right makes work happen faster |
| Document | No matter how small or large, if it's code, it's documented on our internal wiki or client facing wiki |