Releases: Financial-Times/engineering-progression
Releases · Financial-Times/engineering-progression
v1.0.0-beta.1
- Update README.md from alpha to beta (#237)
- J -> S2 Technical trade offs J-S2 (#202)
- Mid -> S1 Shares knowledge with others (#228)
- Mid -> S1 Presents their own work clearly (#229)
- Mid -> S1 Has responsibility for others’ development (#230)
- Mid -> S1 Tackles simple cross team (#231)
- Fix grammar issue (#232)
- Mid -> S1 protect user data (#233)
- Mid -> S1 Understands the security attack vectors (#234)
- Mid -> S1 Manages technical trade-offs - Mid examples (#235)
- Mid -> S1 Where appropriate, builds on other teams (#236)
- Use TCO, not overall cost (#204)
- Remove willingness from competency (#209)
- Split code quality competency (#201)
- Fix spelling of "decisions" (#203)
- Mid -> S1 workshop Provides feedback on peer’s work (#200)
- Mid -> S1 Runs meetings (#199)
- Update competencies.yml (#197)
- Update competencies.yml (#198)
- Leads on fixing production issues (#196)
- Mid -> S1 Clarify what "ambassador" means (#164)
- added S1 competency on working with complex, multipart tech; (#192)
- Add examples to feedback for Juniors (#187)
- Clarify cross group collaboration competency (#188)
- Add examples for "Uses continuous integration" (#190)
- Add another example to delivery competency (#189)
- Add examples to feedback competency (#186)
- examples added to clarity what production issues may be, and line com…
- Add sentence on duplicate evidence (#185)
- Rework the "local development" competency (#184)
- Reword & add examples for "uses code" competency (#183)
- Add examples to hiring lead competency (#166)
- Remove unreasonable expectation for juniors (#167)
- faq covering principal cap and individual contributor (#168)
- Update release section of readme (#162)
v1.0.0-alpha.16
- Add the "How to use" link to the spreadsheet (#163)
- Update release section of readme (#162)
- Add an FAQ covering principal cap and individual contributor (#168)
- Remove unreasonable expectation for juniors (#167)
- Add examples to hiring lead competency (#166)
- Reword and add examples for "uses code" competency (#183)
- Rework the "local development" competency (#184)
- Add sentence on duplicate evidence (#185)
- Add examples to clarity what production issues may be (#191)
- Add examples to feedback competency (#186)
- Add another example to delivery competency (#189)
- Add examples for "Uses continuous integration" (#190)
- Clarify cross group collaboration competency (#188)
- Add examples to feedback for Juniors (#187)
- Add a Mid-Senior1 competency on working with complex, multipart tech (#192)
- Clarify what "ambassador" means (#164)
v1.0.0-alpha.15
v1.0.0-alpha.14
v1.0.0-alpha.13
- Fix typo on J->M Delivery: Works on most important task (#122)
- Add automated accessibility tests to the website (#123)
- Reword & add examples to 9e1a0313-f602-4786-97c6-d4d49506f0bb (#135)
- Add more examples to 787be828-9a7f-4998-9bc6-a8b06f2d77de (#134)
- Relax the requirement that all competencies be met (#133)
- Create a clearer thread around presenting work (#138)
- Fix up debugging competency (#137)
- Remove very difficult to meet leadership competency (#84)
- Update data/competencies.yml (#136)
v1.0.0-alpha.12
v1.0.0-alpha.11
- Reorganise the competencies page on the website (#106)
- Fixed some typos and suggested some changes to wording (#107)
- Relax wording on "contributes to personal development" (#110)
- More examples to "influences a community of practice" (#111)
- Add some examples to inclusivity competency (#112)
- Make team needs competency more concrete (#114)
- Add clarifying example to security competency (#115)
- Add more examples to "presents work" competency (#113)