StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
721080
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-04-06T11:44:02.480
FavoriteCount
0
LastActivityDate
2009-04-06T11:44:02.480
LastEditDate
LastEditorUserId
0
OwnerUserId
81278
ParentId
708775
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Agile Simple Design doesn't mean don't do ANY design/architecture up front. It means do the minimal design up front, so that you will not pay a horrible price for reasonable change requests. Scott Ambler talks about Change Cases - <a href="http://www.agilemodeling.com/artifacts/changeCase.htm" rel="nofollow noreferrer">http://www.agilemodeling.com/artifacts/changeCase.htm</a> James Coplien talks about Agile Architecture - <a href="http://www.infoq.com/presentations/Agile-Architecture-Is-Not-Fragile-Architecture-James-Coplien-Kevlin-Henney" rel="nofollow noreferrer">http://www.infoq.com/presentations/Agile-Architecture-Is-Not-Fragile-Architecture-James-Coplien-Kevlin-Henney</a> <a href="http://blog.jaoo.dk/2009/03/04/handling-architecture-in-the-agile-world/" rel="nofollow noreferrer">http://blog.jaoo.dk/2009/03/04/handling-architecture-in-the-agile-world/</a> The art/craft in all of this is in how to slice the architecture in a way that allows: <ul> <li>relatively fast convergence on overall architecture/infrastructure - on the order of days per months of estimated development time. </li> <li>developing "just enough" architecture/infrastructure per each feature/requirement</li> <li>doing the right balance of preparations for the future compared to focus on the features of today. </li> </ul> Its important that your Product Owner is aware of all of this balancing act as well, and you work collaboratively. He should understand that if you disregard all thinking for the future, each change will be very costly. There is a price to be paid for flexibility. Its btw very similar to investment in QA and test automation. You pay something now, that will pay off only after X times you test the code. if the code never changes it was a waste of effort. but everyone knows that most code changes...
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to educate a development manager about the difficulties of software design?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USYuval
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to educate a development manager about the difficulties of software design?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.