10 Reasons You MUST Consider Pattern-Aware Programming

Editor's Notes

• #8: Conventional programming languages like C# and Visual Basic miss a concept of pattern, therefore patterns like threading, INotifyPropertyChanged or logging are hand-coded and result in a large amount of boilerplate code. This boilerplate code adds up to: High development effort: some features require a large amount of repetitive code when implemented manually The quality of the produced software is poor as it contains high number of defects. Code that stems from copy-paste programming is more likely than other to be buggy because subtle differences are often overlooked. The applications we develop often lack robustness as enterprise-grade features such as exception handling or caching are often deliberately omitted because of the high amount of source code they imply. It’s difficult to add/modify functionality after first release because the business code is often littered with low-level non-functional requirements and so is more difficult to understand and maintain. Features like logging, exception handling or INotifyPropertyChanged are often scattered among thousands of files, making it very difficult to change their implementation. Codebases with a lot of boilerplate slow down the ramp-up of new team members as they often must first learn about caching, threading and other highly technical issues before being able to contribute to the business value. There are also long feedback loops even in small development teams as common patterns like diagnostics, logging, threading, INotifyPropertyChanged and undo/redo can be handled differently by each developer. Architects need to make sure new team members understand and follow the internal design standards and have to spend more time on manual code reviews--delaying progress while new team members wait to get feedback from code review.
• #9: Wouldn't it be nice to produce high-quality, software that is easy to maintain with less development effort and faster ramp-up of new team members... without having to replace your existing compiler? You may want to consider…
• #13: Pattern-Aware Compiler Extensions. They extend conventional object-oriented programming with a concept of pattern and so patterns do not need to be manually implemented as boilerplate code. Features such as INotifyPropertyChanged, logging, transactions are implemented in a cleaner, more concise way, making development and maintenance much easier.
• #14: Stop writing boilerplate and deliver faster As you stop implementing patterns manually and outsource the repetitive work to the compiler, you will need less lines of code to deliver a functionality. Fewer lines of code means fewer hours of work so you’ll be able to deliver features faster and save development time and costs immediately
• #15: 2. Build more reliable software • With a pattern-aware compiler eliminating the boilerplate, your code becomes easier to read, understand and modify, and contains fewer defects. • Reliability becomes much more affordable. Because reliability features such as caching or exception handling no longer require so much manual coding, they are much easier and cheaper to implement. You can spend your extra time building a more robust app.
• #16: 3. Pattern-aware compiler extensions make it easier to add or modify functionality. • Cleaner and shorter code is easier to understand. After the initial release, too much development time is spent on reading and analyzing source code, especially if the initial developer left. With minimized boilerplate code, developers can easily focus on business logic and spend much less time trying to understand the code. • Better architecture is future-proof. Using a pattern-aware compiler, features like logging, exception handling or transactions are no longer scattered among thousands of files but they are defined in one place, making it much easier and fast to modify when necessary.
• #17: 4. New team members contribute quicker • Pattern-aware compilers help new team members contribute quicker and achieve a better division of labor. Because your codebase is cleaner, new or junior team members can focus on simpler, more business logic-oriented tasks rather than having to waste so much time learning complex architectural structures. • Implement a tighter feedback loop. A pattern-aware compiler can validate that hand-written code respects a pattern or a model, and it can detect bugs at build time instead of during code reviews, testing, or in production.
• #18: There are 4 reasons why to consider pattern-aware compiler extensions: They help you stop writing boilerplate code and deliver faster because patterns do not need to be manually implemented as boilerplate code. You can build more reliable software They make it easier to add/modify functionality after first release New team members can contribute quicker thanks to cleaner codebase
• #19: 4. New team members contribute quicker • Pattern-aware compilers help new team members contribute quicker and achieve a better division of labor. Because your codebase is cleaner, new or junior team members can focus on simpler, more business logic-oriented tasks rather than having to waste so much time learning complex architectural structures. • Implement a tighter feedback loop. A pattern-aware compiler can validate that hand-written code respects a pattern or a model, and it can detect bugs at build time instead of during code reviews, testing, or in production.
• #20: 4. New team members contribute quicker • Pattern-aware compilers help new team members contribute quicker and achieve a better division of labor. Because your codebase is cleaner, new or junior team members can focus on simpler, more business logic-oriented tasks rather than having to waste so much time learning complex architectural structures. • Implement a tighter feedback loop. A pattern-aware compiler can validate that hand-written code respects a pattern or a model, and it can detect bugs at build time instead of during code reviews, testing, or in production.
• #22: 4. New team members contribute quicker • Pattern-aware compilers help new team members contribute quicker and achieve a better division of labor. Because your codebase is cleaner, new or junior team members can focus on simpler, more business logic-oriented tasks rather than having to waste so much time learning complex architectural structures. • Implement a tighter feedback loop. A pattern-aware compiler can validate that hand-written code respects a pattern or a model, and it can detect bugs at build time instead of during code reviews, testing, or in production.
• #24: 4. New team members contribute quicker • Pattern-aware compilers help new team members contribute quicker and achieve a better division of labor. Because your codebase is cleaner, new or junior team members can focus on simpler, more business logic-oriented tasks rather than having to waste so much time learning complex architectural structures. • Implement a tighter feedback loop. A pattern-aware compiler can validate that hand-written code respects a pattern or a model, and it can detect bugs at build time instead of during code reviews, testing, or in production.
• #25: 4. New team members contribute quicker • Pattern-aware compilers help new team members contribute quicker and achieve a better division of labor. Because your codebase is cleaner, new or junior team members can focus on simpler, more business logic-oriented tasks rather than having to waste so much time learning complex architectural structures. • Implement a tighter feedback loop. A pattern-aware compiler can validate that hand-written code respects a pattern or a model, and it can detect bugs at build time instead of during code reviews, testing, or in production.
• #26: 4. New team members contribute quicker • Pattern-aware compilers help new team members contribute quicker and achieve a better division of labor. Because your codebase is cleaner, new or junior team members can focus on simpler, more business logic-oriented tasks rather than having to waste so much time learning complex architectural structures. • Implement a tighter feedback loop. A pattern-aware compiler can validate that hand-written code respects a pattern or a model, and it can detect bugs at build time instead of during code reviews, testing, or in production.
• #27: 4. New team members contribute quicker • Pattern-aware compilers help new team members contribute quicker and achieve a better division of labor. Because your codebase is cleaner, new or junior team members can focus on simpler, more business logic-oriented tasks rather than having to waste so much time learning complex architectural structures. • Implement a tighter feedback loop. A pattern-aware compiler can validate that hand-written code respects a pattern or a model, and it can detect bugs at build time instead of during code reviews, testing, or in production.
• #28: 4. New team members contribute quicker • Pattern-aware compilers help new team members contribute quicker and achieve a better division of labor. Because your codebase is cleaner, new or junior team members can focus on simpler, more business logic-oriented tasks rather than having to waste so much time learning complex architectural structures. • Implement a tighter feedback loop. A pattern-aware compiler can validate that hand-written code respects a pattern or a model, and it can detect bugs at build time instead of during code reviews, testing, or in production.
• #29: 4. New team members contribute quicker • Pattern-aware compilers help new team members contribute quicker and achieve a better division of labor. Because your codebase is cleaner, new or junior team members can focus on simpler, more business logic-oriented tasks rather than having to waste so much time learning complex architectural structures. • Implement a tighter feedback loop. A pattern-aware compiler can validate that hand-written code respects a pattern or a model, and it can detect bugs at build time instead of during code reviews, testing, or in production.
• #30: 4. New team members contribute quicker • Pattern-aware compilers help new team members contribute quicker and achieve a better division of labor. Because your codebase is cleaner, new or junior team members can focus on simpler, more business logic-oriented tasks rather than having to waste so much time learning complex architectural structures. • Implement a tighter feedback loop. A pattern-aware compiler can validate that hand-written code respects a pattern or a model, and it can detect bugs at build time instead of during code reviews, testing, or in production.
• #31: Following are the most common questions about PostSharp: Will I be able to understand my code? Yes. Thanks to PostSharp’s Visual Studio tooling, you’ll easily understand where and how patterns are used in your code Can I keep using my existing compiler? Yes. PostSharp is 100% compatible with your existing Microsoft compiler Compilation will be slower Possibly. PostSharp introduces additional steps into the compilation, there is a performance cost. However, PostSharp is highly optimized several times faster than FxCop, etc.
• #32: The detailed document on how ROI is calculated can be provided on request. A few background information on the data: For a cost of only 350$ -- cost of PostSharp license per developer if purchased 5 licenses with 3 years of maintenance (=$5,212 – public price)) Cost for 1 developer is $95k – source: https://visualstudiomagazine.com/articles/salary-surveys/salary-survey.aspx 1 developer typically produces 600 lines of code per month – source: McConnell, Steve (2006-02-22). Software Estimation: Demystifying the Black Art. Pearson Education. PostSharp pays off after he/she saves first 50 lines of code -- Average price for the first year for a 5-dev team: 665$
• #33: Think about the last time your developers found it painful to implement a feature manually or modify functionality in existing software, and then never think of it again. Imagine you could produce high-quality software that is easy to maintain and has fewer bugs – all with less development effort. No more copying and pasting blocks of code to add a functionality. No more spending hours trying to understand the business logic of the code. No more hiring an expensive specialists to build thread-safe applications. Deliver the same functionality faster with less development costs. Stop imagining. Get to know PostSharp, the #1 best-selling pattern-aware extension to C# and VB,and improve your developers’ efficiency and lives.
• #34: Now that you have seen some of the benefits of using a pattern-aware compiler, let's talk about the main reasons you may wish to consider PostSharp, the #1 best-selling pattern-aware compiler extension to C# and Visual Basic.
• #35: Trusted by over 50,000 developers worldwide and over 1,000 leading corporations. More than10% of all Fortune 500 companies including Microsoft, Intel, Bank of America, Phillips, NetApp, BP, Comcast, Volkswagen, Hitachi, Deutsche Bank, Bosch, Siemens, and Oracle rely on PostSharp to reduce their development and maintenance costs.
• #36: Steps to Actuate Sign up for free trial See more features and code examples on www.postsharp.net Read case studies and testimonials of satisfied customers Attend a free live webinar Get the price or request a quote Contact us with any questions