Difference between revisions of "CNA2013: Ah-ha moments"
From CitconWiki
Jump to navigationJump to searchm |
m |
||
| Line 9: | Line 9: | ||
* Can I grow people: Focus, Slack, Belief, Humility; List of what are things needed fundamentally for Continuous Delivery preconditions | * Can I grow people: Focus, Slack, Belief, Humility; List of what are things needed fundamentally for Continuous Delivery preconditions | ||
* Many solutions, no silver bullet; Developers doing demos that they know will work: skipping down happy path. | * Many solutions, no silver bullet; Developers doing demos that they know will work: skipping down happy path. | ||
| − | * | + | * Google's "testing on the toilet", we need CS kinds of literature in our bathroom or common area |
* Integrating QA role into developers day-to-day work, everyone needs to be doing. | * Integrating QA role into developers day-to-day work, everyone needs to be doing. | ||
* Complicated algorithm solved; Surprised how few people are doing continuous delivery, despite literature | * Complicated algorithm solved; Surprised how few people are doing continuous delivery, despite literature | ||
Revision as of 11:01, 25 August 2013
- The pipeline needs to be versioned, in source countrol
- Here for answers to problems, and many have the same questions for universal applicability
- Enjoying listening to people handling roadblocks, learning about UI testing
- Common theme: Improving a build time or pipeline, belief that improvement is possible, cultivate intolerance for inefficiency
- Enjoy seeing new perspectives
- e.g. Check in every 15 minutes. Is that possible? Maybe it is.
- That each session had learning, e.g. learning how other shops are testing
- Hearing about a lot of different setups. Achieving buy in sessions, separating pain from solutions
- Can I grow people: Focus, Slack, Belief, Humility; List of what are things needed fundamentally for Continuous Delivery preconditions
- Many solutions, no silver bullet; Developers doing demos that they know will work: skipping down happy path.
- Google's "testing on the toilet", we need CS kinds of literature in our bathroom or common area
- Integrating QA role into developers day-to-day work, everyone needs to be doing.
- Complicated algorithm solved; Surprised how few people are doing continuous delivery, despite literature
- Many unanswered questions remain, different philosophies persist beyond our discussions.
- Branching is just delayed integration (Thanks, JTF)
- Entered in believing it was hard to do and continue to believe this, despite literature; Love open spaces format
- From hardware background
- difference Continuous delivery and continuous deployment
- Property-based testing new and interesting
- Realizing code doesn't exist in a vacuum, traceability into what make things break, we can investigate how to solve defects
- hiring or growing, Give slack, but monitor
- Love open space format and hallway conversations
- Happy to return to CITCON, will plan to return to Austin
- Growing/hiring discussion, that humility is important- realizing we don't know things
- Test expressivity, business people should be able to read our tests. Not only Cucumber, but RSpec, JUnit, etc too.
- Code coverage is not per line, but per logic piece within a line
- What percentage of people read books? 10% - 15%, hire people that are trying to grow themselves
