The Stand-up is Dead. Long live the Stand-Up.
The traditional Scrum stand-up suggests that members go around a standing circle and answer the following questions:
Answers give an snapshot pf what the developer as completed, what remains, and anything that stands in the way of progress towards meeting delivery goals.
| Beginners – Never meditated | |
| One: Eat one meal a day in silence | |
| Doing so will bring your awareness into the now | |
| Don’t listen to anything, don’t talk to anyone; just sit, eat, watch, and enjoy your meal | |
| I guarantee your food will actually taste better | |
| Two: Drink one cup of tea per day | |
| Bring your full awareness into this experience, feeling every mouthful as it goes down | |
| Open up your senses by smelling the tea's’ aroma and by watching the liquid move around your cup | |
| Three: Have a mindfulness shower | |
| In the shower close your eyes and become aware of your feet. Feel the energy pulsating in and around them |
An Engineering Lead will be the technical lead for some area of the Brad’s Deals engineering organization. They serve as the primary architect and business liaison for technology decisions pertaining to their area of specialization. They act as the primary point of escalation for resolving conflicting opinions on technical implementation decisions. They are expected to devote a portion of their time to researching, recommending and promoting the best tools available to the team. They will serve as the primary point of contact with Product Owners and business stakeholders on questions that relate to their area of specialization. They are responsible of raising visibility of team-wide system, process, or technology issues that relate to their area of specialization.
The DevOps Engineer provides day-to-day support for the applications, services and tools in the Brad's Deals ecosystem. This individual is responsible for the research and development of tools, technologies, and practices in the areas of application deployment and management. This individual is responsible for the design and architecture of high-availability, fault-tolerant systems. This individual is responsible for ensuring that Brad's Deals can grow and operate at scale.
Specific responsibilities of the DevOps Engineer include:
| # | |
| # Ted Price | |
| # Fun demo using define_method | |
| # | |
| class Base | |
| def self.has_a(*attrs) | |
| attrs.each do |attr| | |
| define_method(attr) do | |
| instance_variable_get("@#{attr}") | |
| end |
Notes on CoreOS
| ===== | |
| Jr. Programmer | |
| ===== | |
| Languages | |
| - Has a language she wants to master | |
| - Can read, describe basic program flow given a code sample | |
| - Can write basic elements of a program | |
| - Knows the basic building blocks, terminology of the language | |
| - Has idea of other popular languages that might complement this language |
| = Programming = | |
| Does the codebase look like it was written by a single person | |
| Leads need to code 30% of the time, 1.5 days week! (respect is the currency of the realm) | |
| consistency over cleverness | |
| How long does the build stay broken? | |
| = Team Questions = | |
| Do people avoid conflict? | |
| Do people offer new ideas? (do people feel they can fail?) | |
| Do people flag when they need help? (reinforcing cycle: "i'm almost done, i don't need help") |
Annual reviews are "cave dives,"→ try quarterly reviews
Typical "carrier track" contains some overarching miletones, title and salary bumps → try a "portfolio of experiences and skills" that have been acquired, satisfactorily met, before moving people on.
Set expectations early and often
Professional development - skills that can be applied anywhere
vs
Career development - skills that are targeted to current occupation and role