- Is a proven leader.
- Can communicate effectively.
- Cares deeply about quality and long-term maintainability of the product.
- Does not accept monotonous tasks, but seeks ways to automate and be more efficient.
- Is not intimidated by problems or new challenges, but actively seeks solutions.
- Does not accept roadblocks, but actively seeks ways around them.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
describe('When deconstructing an object', () => { | |
const car = { | |
color: "red", | |
size: "large", | |
doors: [{section: "front", side: "driver"}, {section: "front", side: "passenger"}], | |
make: "Nissan" | |
}; | |
it('should be able to deconstruct the object and get only the properties we want', () => { | |
const {color, size, doors} = car; | |
expect(color).to.equal("red"); |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Feature: Test #6: Gherkin code in more than one list | |
List 1 With Generic Name | |
List 2 With Another Generic Name | |
Scenario: Cow gives milk willingly | |
GIVEN a cow | |
WHEN I milk it | |
THEN I get milk | |
Scenario: Cow refuses |
- Think about 1 to 5 developers who you think exemplify the Sr Developer Criteria
- Send your list of 1 to 5 names of your fellow developers (not yourself) to @byron (PRIVATELY) in slack.
- Please include your reasons for the names you send.
- Byron will receive all the names and compile them into a spreadsheet, analyze the list and use it to make a decision on the first small group of senior developers.
- Byron reserves the right to have the final decision in this first round of Sr Devs.
- Is a proven leader.
- Can communicate effectively.
- Cares deeply about quality and long-term maintainability of the product.
- Does not accept monotonous tasks, but seeks ways to automate and be more efficient.
- Is not intimidated by problems or new challenges, but actively seeks solutions.
- Does not accept roadblocks, but actively seeks ways around them.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Who is responsible for detailed sprint plan? |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
What measures sprint progress and forecasting? |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Who leads release planning? |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In what ceremony does the team makes changes to the process? |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Who is responsible for the detailed sprint plan? |