Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added types of meetings #105

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Added types of meetings #105

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
70939d4
Added types of meetings
Loco1982 Feb 7, 2024
f612a79
Fixed writing thanks to Harry's comments
Loco1982 Feb 7, 2024
58101b5
Fixed typos and added standup explanation
Loco1982 Feb 8, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 33 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,9 +14,15 @@
- [Even if you work with a client you're working for Lambda at the end](#even-if-you-work-with-a-client-youre-working-for-lambda-at-the-end)
- [Do The Simplest Thing That Could Possibly Work (aka KISS)](#do-the-simplest-thing-that-could-possibly-work-aka-kiss)
- [Development process/workflow](#development-processworkflow)
- [Daily (15' max)](#daily-15-max)
- [Weekly (30' max)](#weekly-30-max)
- [Sprint Planning (30' max)](#sprint-planning-30-max)
- [Retrospective (10' max)](#retrospective-10-max)
- [All hands (or Federico's updates) (varies)](#all-hands-or-federicos-updates-varies)
- [One on ones (30' max)](#one-on-ones-30-max)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- [One on ones (30' max)](#one-on-ones-30-max)
- [One-on-ones (30' max)](#one-on-ones-30-max)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done!

- [Design and coding standards](#design-and-coding-standards)
- [GitHub \& GitLab](#github--gitlab)
- [Working on open source projects](#working-on-open-source-projects)
- [Working on open-source projects](#working-on-open-source-projects)
- [Slack channels](#slack-channels)
- [Community projects](#community-projects)
- [Development Environment Setup](#development-environment-setup)
Expand Down Expand Up @@ -72,7 +78,7 @@
- [Algorithmics](#algorithmics)
- [Computability](#computability)
- [Consensus](#consensus)
- [Cryptography](#cryptography)
- [Cryptography](#cryptography-1)

---
> A boring codebase doesn't make a bored developer, on the contrary, it frees developers up to think about important stuff and deliver value to the business. Just as I want my language to be boring so I can focus on interesting stuff, I also want my tech stack to be boring - the interesting bits should be in the value added, not the stuff under that.
Expand Down Expand Up @@ -211,9 +217,32 @@ Strive for solving problems in the simplest way possible. To achieve this, you f
- [Yagni by Martin Fowler](https://martinfowler.com/bliki/Yagni.html)

### Development process/workflow
- There is a weekly call with every member of the team to set the most important goals of the week, as well as a daily call to focus on the problems of the daily tasks.

#### Daily (15' max)

A call that's done at the same time every workday to to go through general updates, personal yesterday's work, personal tasks of today, and blockers/possible risks.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
A call that's done at the same time every workday to to go through general updates, personal yesterday's work, personal tasks of today, and blockers/possible risks.
A call that's done at the same time every workday to go through general updates, personal yesterday's work, personal tasks of today, and blockers/possible risks.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good eye!


#### Weekly (30' max)

A weekly call with every member of the team to set the most important goals of the week.

#### Sprint Planning (30' max)

- When working on projects, the specific tasks to tackle are written in tickets on Github Projects. Some actual Lambda's projects are working on other project management software, but these are legacy.
- [The Manager's Path](https://www.amazon.com/Managers-Path-Leaders-Navigating-Growth/dp/1491973897/ref=sr_1_1?dchild=1&keywords=the+managers+path&qid=1625162711&s=books&sr=1-1)
- Every week or every two weeks there's a call named Sprint Planning to create a new sprint on the Github Project and select the issues that will be worked on. The Tech Lead and the Project Manager (where applicable) will lead these meetings.

#### Retrospective (10' max)

- Before or after every sprint planning there will be a space for the team to reflect on what has been done right or wrong during the sprint and to propose practices to mantain or avoid. We don't always do these meetings, but having the praxis to reflect and balance is a useful tool.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Before or after every sprint planning there will be a space for the team to reflect on what has been done right or wrong during the sprint and to propose practices to mantain or avoid. We don't always do these meetings, but having the praxis to reflect and balance is a useful tool.
- Before or after every sprint planning there will be a space for the team to reflect on what has been done right or wrong during the sprint and to propose practices to maintain or avoid. We don't always do these meetings, but having the praxis to reflect and balance is a useful tool.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thx


#### All hands (or Federico's updates) (varies)

- These are sporadic meetings where upper management tell updates about the company.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- These are sporadic meetings where upper management tell updates about the company.
- These are sporadic meetings where upper management tells updates about the company.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thx!


#### One on ones (30' max)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
#### One on ones (30' max)
#### One-on-ones (30' max)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thx!


- These are meetings between the individual contributor and one of the people he reports to (Tech Lead or PM).
- The idea of these meetings is explained in chapter 1 of this book: [The Manager's Path](https://www.amazon.com/Managers-Path-Leaders-Navigating-Growth/dp/1491973897/ref=sr_1_1?dchild=1&keywords=the+managers+path&qid=1625162711&s=books&sr=1-1)
- Chapter 1 *Estimate reading time: 1 hour*

### Design and coding standards
Expand Down