Prioritizing the grind #136
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
👷 Deploy Preview for shane-is-me processing.
|
treighton
reviewed
Dec 9, 2023
Comment on lines
81
to
83
| Flow vs red tape | ||
|
|
||
| Counting points vs demoing features |
There was a problem hiding this comment.
Are these points you'll elaborate on?
I think points vs demoing features could be a whole section
There was a problem hiding this comment.
Yeah the short-hand stuff is just for me to remember what I was thinking when I first thought of it. Most of the things I put up can be expanded, in fact most of my blog posts are just expansions of previous paragraphs or sentences from older ones...
treighton
reviewed
Dec 9, 2023
|
|
||
| Fostering this environment will empower your team to continue this collaboration without being told to do so. People will automatically jump in to help those that need it, or offer their support to teach those that want to learn. This starts to become a fun place to go to work every day. It creates a cycle of more capable and happy individuals which leads to the feeling of rampant creation anyone that's been on one of these teams will recognize immediately. | ||
|
|
||
| There is an upper limit to how expensive collaboration is on a given team. Communication scales exponentially for every new person on a team which can cause everything to grind to a halt. There are also best judgement calls you will make regularly about critical fires that come up that take precedence, as long as this is not the norm this is totally normal. Efficiency is important, but not if it kneecaps your team every day away from what will help them grow and work on what they feel is important. |
There was a problem hiding this comment.
Learning how to find the upper limit, or how to notice when you're approaching it is a tough skill to learn. Do you have "flags" that you watch for? Could those be made into a pseudo code?
while(
engagement && perceivedProductivity &&
learning &&
deliveringValue
)
Or 🤷♂️
There was a problem hiding this comment.
Good question, I'll think of ways to talk more practically about it.
Bumps [gatsby-remark-autolink-headers](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-remark-autolink-headers) from 6.12.1 to 6.13.0. - [Release notes](https://github.com/gatsbyjs/gatsby/releases) - [Changelog](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-remark-autolink-headers/CHANGELOG.md) - [Commits](https://github.com/gatsbyjs/gatsby/commits/[email protected]/packages/gatsby-remark-autolink-headers) --- updated-dependencies: - dependency-name: gatsby-remark-autolink-headers dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [gatsby-transformer-remark](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-transformer-remark) from 6.12.1 to 6.13.0. - [Release notes](https://github.com/gatsbyjs/gatsby/releases) - [Changelog](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-transformer-remark/CHANGELOG.md) - [Commits](https://github.com/gatsbyjs/gatsby/commits/[email protected]/packages/gatsby-transformer-remark) --- updated-dependencies: - dependency-name: gatsby-transformer-remark dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [gatsby-plugin-feed](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-plugin-feed) from 5.12.0 to 5.13.0. - [Release notes](https://github.com/gatsbyjs/gatsby/releases) - [Changelog](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-plugin-feed/CHANGELOG.md) - [Commits](https://github.com/gatsbyjs/gatsby/commits/[email protected]/packages/gatsby-plugin-feed) --- updated-dependencies: - dependency-name: gatsby-plugin-feed dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [msgpackr](https://github.com/kriszyp/msgpackr) from 1.6.1 to 1.10.1. - [Release notes](https://github.com/kriszyp/msgpackr/releases) - [Commits](https://github.com/kriszyp/msgpackr/commits/v1.10.1) --- updated-dependencies: - dependency-name: msgpackr dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.15.1 to 1.15.4. - [Release notes](https://github.com/follow-redirects/follow-redirects/releases) - [Commits](follow-redirects/follow-redirects@v1.15.1...v1.15.4) --- updated-dependencies: - dependency-name: follow-redirects dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
…redirects-1.15.4 Bump follow-redirects from 1.15.1 to 1.15.4
…r-1.10.1 Bump msgpackr from 1.6.1 to 1.10.1
…plugin-feed-5.13.0 Bump gatsby-plugin-feed from 5.12.0 to 5.13.0
…transformer-remark-6.13.0 Bump gatsby-transformer-remark from 6.12.1 to 6.13.0
…remark-autolink-headers-6.13.0 Bump gatsby-remark-autolink-headers from 6.12.1 to 6.13.0
Bumps [gatsby-transformer-sharp](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-transformer-sharp) from 5.12.0 to 5.13.0. - [Release notes](https://github.com/gatsbyjs/gatsby/releases) - [Changelog](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-transformer-sharp/CHANGELOG.md) - [Commits](https://github.com/gatsbyjs/gatsby/commits/[email protected]/packages/gatsby-transformer-sharp) --- updated-dependencies: - dependency-name: gatsby-transformer-sharp dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
…transformer-sharp-5.13.0 Bump gatsby-transformer-sharp from 5.12.0 to 5.13.0
drainpip
commented
Jan 29, 2024
| @@ -1,6 +1,6 @@ | |||
| --- | |||
There was a problem hiding this comment.
Changes in this file were to separate out the focus of this post (long-term thinking vs. daily grind)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.