Speaking and Writing

I try to stay fairly active in the professional development community and try to write a paper or speak at a conference at least once a year.  This is a running list of all the papers, workshops, and presentations. I created it as a sort of CV but also because I thought it would be cool to see written down in one place all the various events and publications I've done.

In many cases I've posted slides or written about the paper, presentation, or workshop on this website. If there isn't a link or you just want more information, drop me a line and let's talk.

Presentations and Workshops


Panels


Publications


Interviews



Conference Committees

  • Agile 2013, 2014, 2015, 2016, Experience Reports, reviewer and shepherd
  • SATURN 2013, 2016, 2017,  Program Committee
  • SATURN 2014,  Technical Program Chair
  • SATURN 2015, Technical Program Co-Chair with George Fairbanks
  • ICSME Annual Workshop on Technical Debt 2014, 2015, 2016, Program Committee

Popular posts from this blog

Dealing with Constraints in Software Architecture Design

Image
Definition of constraint (n)Bing Dictionary con·straint[ kən stráynt ] limiting factor: something that limits freedom of actionstate of restriction: a state in which freedom of action is severely restrictedlack of spontaneity: a lack of warmth and spontaneity in somebody's manner or in the atmosphere on a particular occasion
In software architecture design, constraints come in two basic flavors - technical and business.  On most projects there are only a handful of constraints, but these constraints are a highly influential architectural driver.  Constraints, as the dictionary definition above indicates, are a limiting factor and severely restrict options for making design decisions.  They are also fixed design decisions that cannot be changed and must be satisfied.  You could think of constraints as the ultimate non-negotiable, "must have" requirement.  It is for this reason that architecture design constraints must be created and accepted with care.

Read more

Architectural Drivers: Building Blocks for Decision Making

Architectural drivers are formally defined as the set of requirements that have significant influence over your architecture.  In other words, there are some requirements that will help you decide which structures to pick for your system design and others that are less consequential in the context of software architecture.  This implies that it is extremely important to get the architectural drivers right early in a project, as architecture structures will become more difficult to change as the developed software becomes more realized.

Thinking about early requirements as "drivers" can also help you to create traceability from stakeholder concerns to specific architectural decisions made.  Having this traceability is great because it helps to promote important qualities in your team, such as agility.  With traceability you can make changes on purpose and with confidence as you understand the genesis for structural decisions.

What are Architectural Drivers? Architectural driv…
Read more

Managing Multiple Ruby Versions with uru on Windows

My undergraduate software engineering professor was awesome. Here's one bit of advice he shared during his course that really stuck with me over the years.
Pick a scripting language.  Any Scripting Language.  Learn to use it really, really well. Compiled programming languages obviously have a purpose, but lightweight, interpreted scripting languages are an important tool as well. An interpreted scripting language is the perfect choice for one off tests, tedious text manipulation, automated tasks, and simple tools. Scripts are easy to write, easy to share, and good enough to get the job done.

My prof used Perl and was a whiz at it. I eventually settled on Ruby as my scripting language of choice. While the core language works really well across different platforms, as a predominantly Windows user,  I find that Ruby sometimes runs into problems in odd situations. One thing that is particularly annoying is the lack of a Ruby version manager. Version managers are a great idea.  The…
Read more