This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Kent is the creator of Extreme Programming, the groundbreaking Agile method that introduced evolutionary design, test-drivendevelopment, continuousintegration, and many other Agile practices to the world. It’s the basis of most of the material in The Art of Agile Development. About the Book Club.
Which books should you read as a software developer? Software Developers Should Read the Right Books. Great, you’re reading books! To have an even more significant impact on your career as a software craftsman, you should not just read; you should read the right books. Why This Book?
Reading these five books will give you a great start. Software Craftmanship Requires Reading the Right Books. Great, you’re reading books! To have an even more significant impact on your career as a software craftsman, you should not just read; you should read the right books. Why This Book? Trial and error?
ContinuousIntegration. Most software development efforts have a hidden delay between when the team says “we’re done” and when the software is actually ready to release. Continuousintegration is a better approach. Teams using continuousintegration keep everyone’s code working together and ready to release.
I recently found out about the bookDeveloperTesting – Building Quality Into Software by Alexander Tarlinder , and I immediately wanted to read it. Even though I am a developer at heart, I have always been interested in software testing (I even worked as a tester for two years). What ILiked The Most.
We use Extreme Programming as our model of how to develop software. They also love test-drivendevelopment, pairing, continuousintegration, and evolutionary design. They tend to be passionate, senior developers. This is what test-drivendevelopment is all about, and its an amazing way to work.
The Art of Agile Development (Book) - 2008. ContinuousIntegration on a Dollar a Day - 27 Feb, 2006. An easier, cheaper (and better) way to do continuousintegration. Testing Without Mocks: A Pattern Language - 27 Apr, 2018. How to use test-drivendevelopment without traditional test doubles.
The Art of Agile Development (Book) - 2008. ContinuousIntegration on a Dollar a Day - 27 Feb, 2006. An easier, cheaper (and better) way to do continuousintegration. Testing Without Mocks: A Pattern Language - 27 Apr, 2018. How to use test-drivendevelopment without traditional test doubles.
ContinuousIntegration. Finally, continuousintegration will prevent painful merge conflicts and keep everyone’s code in sync. Test-DrivenDevelopment. You can also use the unit tests as documentation and a safety net. Test-DrivenDevelopment. ContinuousIntegration.
Test-DrivenDevelopment. Technically, you can refactor at any time, but unless your IDE has provably-safe refactorings, it’s best to do it when you have a good suite of tests that are all passing. The definitive guide is Martin Fowler’s eponymous book, Refactoring: Improving the Design of Existing Code. Constantly.
Although this book is focused on individual Agile teams, many organizations have more than one development team, and they’re often dependent on each other to finish their work. Each coach will need resources, such as this book, to help them learn. The material in this book is completely compatible with LeSS.
Test-DrivenDevelopment. ContinuousIntegration. Programmers, use test-drivendevelopment to combine testing, coding, and designing. As you work, integrate with the rest of the team’s work by using continuousintegration. Test-DrivenDevelopment.
Among the experts, you may find: Mark Richards: hands-on software architect and co-author of the book “Fundamentals of Software Architecture” Neal Ford: Software Architect & Director at ThoughWorks. Nate co-authored the book Presentation Patterns with Neal Ford and Matthew McCullough.
Furthermore, Carlos highlighted the rising trend of bringing frontend development closer to native code through technologies like WebAssembly (Wasm) and web containers. Viktor Farcic We also had the great opportunity to interview Viktor Farcic, a Developer Advocate at Upbound, host of DevOps Toolkit, and cohost of the podcast DevOps Paradox.
ContinuousIntegration. Continuous Deployment. That doesn’t work for teams using continuousintegration and deployment. Other than short-lived development branches, they only have one branch: their integration branch. Test-DrivenDevelopment. Sign up here.
Test-DrivenDevelopment. ContinuousIntegration. Test-drivendevelopment encourages you to think about and improve your design at nearly every step. Test-drivendevelopment encourages you to think about and improve your design at nearly every step. Test-DrivenDevelopment.
ContinuousIntegration. Continuous Deployment. That doesn’t work for teams using continuousintegration and deployment. Other than short-lived development branches, they only have one branch: their integration branch. Test-DrivenDevelopment. Sign up here.
Most of these skills are out of the scope of this book. Until then, development on an Agile team looks similar to development on any other team. TestDrivenDevelopment. They use test-drivendevelopment to write tests, implement code, refactor, and incrementally design and architect the software.
I highlight two Agile approaches to technical success in this book. Programmers continuouslyintegrate their code, which enables the team to release their software whenever it makes the most business sense. In addition to the structure of development, XP includes advanced technical practices that lead to excellence.
Test-DrivenDevelopment. Inside the script, use a compiler or linter to tell you when you make syntax errors, and tests to tell you when you make semantic errors. ContinuousIntegration. Your deploy script can run your tests against the production build. ContinuousIntegration.
Software Development The biggest change we’ve seen is the growth in interest in coding practices; 35% year-over-year growth can’t be ignored, and indicates that software developers are highly motivated to improve their practice of programming. Continuousintegration showed a 22% decline, while continuous deployment had a 7.1%
The details of how to respond during an incident are out of the scope of this book. A programmer makes an off-by-one error, but their pairing partner suggests a test to catch it. A team member accidentally erases a file, but continuousintegration rejects the commit. This is incident analysis.
Test-DrivenDevelopment. Continuous Deployment. Complicated configuration ends up being a form of code—code that’s written in a particularly lousy programming language, without abstractions or tests. It’s okay to use DEBUG logs during development, but don’t check them in. Feature Toggles. Sign up here.
Lean is about Flow Efficiency The book This is Lean (Modig and Ahlström, 2013) describes “lean” as a relentless focus on efficiency – but not the kind of efficiency that cuts staff and money, nor the kind of efficiency that strives to keep every resource busy all of the time. Put the tests into a test harness for ongoing code verification.
We organize all of the trending information in your field so you don't have to. Join 49,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content