Self Eval

gistfile1.txt

| Category             	| Current Grade 	| Cost 	| Aspirational Grade 	| Notes 	|
|----------------------	|---------------	|------	|--------------------	|-------	|
| Planning             	| C              	| L    	| B                  	| There are now more documentation of this process via OKRs and specs so I feel the transparency has increased. |
| Design               	| C              	| XL    | B                   	| Need to factor in infrastructure when designing features. E.g. Blazor WebJS. |
| Build/Infrastructure 	| D             	| XL   	| B                  	| Need to align with rest of dotnet, we have too much "special" logic. |
| Coding               	| B             	| XXL   | A                  	| Need to respond to community PRs more promptly. |
| Testing              	| C             	| L    	| B                  	| How do we know we have the right amount of coverage? Coverage is mostly driven by devs but may become out of date over time. Need improvements in tooling for debuggability/reliability. |
| Performance/Stress   	| C             	| L    	| B                  	| I heard Sebastian finally got clients working in benchmarks v2! |
| Documentation        	| B             	| M    	| A                  	| Docs are what our users interact with first in many cases, we should aspire to make these as complete and informative as possible. |
| Issue Management     	| C             	| S    	| A                  	| I'm personnally terrible at this so... gonna drop this grade for the team a bit. |
| Release Activities   	| D             	| M    	| B                  	| There's a lot of manual (error prone) steps when patching and we need to migrate infrastructure. Traditionally we have had lots of trouble here with patching correctly and on time, though not always our fault. |