Read on Twitter
Gather round, let me tell you a story about this gif.
A little over a month ago, @tammmri joined my team as a junior Python developer. She was an @outreachy intern and is an active @OpenStack contributor. IT is her second career, and she has been in the field for two years.
Less than a week into being with us, the onboarding mechanics were complete and she was soaking up new knowledge like a sponge, rushing through internal training on http://academy.citycloud.com"> http://academy.citycloud.com at an alarming pace.
At two weeks, she was contributing patches to courseware and pushing them to production via our CI/CD pipeline, with minimal coaching from @elenalindq (that& #39;s where the gif at the top of the thread came in).
At about the same time, she flagged a bug in an OpenStack project (one she previously hadn& #39;t been working on), and helped with review and testing for the fix, which landed in a matter of days.
Throughout, she& #39;s been excellent in distributed-team communications, keeping everyone informed and asking all the right questions when she needed — and also having the tenacity to bite and chew on issues she ran into, herself.
None of us had to tell her about the value of docstrings, unit tests, mocking, and writing good commit messages.
( @vkmc, if this is at least partly your doing, thank you for helping her be excellent.)
( @vkmc, if this is at least partly your doing, thank you for helping her be excellent.)
Today, she landed her first refactoring patch in functional production code — a patch of the best possible kind, one that maintains an existing bit of functionality while deleting half of its code, keeping things DRY.
Hire. Junior. People.
