The Helix PACT is:
- Product Experience
#p - Architecture & Technology
#a - Culture & Team
#c - Tools of the trade
#t
We will work as meritocracy, input from others, and reviewing PRs and contributing to other projects is a top priority.
If we don't have a good reason why something should be private, it should be public. All new repos, live on public github.
We are a diverse team in every respect.
(Virtual) Get-togethers, Show-&-Tells and hackathons only.
Code wins. Everybody codes. Commits.
Well designed, beautiful output.
In that order.
Always.
Simple, Fast and Up beats elegant.
As global as the web with regards to languages, delivery, and performance
Uncached things are fast. <300ms fast. always.
Everything has an API, REST of course.
period.
The software is secondary, what we build is a service. Pager Duty for everyone.
Discussions and decisions are open, asynchronous and archived.
Results of commits can be seen in a production environment in 60 seconds or less.
It's "minimum" when the team has doubts that it could work. It's viable when users don't care and use it anyway.
Listen closely to customer and user feedback. Measure qualitatively and quantitatively.
Whether he wants it or not, the dictator has the last word on product and architecture
If we don’t make a wrong decision once in six months, we are not ambitious enough. (Or self-critical)
The goal of the service is not to deliver features, but to get jobs done for our users and customers.
URI, CSS, Client Code ... Edge ... (Server Code?)
Github, Google Drive and One Drive.
On the server-side JavaScript and Python are used for the respectively intuitive payloads.
Native.
Remember a good drag and drop experience on mobile?
Output is assembled on request.
Make maximum use of available services.
The goal is 100. Don't give it up.
Less code is better. Actively manage the dependency graph to an absolute minimum.
a.k.a. polished, but tweakable.
Support for simple local development is imperative. Low entry barrier.
Power content, workflows, designs, and operations.
All documents (md, docx, gdoc, xlsx, sheets) should read well and intuitive when viewed/edited through their native interface.
Let's design interfaces that are bold now, we can go back to safe and boring later on.
We will put no effort into making our code compatible with IE.