Team Name: the breakers the code breakers splice and slice devisive Iron Maidener DRAGONFORCE II
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
Team Name: | |
the breakers | |
the code breakers | |
splice and slice | |
devisive | |
Iron Maidener | |
DRAGONFORCE II | |
Buying locally used is a great option. Just make sure to be safe (duh) and individually demo the speakers before you buy. Buying affordable speakers used online is tough due to shipping costs; they can easily run $50-$100 or higher which kind of kills the value.
Our own sidebar guides are a great resource for bookshelf speakers/ and tower speakers.
This roundup of bookshelf speakers at TheWirecutter is a good place to get started. There are some notable omissions, but it's fairly comprehensive and (most importantly) it offers some background about what to look for.
Speakers (Compact)
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 Went Well? | |
=============== | |
- Defined enough stories, did not suffer from story starvation | |
- Mix of uTu stories and uTu tasks | |
- uTu meetings have pleasingly moved to concrete tasks, rather than broad understanding | |
- Productive technical discussions w.r.t. implementation choices | |
- Guidance from outside team (Terry) | |
- More than average pairing | |
- Pairing sessions were short+productive |
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 Went Well? | |
=============== | |
- uTu pace picking up, lots of stories (a more responsive Marcus) | |
- Plenty of stories; no story starvation (mostly... Garett was looking for stuff a bit on Thursday) | |
- John had a review | |
- Nice to do some "pseudo-greenfield" work in "our" component; decided on own style/convention | |
- Cross-team collabs w/ Broundon, Terry | |
- Paired on some stories w/ each other (internally to JARVIS) | |
- David's Capistrano PR was merged to Capistrano master 🎉 |
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
03:32 bundler:install | |
01 bundle install --path /data/apps/ror/pws/shared/bundle --without development test --deployment --quiet --retry 5 | |
✔ 01 [email protected] 18.507s | |
✔ 01 [email protected] 19.048s | |
✔ 01 [email protected] 19.593s | |
03:52 react_on_rails:compile_environment | |
01 cd /data/apps/ror/pws/releases/20171026120927; ./components/do.sh 'test ! -f package.json || yarn check --integrity 2> /dev/null || yarn install' | |
01 ===> apple_gsx_client | |
01 ===> aurora_client | |
01 ===> call_queues |
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 Went Well This Week | |
======================== | |
- Healthy point total despite missing 1 people-day, plus have stories ready to ship on Monday | |
- Local deploys should be faster - always nice to help the whole team be more productive | |
- Owe a shout-out to Diego for Nitro Search sortable scopes; made the Project Score story much easier | |
- Going story-by-story in retro avoided "overlooked story syndrome" | |
- John appreciated detailed TB stories | |
- TB stories shipped in reasonable time; hasn't always been the case |
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 Went Well | |
============== | |
- Productive week (matched existing velocity of 32) almost entirely thanks to G and D, despite being at 90% power | |
- Good uTu week; finished all estimated stories for the sprint | |
- uTu is nice (easy to troubleshoot with, a good partner) | |
- Got helpful PR comments from outside team (Terry) | |
What Didn't Go Well | |
=================== |
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 Went Well This Week? | |
========================= | |
- Lots of points! | |
- Why? | |
- Star performance from Garett | |
- Had some carryover stories that finally shipped | |
- Many stories were in areas where the team was already comfortable & confident | |
- Groomed stories frequently | |
- Benefitted greatly from Tim's guidance with regards to uTu + project flow |
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
~/Projects/data_analysis (project_score_analysis!) (2.4.2) ± make build | |
docker-compose build | |
Building notebooks | |
Step 1/9 : FROM jupyter/datascience-notebook | |
latest: Pulling from jupyter/datascience-notebook | |
e0a742c2abfd: Pulling fs layer | |
486cb8339a27: Pulling fs layer | |
dc6f0d824617: Pull complete | |
4f7a5649a30e: Pull complete |