wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
echo 'deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main' | sudo tee /etc/apt/sources.list.d/google-chrome.list
sudo apt-get update
sudo apt-get install google-chrome-stable
Kevin Pefianco Thomas pefianco
pefianco
/ demofivetwentytwo.markdown
Last active
May 22, 2017 14:27
-
3 month solo maximum
-
mid1s and mid2s don't go solo on first engagement
-
no Mid 1 solos, not for a day
-
no solo first engagements
-
no one gets two solo assignments in a row of 2 months or more
Stride Core Values
Humility
- Admit that you might be wrong
- Admit what you don’t know
- Make the team’s success your success
- Bring your pair along with you and double check your assumptions when you can’t
- Bring the team along with you, solutions with team buy in are more valuable than going rogue, even when you’re right
- Listen to feedback and take ownership of action items
pefianco
/ stride_consulting_pillars.markdown
Last active
September 20, 2016 22:30
Stride Consulting Pillars
I've been thinking about our company direction and what that means to us as consultants. I appreciate the Stride Core Values and I believe in all of them. However I feel like they leave us a bit rudderless because they are values that no one from any consulting company would object to. So I made a list of practices that I see at Stride that exhibit some of the Core Values.
I think it is commendable that we have been so flexible and focused on delivering client value. However I'd also like us to agree upon a set of practices as consultants. Not all practices will be possible at every client but we need a baseline to begin to evaluate potential clients and ongoing engagements in the interest of improving consultant growth and happiness.
I came up with four consulting pillars, core practices that we agree on that are are not implied by our core values. I'd like us to have a common page to start on in our practice as consultants.
pefianco
/ TestDrivenDevelopment.markdown
Last active
August 12, 2016 08:06
A pattern for test driving a new application unit
- Write unit tests
- Think in terms of interfaces, inputs and outputs
- Red-green every test every time to ensure that the test is correct and implementation is correct
- Test one thing at a time
- Think of edge cases, unit tests only test the things that you think of
- Remember that test driving your application design in the long run is the most valuable part of test driven development
- Create the test file first