Buy Amikacin Without Prescription » We Always Have The Cheapest Offers In Our Online-Drugstore

Christian Gruber — Fri, 23 Jan 2009 14:54:24 +0000

Buy amaryl without prescription, The question of "expected velocity" and long-term planning has come up at more than one client. A recent client conversation got me thinking, however, questioning how to interpret velocity when estimating and plotting a roadmap based on a current backlog of features, buy amaryl without prescription. Assume, for a moment, Generic amaryl cheap, a backlog of story-pointed features, and 10 good iterations (consistent team, no odd occurrences that would affect velocity). Mathematically average velocity (well, amaryl price, a mean really) is a 50/50 proposition for any subsequent iteration. Some organizations don't find this level of confidence acceptable. What velocity should be reported as expected for iteration/sprint planning and roadmap forecasting, and how should it be used?

Context

Interpreting velocity, before anything else, requires some context, buy amaryl without prescription. Amaryl no rx, An agile organization that sees estimates as hypothetical might find this article is of less use. In fact, a good question is whether estimation is even a value-added activity. For this post assume an organization that sees strong value in estimation and planning.

Culture

The biggest piece of context is to know the organizational culture, order amaryl on internet. This is important in two respects, and both of these cultural factors are important because they impact how Velocity is understood within the organization.

What is Failure?

First is the meaning of failure in the organization. Buy amaryl without prescription, Is failure to deliver what was committed to by the planned date considered a failure of the team, or is it simply a fact to be understood and accounted for in future planning. Buy amaryl from us, Even in Agile organizations, the former is often true and a hard habit to break. If not delivering to expectations is considered failure and has negative consequences, then that means that estimation is being treated not as estimation, overnight amaryl, but as prediction and contract. Velocity is therefore a commitment, Lowest price amaryl, and should therefore be used conservatively.

Consistency or Speed?

The second item to know is whether consistency and predictability of delivery is of a higher strategic value than the actual rate of delivery. This is often un-stated. Usually people want fast and consistent delivery, buy amaryl without prescription. The truth is that you can get consistent, or fast software development, cheap price amaryl, or a balance between the two. Lack of trust is usually a strong motivation to encourage consistency over speed, Find cheap amaryl online, or a history of quality problems, etc. In this case, as well, amaryl in uk, Velocity is more of a boundary than an indicator.

Emotional Loading in Estimation (or why not Low-ball?)

If estimation is seen as binding, contractual, Amaryl pharmacy online, or limiting, then additional emotions get overloaded. Trust, promise, drug amaryl, and betrayal are words used in such organizational cultures. Buy amaryl without prescription, Distrust is usually a strong factor, especially between silos (business vs. technology, Purchase amaryl no rx, company vs. project management vs. customer, etc.), cheap amaryl in canada. So when people are asked to give estimates, even using agile-friendly mechanisms such as story points, Cheap amaryl, there is usually a process of cementing that estimate into a part of an accountability model, so estimates start to get conservative. People are then accused of low-balling, others are accused of irrational expectations.., buy amaryl without prescription. we've all seen this. The language clearly becomes one of contention and blame, amaryl buy drug. Even the term low-balling is often an outright pejorative term for estimating too conservatively.

This doesn't happen only in agile environments, Amaryl overnight delivery, and project managers in traditional PMBOK frameworks have long factored risk into "contingency budgets". Buy amaryl without prescription, Interestingly, however, if a Project Manager were to factor risk into the task estimates, they'd be "low-balling capacity," yet if they were to factor it out and layer it on top of the project work, it's "contingency budgeting" (At least in a few experiences I've had). Either way, someone's adding a factor for uncertainty, based on the need to predict conservatively or liberally or somewhere in between.

That's the point of the article: how can Agile projects use velocity to estimate as conservatively (or liberally) as is appropriate?

An average is a 50% chance to succeed (or fail)

Velocity is not a constant, find discount amaryl. It's a set of instantaneous values on a curve, with instances being iterations. Amaryl prescription, That means that it varies, and is therefore only meaningful statistically. So how do you reasonably use velocity statistically, and improve confidence, amaryl vendors. One way is to stop delivering against "average" velocity, buy amaryl without prescription.

A lot of coaches use average velocity over the previous N iterations. This is not helpful for all sorts of reasons, Cheap amaryl no rx, if estimation is a commitment. By definition, average (well, actually a mean, amaryl buy online, but they're close) is a 50/50 proposition. If you report the average team velocity (assuming it's accurate), Buy amaryl lowest price, then about half the time the team will be under and about half the time the team will be over, statistically. Buy amaryl without prescription, So basically an average is a crap shoot, when taken in any given instance. It's can only be good in the long run. For this to work, the long-haul has to include permission to fail and a lot of trust, amaryl in us. Teams need to be able to go miss dates but will sometimes exceed dates and it should all wash out in the end. In organizations such as I'm describing, Amaryl free sample, that trust isn't there, so. Additionally, if the language of commitment is around meeting instantaneous iteration commitments (as opposed to delivering high-quality customer value as quickly as is sustain-ably possible) then you aren't playing the long-game, online pharmacy amaryl, you're playing a very short-game.

Simulate Velocity, not work

In a PMI training course I took when I was at Sun Microsystems, Order amaryl without prescription, we were nicely informed that two point estimates of tasks are a perfect way to fail half the time, per the above logic. One point estimates are just idiotic, buy amaryl without prescription. Three point estimates were better. We simulated with a monte-carlo algorithm and found a curve and a distribution, cheapest amaryl prices, and then determined a confidence level yadda yadda. Well, Amaryl cheap, we're trying to avoid wasting a lot of time estimating up-front, but one way to start representing velocity properly is to do the same kind of statistical modelling done in traditional product management, only simulate velocity, not work items.

In this approach, buy discount amaryl online, you take the last N iterations (say 10). Determine the maximum velocity (optimistic) and the minimum velocity (pessimistic), Lowest price for amaryl, and then the mode (the velocity value that seems to occur most frequently). Then you do monte-carlo simulation Buy amaryl without prescription, so you get a statistical pattern. Now, you actually can determine an answer based on confidence. If you want to be right with an 80% confidence, amaryl rx, you pick a velocity where 80% of the simulated runs were successful. (Note - there are a paucity of excel templates to do this math automatically, Buy generic amaryl, and often they are for sale. It would be nice to have a few functions with arbitrary distributions based on min-max-mode to help this along.)

It's not perfect, and it's a potentially huge amount of administrative overhead. Elsewhere I've referenced blogs that entirely oppose any estimation at all, but if you are gong to, then working statistically with simulation is the only way to take small sample numbers meaningful.

Commitment Velocity: Low-Ball as a policy.

Another approach, one perhaps controversial, but taught by some Scrum trainers is to pick the lowest historical delivered velocity, buy amaryl without prescription. This is a commitment-based approach, order amaryl overnight delivery, on the assumption that building trust around consistent delivery is critical to building sound relationships where product owners and teams can safely state their needs and get things done with a minimum of contractual behaviour. By taking the minimum, Find amaryl without prescription, you force a low-ball capacity, which means you can have high-confidence of success after a few iterations. You have, likely, amaryl pills, after a while, some spare time on your hands. Amaryl in australia, Teams can then choose to pull more work in (without adjusting their commitment velocity), work on "technical debt", improve their skills, etc, amaryl for order. Buy amaryl without prescription, A team could raise their commitment velocity in certain inflection points in the project. A new team member is added that provides a necessary skill not previously available, and after a few iterations the team is consistently hitting a higher number, Amaryl, but this is a careful process to ensure that they are committing, and if they don't make their new number, it goes down to what they got accomplished.

Indemnify teams' learning

An arguably healthier option, if you have built enough trust, is to simply indemnify a team from failing to meet the estimate. Since you're doing mathematics on actuals to generate an expected future number, everyone can acknowledge that past behaviour is no guarantee of future behaviour, and simply use it for capacity planning. In this case, estimation is actually estimation, not commitment or contract. The team is expected to be ahead sometimes, and behind sometimes. The upside of this is that a lot of extra time isn't spent playing with fictional numbers, buy amaryl without prescription. Teams are spending their efforts on delivery as quickly-yet-sustain-ably as they can, and the organization treats them as trusted professionals in this. The temptation to assume you can predict the future is seen as folly, and the estimates are used to guide overall direction, not to make outward customer commitments.

Don't be mindless

There may be other approaches, I'm sure. The agile community is certainly not short of people who love this topic and can talk for hours on "proper" estimation. The point of this post is merely to point out some options, and ask you to look at your organizational culture, team culture, customer culture, the meaning of terms like commitment, failure, success, consistency, speed, etc. Buy amaryl without prescription, As you understand the culture, balance consistency vs. speed, trust, and other factors to choose a method of estimation that meets your goals. Don't do estimation based on your own, internal cultural assumptions, as you may have developed or been taught techniques that are useful when and where they were taught, but may no longer be so. Or maybe they weren't so useful then either. Regardless, this because estimation cuts at the heart of the dialogue between producer and consumer, and establishes parameters for that discussion, it's critical that you think your choice through.

[Christian also blogs at http://www.geekinasuit.com/]

Buy Amikacin Without Prescription » We Always Have The Cheapest Offers In Our Online-Drugstore

Christian Gruber — Fri, 02 Jan 2009 20:31:31 +0000

Isráfíl Consulting Buy bactroban without prescription, is finally prepared for the first series of its Agile Software Engineering Practices training courses. Bactroban pill, This series is offered in partnership with Berteig Consulting who are graciously hosting the registration process. Their team has also helped greatly in shaping the presentation style and structure of the course, no prescription bactroban. Bactroban drug, The initial run will be in Ottawa, Toronto (Markham), cheap bactroban in usa, Bactroban online stores, and Kitchener/Waterloo.

Topics covered will include Test Driven Development (TDD), find cheap bactroban, Canadian pharmacy bactroban, testability, supportive infrastructure such as build and continuous integration, bactroban tablet, Buy cheap bactroban internet, team metrics, incremental design and evolutionary architecture, purchase bactroban online, Bactroban malaysia, dependency injection, and so much more, buy bactroban pills. (This course won't present the planning side of XP, but covers many other aspects common to XP projects) It makes a great complement for training in Agile Processes such as XP, Scrum, or OpenAgile, buy bactroban without prescription. Order bactroban from canada, The overview slide presentation is available for free download from the Isráfíl web site.

The courses are scheduled for:

2009-02-05: 2 Day Agile Software ENGINEERING Practices Training - Kichener/Waterloo, Ontario (15 Spots)

2009-02-12: 2 Day Agile Software ENGINEERING Practices Training - Markham/Toronto, order discount bactroban, Cost of bactroban, Ontario (15 Spots)

2009-02-19: 2 Day Agile Software ENGINEERING Practices Training - Ottawa, Ontario (15 Spots)

The course is $1250 CAD per student, buy cheapest bactroban online, Compare bactroban prices online, and participants receive a transferrable discount of $100 CAD for other training with Berteig Consulting as a part of our ongoing partnership. I initially prototyped this course in Ottawa this December, buy cheap bactroban online, Cheap bactroban without prescription, and am very excited to see this through in several locales. Class size is limited to 15, find no rx bactroban, Cheap bactroban overnight delivery, so we can keep the instruction style more involved. The above schedules are linked to Berteig Consulting's course system and have registration links at the bottom of the description, generic bactroban online. Cheap bactroban no prescription, Locations are TBD, but will be updated at the above links as soon as they're finalized.

A further series is planned for several US cities in March, purchase bactroban overnight delivery, Bactroban non prescription, and we'll be sure to announce them as well.

. Canadian bactroban. Sale bactroban. Cheap bactroban internet. Canada bactroban. Compare bactroban prices. Buy bactroban. Bactroban from india. Order cheap bactroban online. Fda approved bactroban. Cheap bactroban from uk. Cost bactroban. Cheapest bactroban online. Discount bactroban without prescription. Order discount bactroban online. Drug bactroban online purchase.

Buy Amikacin Without Prescription » We Always Have The Cheapest Offers In Our Online-Drugstore

Christian Gruber — Tue, 04 Nov 2008 23:21:15 +0000

I was vaguely annoyed to see this blog article Buy protonix without prescription, featured in JavaLobby's recent mailout. Not because Kevin Pang doesn't make some good points about the limits of code coverage, Fda approved protonix, but because his title is needlessly controversial. And, because JavaLobby is engaging in some agile-baiting by publishing it without some editorial restraint.

In asking the question, buy protonix on internet, "Is code coverage all that useful, Cheap protonix in usa, " he asserts at the beginning of his article that Test Driven Development (TDD) proponents "often tend to push code coverage as a useful metric for gauging how well tested an application is." This statement is true, but the remainder of the blog post takes apart code coverage as a valid "one true metric," a claim that TDD proponents don't make, cheap protonix from usa, except in Kevin's interpretation.

He further asserts that "100% code coverage has long been the ultimate goal of testing fanatics." This isn't true. Protonix without a prescription, High code coverage is a desired attribute of a well tested system, but the goal is to have a fully and sufficiently tested system. Code coverage is indicative, cheapest protonix online, but not proof, Buy cheapest protonix on line, of a well-tested system. How do I mean that, buy protonix without prescription. Any system whose authors have taken the time to sufficiently test it such that it gets > 95% code coverage is likely (in my experience) thinking through how to test their system in order to fully express its happy paths, edge cases, find discount protonix online, etc. Protonix no prescription, However, the code coverage here is a symptom, not a cause, best price protonix, of a well-tested system. Buy protonix in us, And the metric can be gamed. Actually, when imposed as a management quality criterion, purchase protonix overnight delivery, it usually is gamed. Buy protonix without prescription, Good metrics should confirm a result obtained by other means, or provide leading indicators. Protonix rx, Few numeric measurements are subtle enough to really drive system development.

Having said that, I have used code-coverage in this way, but in context, low price protonix, as I'll mention later in this post.

Kevin provides example code similar to the following:

String foo(boolean condition) {    if (condition)        return "true";    else        return "false";}

... Protonix tablets, and talks about how if the unit tests are only testing the true path, then this is only working on 50% coverage. Good so far, buy protonix from canada. But then he goes on to express that "code coverage only tells us what was executed by our unit tests, Protonix sale, not what executed correctly." He is carefully telling us that a unit test executing a line doesn't guarantee that the line is working as intended. Um.., buy protonix without prescription. that's obvious. And if the tests didn't pass correctly, protonix order, then the line should not be considered covered. Buy protonix once daily, It seems there are some unclear assumptions on how testing needs to work, so let me get some assertions out of the way...

Code coverage is only meaningful in the context of well-written tests. It doesn't save you from crappy tests.

Code coverage should only be measured on a line/branch if the covering tests are passing.

Code coverage suggests insufficiency, protonix cheap price, but doesn't guarantee sufficiency.

Test-driven code will likely have the symptom of nearly perfect coverage.

Test-driven code will be sufficiently tested, Protonix overnight shipping, because the author wrote all the tests that form, in full, the requirements/spec of that code.

Perfectly covered code will not necessarily be sufficiently tested.

What I'm driving at is that Kevin is arguing against something entirely different than that which TDD proponents argue, buy protonix cheap. Buy protonix without prescription, He's arguing against a common misunderstanding of how TDD works. On point 1 he and I are in agreement. Best price for protonix, Many of his commentators mention #3 (and he states it in various ways himself). His description of what code coverage doesn't give you is absurd when you take #2 into account (we assume that a line of covered code is only covered if the covering test is passing). But most importantly - "TDD proponents" would, order discount protonix online, in my experience, Compare protonix prices online, find this whole line of explanation rather irrelevant, as it is an argument against code-coverage as a single metric for code quality, and they would attempt to achieve code quality through thoroughness of testing by driving the development through tests, protonix in us. TDD is a design methodology, not a testing methodology, buy protonix without prescription. You just get tests as side-effect artifacts of the approach. Protonix alternative, Useful in their own right. Sure, but it's only sort of the point, order discount protonix. It isn't just writing the tests-first.

In other words - TDD implies high or perfect coverage. But the inverse is not necessarily true.

Buy protonix without prescription, How do you achieve thoroughness by driving your development with tests. Buy protonix online cheap, You imagine the functionality you need next (your next increment of useful change), and you write or modify your tests to "require" the new piece of functionality. They you write it, buy protonix pills, then you go green. Drug protonix online purchase, Code coverage doesn't enter into it, because you should have near perfect coverage at all times by implication, because every new piece of functionality you develop is preceded by tests which test its main paths and error states, lowest price protonix, upper and lower bounds, Cheap protonix online, etc. Code coverage in this model is a great way to notice that you screwed up and missed something, but nothing else.

So, protonix professional, is code-coverage useful. Heck yeah, buy protonix without prescription. Protonix bangkok, I've used coverage to discover lots of waste in my system. I've removed whole sets of APIs that were "just in case I need them" APIs, because they become rote (lots of accessors/mutators that are not called in normal operations), cheap protonix pill. Is code coverage the only way I would find them. Buy protonix on line, No. Buy protonix without prescription, If I'm dealing with a system that wasn't driven with tests, or was poorly tested in general, I may use coverage as a quick health meter, but probably not. Going from zero to 90% on legacy code is likely to be less valuable than just re-writing whole subsystems using TDD... and often more expensive.

Regardless, protonix buy online, while Kevin is formally asking "is code coverage useful?" he's really asking (rhetorically) is it reasonable to worship code coverage as the primary metric. Protonix vendors, But if no one's asserting the positive, why is he questioning it. He may be dealing with a lot of people with misunderstandings of how TDD works, buy protonix low price. He could be dealing with metrics bigots, buy protonix without prescription. He could be dealing with management-imposed-metrics initiatives which often fail. It might be a pet peeve or he's annoyed with TDD and this is a great way to do some agile-baiting of his own. I don't know him, so I can't say. His comments seem reasonable, so I assume no ill intent. But the answer to his rhetorical question is "yes, but in context." Not surprising, since most rhetorically asked questions are answerable in this fashion. Hopefully it's a bit clearer where it's useful (and where/how) it's not.

(This article is a cross-post from "Geek in a Suit")

Buy Amikacin Without Prescription » We Always Have The Cheapest Offers In Our Online-Drugstore

Christian Gruber — Sat, 02 Aug 2008 22:57:52 +0000

Buy zofran without prescription, This post is a little geeky and technical and product-related for AgileAdvice, and is a shameless self-promotion. Cheapest zofran prices, Nevertheless, since testability, zofran order, Zofran buy online, test-driven-development, and incremental design are non-exclusive sub-topics of Agile, zofran online stores, Order discount zofran, I though I'd report this here anyway.

Many developers use the Dependency Injection and Inversion of Control (IoC) patterns through such IoC containers as Spring, Hivemind, zofran online sales, Cheapest zofran online, Picocontainer, and others, zofran pharmacy. Find zofran without prescription, They have all sorts of benefits to testability, flexibility, no rx zofran, Order generic zofran, etc. that I won't repeat here, where to buy zofran, Zofran professional, but can be read about here, here, zofran overnight shipping, Order zofran, and here. A great summary of the history of "IoC" can be found here, zofran without prescription. J2ME developers, however, especially those on limited devices that use the CLDC configuration of J2ME, cannot use the substantial number of IoC/DI containers out there, because they nearly all rely on reflection, buy zofran without prescription. Zofran medication, These also often make use of APIs not present in the CLDC - APIs which could not easily be added. Lastly there's a tendency among developers of "embedded software" to be very suspicious of complexity.

In working out some examples of DI as part of a testability workshop at one of my clients, zofran vendors, Cheapest zofran price, I whipped up a quick DI container, and being the freak that I am, zofran in australia, Zofran sales, hardened it until it was suitable for production, because I hate half-finished products, zofran generic. Zofran online cheap, So allow me to introduce the Israfil Micro Container. (That is, order cheap zofran, Zofran buy drug, the Container from the Israfil Micro project). Buy zofran without prescription, As I mention in the docs, "FemtoContainer" just was too ridiculous, and this container is smaller than pico-container. The project is BSD licensed, buy zofran on internet, Low cost zofran, and hosted on googlecode, so source is freely available and there's an issue/feature tracker, zofran online without prescription, Zofran free delivery, yadda yadda.

Essentially I believe that people working on cellphones and set-top boxes shouldn't be constrained out of some basic software design approaches - you just have to bend the design approach to fit the environment. So hopefully this is of use to more than one of my clients, find cheap zofran. Cheap zofran no prescription, It currently supports an auto-wiring registration, delayed object creation (until first need), no rx zofran, Order zofran online, and forthcoming are some basic lifecycle support, and a few other nicities, cheap zofran from uk. Buy discount zofran online, It does not use reflection (you use a little adapter for object creation instead), and performs quicker than pico-container, buy cheapest zofran. Low, low overhead, buy zofran without prescription. Zofran internet, It's also less than 10 classes and interfaces (including the two classes in the util project). It's built with Maven2, zofran in australia, Cheap zofran from canada, so you can use it in any Maven2-built project with ease, but of course you can always also just download the jar (and the required util jar too), price of zofran. Enjoy...

P.S. There are a few other bits on googlecode that I'm working on in the micro-zone. Some minimalist backports of some of java.lang.concurrency (just the locks), as well as some of the java.util.Collections stuff. Not finished, but also part of the googlecode project.

Buy Amikacin Without Prescription » We Always Have The Cheapest Offers In Our Online-Drugstore

Christian Gruber — Wed, 14 May 2008 18:39:03 +0000

This was actually cribbed from a Bruce Schneier blog post about security...

Buy amikacin without prescription, Security engineers see the world differently than other engineers. Amikacin india, Instead of focusing on how systems work, they focus on how systems fail, amikacin in malaysia, Buy amikacin low price, how they can be made to fail, and how to prevent--or protect against--those failures, purchase amikacin no rx. Amikacin overnight delivery, Most software vulnerabilities don't ever appear in normal operations, only when an attacker deliberately exploits them, get amikacin. Cheap price amikacin, So security engineers need to think like attackers.People without the mindset sometimes think they can design security products, but they can't, buy amikacin generic. Amikacin malaysia, And you see the results all over society--in snake-oil cryptography, software, buy amikacin pills, Cheap amikacin, Internet protocols, voting machines, amikacin vendors, Amikacin alternative, and fare card and other payment systems. Many of these systems had someone in charge of "security" on their teams, but it wasn't someone who thought like an attacker.Â Â

There's an interesting parallel between this statement and how most software quality is handled, buy amikacin without prescription. Quality and Security are similar, buy amikacin internet. Amikacin for sale, In fact, I see security as a very specific subset of quality-mindedness, order amikacin from canada. Amikacin cheapest price, Certainly both require the same mindset to ensure - rather than thinking merely "how will this work", a quality-focused person will also, cheapest amikacin prices, Amikacin online cheap, or perhaps alternately think: "how might this be breakable". From this simple change in thinking flows several important approaches

Constraint-based thinking (as opposed to solution based thinking): allows an architect/developer to conceive of the set of possible solutions, buy amikacin no rx, Amikacin for order, rather than an enumeration of solutions. Buy amikacin without prescription, By looking at constraints, a developer implements the lean principle of deciding as late as possible, with as full information as possible.
Test-First: As one thinks of how it might break, scenarios emerge that can form the basis of test cases. These cases form a sort of executable acceptance criteria
Lateral Thinking: The constraint+test approach starts to get people into a very different mode, buy amikacin from us, Buy amikacin no prescription required, where vastly different kinds of solutions show up. The creative exercise of trying to break something provides insights that can change the whole approach of the system.

Â Schneier goes on to ponderÂ

This mindset is difficult to teach, amikacin pharmacy, Cheap amikacin internet, and may be something you're born with or not. But in order to train people possessing the mindset, lowest price amikacin, Amikacin without rx, they need to search for and find security vulnerabilities--again and again and again. And this is true regardless of the domain, amikacin tablet. Good cryptographers discover vulnerabilities in others' algorithms and protocols, buy amikacin without prescription. Amikacin price, Good software security experts find vulnerabilities in others' code. Good airport security designers figure out new ways to subvert airport security, overnight amikacin. Best price amikacin, And so on.Â Â

Â Here again - I think it's possible to help people get a mind-set about quality, but some do seem to have a knack, cheapest amikacin online. Compare amikacin prices online, It's important to have some of these people on your teams, as they'll disturb the waters and identify potential failure modes, purchase amikacin overnight delivery. Buy amikacin without prescription, These are going to be the ones who want to "mistake proof" (to borrow Toyota's phrase) the system by writing more unit tests and other executable proofs of the system. Cheap amikacin pill, But most importantly (and I can personally testify to this) it is critical that people just write more tests. It is a learned skill to start to think of "how might this fail" until it becomes a background mental thread, amikacin without a prescription, Amikacin buy drug, always popping up risk models.A related concept is Demmings' "systems-thinking", which, generic amikacin online, Amikacin, applied to software quality, causes one to start looking at whole ecosystems of error states, amikacin from india. This is when fearless re-factoring starts to pay off, because the elimination of duplication allows one to catch classes of error in fewer and fewer locations, where they're easier to fix. There are many and multifarious spin-off effects of this inverted questioning and the mindset it generates. Try it yourself, buy amikacin without prescription. When you're writing code, ask yourself how you might break it. What inputs, external state, etc. might cause it to fail, crash, or behave in odd ways. This starts to show you where you might have state leaking into the wild, or side-effects from excessively complex interactions in your code. So quality focus can start to improve not only the external perception of your product, but also its fitness to new requirements by making it more resilient and less brittle. Cleaner interactions and less duplication allow for much faster implementation of new features.I could go on, but I just wanted to convey this sense of "attitude" or "mindset," over mere technique. Technique can help you get to a certain level, but you have to let it "click", and the powerful questions can sometimes help.