Bill Schneider
Sr. Principal Software Engineer
Advisory Board Company
location_on United States
Member since 5 years
Share
Bill Schneider
Specialises In (based on submitted proposals)
I've been at the Advisory Board Company for the last 9 years, building applications to help hospitals save on surgical costs while maintaining high quality of care. When I started, the firm had virtually no software development experience. As a technical thought leader, I have led several teams through the engineering side of an Agile transformation, with predictable, high-quality releases. I have helped establish a culture of refactoring, writing clean code, and testing. Although my hands-on experience is primarily Java, Javascript and Oracle, I am a pragmatic polyglot and believe in using the right tools for the job, and led a number of transitions to adopt new or different technologies.
-
keyboard_arrow_down
Git with the Flow: lessons learned from adopting Gitflow one step at a time
45 Mins
Talk
Beginner
Source control is an unglamorous but important part to an effective agile team. Distributed SCM like Git is (still!) new and unfamiliar territory for some teams, yet it can be the gateway to new modes of collaboration and workflow.
At this talk I will share my experience of adopting Git, and Stash, on my teams, one small step at a time. As the teams got comfortable and built up their confidence, they made their way from a centralized Subversion-like workflow, to full-blown Gitflow, in just a few months.
So why does a talk about SCM belong at an Agile conference? The answer is: this is not about a particular SCM tool. It's about people, collaboration and the learning process. It's about how SCM tools enabled us to work together as a team more effectively, with better transparency and discipline.
-
-
keyboard_arrow_down
Functional testing is for everyone! Busting myths about unit vs. functional testing
45 Mins
Talk
Intermediate
I will share how I led a team from believing that end-to-end functional (browser) tests were "other" or "someone else's problem", to engaging the whole team in writing these kinds of tests. By the end of the transition these tests were on almost equal footing as unit tests.
Along the way, I had to challenge conventional wisdom and dogma about unit tests - that unit tests are easier than functional tests, that unit tests are less brittle, or that unit tests are unconditionally useful.
This talk is more about changing people's mindset than about specific tools, although I found that having the right tools made the mindset shift possible.
-
-
No more submissions exist.
