oleo-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

nappy unruly


From: Tim Polk
Subject: nappy unruly
Date: Thu, 12 Oct 2006 11:08:50 +0400
User-agent: Thunderbird 1.5.0.7 (Windows/20060909)


In the image below, I show a hypothetical ideal application with eight modules or layers, compared to a near-worst-case legacy application.
Often just writing such a test helps me find code-defects, and then I run the test to confirm it.
To make progress so quickly, we cut a lot of corners. Just like youcan take a TDD-based approach to developing application code, you can do thesame thing with your database schema. someone else appears to own the problem, and if you attempt to take it on you may be working outside your area of focus. To make progress so quickly, we cut a lot of corners. It doesn't have to be that way.
This year that process helped us make the development, and testing processes even more smooth and high-quality. It promotes detailed design. According to press reports, Fr. We only programmed for the best-case networking scenarios. It is also more an act of documentation than of verification.
It doesn't have to be that way.
No major surprises, no major fire-fighting.
chapter loops through its pages, tells each page to 'change margins'.
Decide on which layer a class belongs to, each time you create a class.
Just like youcan take a TDD-based approach to developing application code, you can do thesame thing with your database schema.
a manager in a different group may feel angry that you've identified what you think is a problem in his area. In other words, we already had a fairly sizable amount of technical debt and the application was only a week or two old. To make progress so quickly, we cut a lot of corners.
No major surprises, no major fire-fighting. I loathe that it has come to this, and can't imagine ever being proud of living in a country where torture, of any kind for any reason, is not only acceptable but legislatively protected. Third, it enables data professionals to work in an evolutionary manner, just like application programmers.
because they are worried that enumerated types could have unspecified sizes. We let bugs creep in. Some division of responsibilities larger than the individual classes. We didn't implement any tests. Holy shit, they are not only hilarious and consumate theatrical performers, but their musical talents are both incredibly high-level and widely ranging.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]