Home

The "templated" project

Who

First of all, hello. I'm LeChatErrant, software engineer studying at Epitech Paris, creator and maintainer of API-template

I'm currently working at Tresorio, a green cloud-computing startup, at the position of lead-developer of the cloud-rendering branch (distributed computing for 3D animation)

Passionated by the design of backend software and distributed systems, I'm aiming to offer tools to help building the most complete architecture possible

What

The "templated" project is divided into 4 parts :

API-template
back-office-template (coming soon)
devops-template
cli (wip)

Why

Starting a whole new stack from scratch is painfully. You have to

Choose between multiple technologies
Adopt a coding style
Enforce good practices
Setup a lot of tooling
Make sure futur developpers will follows instored guidelines, to keep the project maintainable

Those decisions are often poorly made and lead to multiple refacto, since

Your skills evolves along with the project
You learn new technologies / ways to achieve something
Most of the decisions taken become invalid are the project grows
Team changes

That's why I archived every mistakes I learned from and every choices made in this project. It ensures :

All have already taken care of, from the database migrations to the monitoring of your scaled architecture
Don't loose time writing all nasty configurations
Best tooling and technologies has already been choosed
Untrackable bugs has already been tracked
Benefit from the experience already gained on huge production project