Skip to main content

Recent Reads: Leadership, Use Cases

Here are a few articles I’ve read recently that I though were worth sharing. The first two are by Kate Mastudaira, who’s ACM articles on people management are always well written and often seem to be consistent with things I’ve learned from reading and speaking with Jerry Weinberg. The third is from the person many most associate with Use Cases, Ivar Jacobson, about an update to Use Cases that seems to align more closely with agile methods.

Delegation as Art by Kate Matsudaira

A good discussion about what it means to be a “senior engineer.” in particular, “senior” implies leadership, which implies teaching. This quote hits the highlights, but the article is still worth a read:

Being a senior engineer means having strong technical skills, the ability to communicate well and navigate ambiguous situations, and most important of all, the ability to grow and lead other people.

Nine Things I Didn't Know I Would Learn Being an Engineer Manager by Kate Matsudaira

This article explains why being a good engineering manager is not all about technical skill, but also (more so?) about communicating, coordinating, and listening. Kate Mats also shares links to resources about techniques to use to improve your non-technical skills. Whether you agree or not with what she says, her points can get you thinking.

Use Case 2.0 by Ivar Jacobson

This article goes into an updated view of use cases, adopting a few ideas from agile planning. Since Use Cases are the canonical way people like to talk about requirements on traditional projects, knowing about this might be a good way to bridge the gap between “waterfall” and “agile” projects.

Comments

Popular posts from this blog

Continuous Integration of Python Code with Unit Tests and Maven

My main development language is Java, but I also some work in Python for deployment and related tools. Being a big fan of unit testing I write unit tests in Python using PyUnit. Being a big fan of Maven and Continuous Integration, I really want the  Python unit tests to run as part of the build. I wanted to have a solution that met the following criteria:
Used commonly available pluginsKeep the maven structure of test and src files in the appropriate directories.Have the tests run in the test phase and fail the build when the tests fail.
The simplest approach I came up with to do this was to use the Exec Maven Plugin by adding the following configuration to your (python) project's POM.

<plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <executions> <execution> <configuration> <executable>python</executable> <workingDirectory>src/test/python</workingDirect…

Displaying Build Numbers in Grails Apps

Being a fan of Continuous Delivery, identifiable builds, and Continuous Integration: I like to deploy web apps with a visible build number, or some other way of identifying the version. For example, having the build number on the login screen for example. In the Maven/Java world, this is straightforward. Or at least I know the idioms. I struggled with this a bit while working on a Grails app,  and wanted to share my solution. There may be other, better, solutions, but the ones I found approaches that didn't quite work they way that I'd hoped.

My requirements were:
To display a build number from my CI tool, where the number was passed in on the command line. In Bamboo, for example you might configure a grails build as
-Dbuild.number=${bamboo.buildNumber} warTo only change build artifacts and not any source files.To not misuse the app version, or change the names of any artifacts.To be simple and idiomatic.I realized that that Grails itself changes the application metadata (appl…

Motivation Visibility, and Unit Testing

I've always been interested in organizational patterns (such as those in Organizational Patterns of Agile Software Development). I've recently found myself thinking a lot about motivation. I'm now reading Drive: The Surprising Truth About What Motivates Us and just finished Rob Austin's book on performance measurement. Being the parent of a three year old, I'm finding more and more that "because I said so, and I'm right" isn't too effective at home. My interests in motivation are closely related to my interest in writing software effectively. Writing software is partially a technical problem about frameworks, coding, and the like, but the harder (and perhaps more interesting) problem is how to get a group of people working together towards a common goal. Agile practices, both technical and organizational, build a framework which makes having the right amount of collaboration and feedback possible. But there's a bootstrapping process: How do yo…