adam/org-notes
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

more

Browse Source
This commit is contained in:
Adam Mohammed
2023-08-16 15:49:23 -04:00
parent cef3a19c35
commit fcf7195e97
2 changed files with 115 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files

111
notes.org_archive
View File

@@ -372,3 +372,114 @@ Cluster api - failed provision
This is actually a good move. By just generating event by the ID we
reduce the chance that consumers depend on the state of an object
instead of just the ID.
* DONE Express concern around engineering quality
:PROPERTIES:
:ARCHIVE_TIME: 2023-08-16 Wed 10:36
:ARCHIVE_FILE: ~/org-notes/notes.org
:ARCHIVE_OLPATH: Tasks
:ARCHIVE_CATEGORY: notes
:ARCHIVE_TODO: DONE
:END:
I raised concerns that this result is doesn't meet the bar to achieve success on the problem we set out to solve.
I also do believe it doesn't help solve the problem
When I express that the immediate response was defense. That's the wrong response itself.
I can be clearer -- There are two points I want here,
1. I don't think this solves the problem we were targeting.
2. We have finite time, deciding if we want to iterate or redesign based on learning is a decision to make.
3. Option 3 which I didn't think was possible is to completely ignore the point.
Here's what's worse though. We're trying to transform the team to be enablers for other teams, so we need to set the bar.
We have people on this team that are trying to raise / set the bar, and when they raise concerns they are dismissed without
consideration.
My main concern is our ability to field feedback on this team. I don't
think I have many occurrences of differing opinions being given the required space.
At best it leads to apathy, at worst it leads to mediocrity. Either way it leads to a dysfunctional team by design.
Those people trying to raise the bar aren't doing so selfishly.
We don't get immediate gain out of performing better or working harder, we still get paid the same.
So why would we be striving to raise the bar? This is a fundamental question to see if a leader understands
what high performers need to thrive.
* DONE Try to deploy
:PROPERTIES:
:ARCHIVE_TIME: 2023-08-16 Wed 10:36
:ARCHIVE_FILE: ~/org-notes/notes.org
:ARCHIVE_OLPATH: Tasks
:ARCHIVE_CATEGORY: notes
:ARCHIVE_TODO: DONE
:END:
* DONE Write ExternalSecretPush for DB creds and Secret key base
:PROPERTIES:
:ARCHIVE_TIME: 2023-08-16 Wed 10:36
:ARCHIVE_FILE: ~/org-notes/notes.org
:ARCHIVE_OLPATH: Tasks
:ARCHIVE_CATEGORY: notes
:ARCHIVE_TODO: DONE
:END:
* DONE Present Users through the ResourceOwnerShim
:PROPERTIES:
:ARCHIVE_TIME: 2023-08-16 Wed 10:36
:ARCHIVE_FILE: ~/org-notes/notes.org
:ARCHIVE_OLPATH: Tasks
:ARCHIVE_CATEGORY: notes
:ARCHIVE_TODO: DONE
:END:
* TODO Put together POC for micro-caching RAILS
:PROPERTIES:
:ARCHIVE_TIME: 2023-08-16 Wed 10:36
:ARCHIVE_FILE: ~/org-notes/notes.org
:ARCHIVE_OLPATH: Tasks
:ARCHIVE_CATEGORY: notes
:ARCHIVE_TODO: TODO
:END:
* TODO Create a ticket to deal with 403s for provisioning failures
:PROPERTIES:
:ARCHIVE_TIME: 2023-08-16 Wed 10:36
:ARCHIVE_FILE: ~/org-notes/notes.org
:ARCHIVE_OLPATH: Tasks
:ARCHIVE_CATEGORY: notes
:ARCHIVE_TODO: TODO
:END:
* TODO MAKE TICKETS
:PROPERTIES:
:ARCHIVE_TIME: 2023-08-16 Wed 10:36
:ARCHIVE_FILE: ~/org-notes/notes.org
:ARCHIVE_OLPATH: Tasks
:ARCHIVE_CATEGORY: notes
:ARCHIVE_TODO: TODO
:END:
scheduler
worker configuration
cleanup job
* DONE Start Chuck Roast Braise
:PROPERTIES:
:ARCHIVE_TIME: 2023-08-16 Wed 11:21
:ARCHIVE_FILE: ~/org-notes/notes.org
:ARCHIVE_OLPATH: Tasks
:ARCHIVE_CATEGORY: notes
:ARCHIVE_TODO: DONE
:END:
* DONE Create Tickets for Scheduler
:PROPERTIES:
:ARCHIVE_TIME: 2023-08-16 Wed 11:21
:ARCHIVE_FILE: ~/org-notes/notes.org
:ARCHIVE_OLPATH: Tasks
:ARCHIVE_CATEGORY: notes
:ARCHIVE_TODO: DONE
:END: