Sign In
Progressive Development
Zany Adventures in Software Engineering with Maven and Motley
Tags
About
agile
assertions
build
change
checklists
code comments
code coverage
code reviews
debugger
debugging
design
design by contract
estimation
general programming
HPT
interviewing
lean
legacy code
management
meetings
mock objects
people
personal vision
presentations
productivity
project management
quality
refactoring
root cause analysis
scrum
static analysis
supportability
TDD
teams
test
test-driven development
tools
unit testing
values
vision/mission
Browse by Tags
MSDN Blogs
>
Progressive Development
>
All Tags
>
design
Tagged Content List
Blog Post:
Motley says: "Developing international software is really, really hard. We need a brand new version."
James Waletzky
Summary Motley: Developing international software is really, really hard. We need brand new binaries to ship in other languages. Maven: Follow these tips when developing for international markets: design for one worldwide binary, ensure the software is globalized, do not build strings at...
on
16 Sep 2008
Blog Post:
Motley says: "Don't be anal about API design"
James Waletzky
Summary Motley: Don't be anal about Application Programming Interface (API) design. Maven: Good APIs are discoverable, consistent, simple, usable, hard to misuse, cohesive, lack side-effects, strongly typed, documented, has tests and samples, extensible when necessary, and are developed with...
on
12 Jun 2008
Blog Post:
Motley says: "I fear public speaking more than I fear dying!"
James Waletzky
Summary Motley: Speak at a conference?!? Are you insane?!? No public speaking for me! Maven: Speaking at a conference is a great way to build confidence and influence not just your company, but the industry. ______________________________ [Context: We'll continue with HPT Part 3...
on
11 Dec 2007
Blog Post:
Motley says: "Performance stinks, but I'll deal with it later"
James Waletzky
Summary Motley: I'll deal with performance issues when I have something to test. Then I'll run the profiler and just optimize the slow methods. Maven: Think about performance early in the development cycle. Set goals. Design for performance. Measure, measure, measure. Optimize the scenarios...
on
20 Nov 2007
Blog Post:
Motley says: "It's tough to make decisions involving multiple dimensions"
James Waletzky
Summary Motley: It's tough to make decisions in multiple dimensions, so just pick the most important one. Make the decision and move forward. No need to document the alternatives. Maven: Pugh Concept Selection (PCS) facilitates decision making where there are multiple alternatives and multiple...
on
4 Sep 2007
Blog Post:
Motley says: "My design is done when the schedule says it's done"
James Waletzky
Summary Motley: Design is done when that 3 day period I have to do design has expired. Maven: Design is done when your stakeholders are satisfied. Stakeholders include you, your peers, the test team, architect, future maintainers, your manager, and customer support. ______________________________...
on
31 Jul 2007
Blog Post:
Motley says: "A good design is all in the eye of the beholder" (Part 2)
James Waletzky
Summary Motley: Judging a design to be "good" is very subjective. Maven: "Good" designs satisfy fundamental design principles, like separating creation from usage, encapsulating variability, preferring containment to inheritance, and designing to interfaces. ______________________________...
on
24 Jul 2007
Blog Post:
Motley says: "A good design is all in the eye of the beholder" (Part 1)
James Waletzky
Summary Motley: Judging a design to be "good" is very subjective. Maven: "Good" designs satisfy fundamental design principles, like loose coupling, high cohesion, simplicity, and no undesirable redundancy. ______________________________ [Context: Motley is wondering how to really...
on
17 Jul 2007
Blog Post:
Motley says: "Refactoring means no more up-front design"
James Waletzky
Summary Motley: Refactoring keeps my design clean from the start, so no more up-front design! Maven: Up-front design is still necessary to achieve clarity on the overall approach (preventing rework later) and needs to be documented to allow others to review your thinking. ______________________________...
on
10 Jul 2007
Page 1 of 1 (9 items)