# amplifieddevelopment.net > AI-optimized mirror of amplifieddevelopment.net containing 23 pages totalling 6,199 words of clean markdown content, structured data, and semantic HTML. Original source: https://amplifieddevelopment.net/. Last updated: 2026-06-15T03:42:16.185Z. Each page is available as HTML (with JSON-LD structured data) and Markdown (text-only, ideal for LLMs and RAG). ## Homepage - [The Mission](/content/site-root.html) (526 words) ## Articles & Blog Posts - [blog/2017-01-19/index.html](/content/blog/2017-01-19/index.html) (1 words) - [blog/index.html](/content/blog/index.html) (1 words) - [Deployment](/content/blog/2017-01-20/index.html): Yesterday's exploration brought us to the point where we had a working .NET Core feature integrated with unit and functional tests.  Today, we will focus on wrapping that feature up as an AWS Lambda and automatically deploying it. Our Lambda project (QueueMover.Lambda) was create, (650 words) - [Extreme Remote: Product Management - Online conversations — Amplified Development](/content/blog/2016-06-30/index.html): Normal 0 false false false EN-US JA X-NONE , (111 words) - [Ignore attributes](/content/blog/2017/1/24/lessons-learned-about-upgrading-from-nunit-2x-to-3x.html): Our current project has been spurred to move from NUnit version 2.6.4 to version 3.6 for .NET Core compatibility.  Along the way we learned about some key differences, some minor, some more interesting: Ignore attributes With NUnit 3.x, [Ignore] attributes must specify a reason. So, e, (289 words) - [Extreme Remote: Code Ownership - Feature toggles — Amplified Development](/content/blog/2016-07-25/index.html): In the previous post, I recommended short-lived feature branches to help keep in-house and remote developers working effectively on the same code modules.  This ensures that your in-house developers maintain genuine code ownership at all times. But, short-lived feature branches cause incom, (327 words) - [Writing for business users only](/content/blog/2016-07-06/index.html): Normal 0 false false false EN-US JA X-NONE , (463 words) - [Extreme Remote: Code Ownership - Everybody in the same code pool — Amplified Development](/content/blog/2016-07-04/index.html): When you have a team comprised of in-house and remote members, it is very tempting to organize the work so that each group works on separate sections of the project.  This helps each group work together effectively, have easy communication, etc.  Yet, there is a painful reality to , (404 words) - [Feature Branches and Code Quality](/content/blog/2016/08-08/index.html): The current series of posts have been recommending short-lived feature branches to help in-house and remote developers to work on the same code modules.  Feature toggles and automated tests provide important protections while working in this manner. Code reviews provide another key protect, (193 words) - [Delightful Requirements: Scenario Names - Read well when collapsed — Amplified Development](/content/blog/2016/7/13/delightful-requirements-scenario-names-read-well-when-collapsed.html): When I first began writing Gherkin scenarios, I tended to use scenario names as labels.  For example, I almost always started with:, (319 words) - [The Importance of Examples in Requirements](/content/blog/2016-07-07/index.html): At Amplified Development, we are strong proponents of using examples liberally in your specifications.  Examples just make requirements better. The main objection to examples is that they make test implementation more difficult.  This is true; but, the level of difficulty may depe, (266 words) - [Long-lived feature branches](/content/blog/2016-07-18/index.html): We have been discussing the advantages of a 'relay race' style of development.  This approach has in-house and remote developers completing granular requirements and tasks each day, and their counterpart picking up progress as their work day begins. Success with this approach requires arti, (388 words) - [Key Meetings for Product Owners in the Iteration Cycle](/content/blog/2016-06-29/index.html): Normal 0 false false false EN-US JA X-NONE , (265 words) - [Extreme Remote = Off-shore? — Amplified Development](/content/blog/2016-06-24/index.html): In the previous post, I defined Extreme Remote as "having team members so far away that regular overlapping work periods are very difficult to maintain".  And, I referred to countries such as Pakistan and India as sources of technical talent.  So, isn't that just what we , (191 words) - [Code Ownership in Off-Shore Development](/content/blog/2016-07-01/index.html): Normal 0 false false false EN-US JA X-NONE , (228 words) - [The Relay Race Style of Development](/content/blog/2016-08-15/index.html): We have proposed a 'relay race' style of development where in-house and remote team members hand off active development on code modules as their work days start and end with the rotation of the earth.  This manner of work necessitates very granular requirements so that individual requiremen, (342 words) - [Requirements](/content/blog/2016-07-05/index.html): (Note: The series on Extreme Remote will continue as a weekly post next Monday.  At this time, we are launching a second series of posts with the theme:   Delightful Requirements ) Requirements.  You're gonna have 'em.  Whether they are a hallway conversation wit, (400 words) - [Extreme Remote: Code Ownership - Automated tests — Amplified Development](/content/blog/2016-08-01/index.html): When you work with short-lived feature branches, feature toggles help you sleep at night by quarantining new code for partially implemented features.  Yet, there may still be a worry that somehow there was some lapse in feature toggle implementation and side-effects have crept in. Automate, (197 words) - [The Importance of Meaningful Scenario Names](/content/blog/2016/7/12/delightful-requirements-scenario-name-write-for-the-business-stakeholder.html): In an earlier post, I promoted the idea that Gherkin scenarios should find a sweet spot  between the interests of business stakeholders and test implementers.  In this post, I want you to forget all that and ignore the test implementer and focus only on the business stakeholder..., (186 words) - [Importance of Writing Good Gherkin Scenarios](/content/blog/2016-07-08/index.html): One of the most common mistakes made when adopting Gherkin style requirements is to simply port existing test scripts into the Gherkin syntax.  The result is a scenario detailing every mouse click and value entered on the way to the behavior being tested.  It is extremely hard for , (165 words) - [Extreme Remote: Product Management - Daily Meetings — Amplified Development](/content/blog/2016-06-28/index.html): Normal 0 false false false EN-US JA X-NONE , (150 words) - [sitemap-xml.html](/content/sitemap-xml.html) (137 words) ## Resources - [Full Page Index](/index.html): Browse all cached pages with rich metadata - [About This Cache](/content/about.html): Methodology, technical details, and usage guidelines - [XML Sitemap](/sitemap.xml): Machine-readable sitemap for crawler discovery - [Robots.txt](/robots.txt): Crawler directives