This is a reminder that Jared Richardson is our speaker next month.
If there's a particular talk you're interested in let us know.
He wrote a book called "Ship It!" that is published under the Pragmatic label which talks about how to ship software.
I have the book and think it's pretty comprehensive.
I've been to some of his talks and really enjoyed it.
I'm sending this message to both JUG groups - just reply directly to me at greg.ostravich at
gmail.com
Here are some of his talks:
Presentations by Jared Richardson
Technical debt has long been recognized in technical circles for years,
but convincing your manager to budget time to repay "technical debt"
has always been problematic. Let's couch the term technical debt
concept in language more familiar to our managers: credit card debt.
Agile practices are popular because they work, but getting people to take that first step can be tricky.
There are a number of great techniques you can use across technologies
and projects. Come hear some of my favorites and contribute a few of
your own. We'll discuss topics from DRY to creating a zone defense for
your product.
Continuous Integration is increasingly recognized as a vital practice
in an Agile software shop. Traditionally it's been difficult to set up
and administer. Today, that's no longer the case.
A great team builds great software, but how do you build a great team?
Creating and maintaining a solid automated test suite is critical to an
Agile strategy, but often we're just told to "Do it." In this talk
we'll look at several pragmatic strategies for creating and building
your suite.
Most people fear public speaking more than death, but you don't have to
let it handicap you or your career. Learn solid techniques for managing
yourself, your content, and your audience.
Has your career been a random product of your manager's whims or
company's needs? Never rely on your company to keep your skills current
and marketable. Take control of your own career with a proven strategy.
Subversion is a free source code management system that's very powerful.
How do you keep a team scattered across time zones in sync?
Software projects fail over and over for many of the same reasons.
We'll look at some of the more avoidable problems and some solid ways
to fix them, or avoid them in the first place.
An agile team is first and foremost "a team". When that gets lost in
the rush to get a product out the door, the people suffer as well as
the products. It's bad for the company, but even worse for the team
members. We'll learn how to defuse some of the more common problems
you'll run into on dysfunctional teams.
An overview of the Agile software approach from the book Ship It! A
Practical Guide to Successful Software Projects.
Having problems with message search?
Offline 
Send Email