Frontend Team
Meet the front-end team - the people responsible for why the platform interface looks so polished and functional.
We asked, they answered
A few questions we know you were dying to ask our Frontend team
We start the week by checking on what we didn't finish off last week and what has come in as high priority.
We don't have a daily sprint, we trust each other as a team to organise our own workloads.
The most important action of the day is to check Github and see that status of reviews, if there are any new bugs etc.
A penguin!
Either: Make It Work > Make It Right > Make It Fast
Or: We have style, we have grace, we paste memes all over the place.
GitHub, Zulip, or “in-person” on Google Meet
Our preferred method of communication is written - either on Github or Zulip - but we will have a call if it clears things up more efficiently.
We have multiple means of making collective decisions
- Github discussions (slow).
- Zulip comments and polls (quick..ish).
- Proof of Concept PRs (slow).
Additionally, one person might make a proposal and come up with an idea which they then put forward to the team. We make the final decision through discussion.
We are an autonomous team which likes to have fun whilst we ship.
We like it when our ideas are challenged.
We are comedy geniuses.
The way we collaborate and communicate, send each other memes, learn new things from each other and hear different ideas that everybody comes up with. We're completely open to new ideas.
Of course we also love the individual personalities of the team :)
Percussive maintenance (the old school method of hitting it with your hand).
In reality we mostly seek support from the other members of the team if we are really stuck on a problem. It's great to have a different perspective or at least another pair of eyes to look at the issue.
On Zulip (our chat tool) → we have a dedicated stream with this in mind.
Notifying others Zulip of significant codebase changes and celebrating merging of them on Zulip.