Home > Articles > Programming > Java

How to Crash and Burn Your Java Project

Pete McBreen presents a fly-on-the-wall perspective on the strange things project teams do to ensure that their Java project never manages to deliver anything useful.
Like this article? We recommend

The most important thing you have to do in order to crash and burn your Java project is to ensure that nobody who knows anything about OO design gets to work on the project. The easiest way to do this is to hire cheap, fresh out of school "Java wannabe" programmers and give the design job to someone who has never delivered an OO application. If that strategy fails and you get given a real designer make sure that some really junior programmers are assigned the task of "assisting with the design". If you do this really well your designer will be too busy helping the juniors to actually manage to do any design.

Make sure that you start the project with a really big team from day 1. After all, we all know that adding people to a late project makes it later, so we should start with a big team right from the start. A big team also mitigates the problem of losing people as the project progresses, so the best plan is to over-staff at the start, allowing natural attrition to reduce the team to the optimum size by the end of the project.

Starting with a really big team also helps prevent any real OO design from happening, after all with all those developers you have to start coding as early as possible. The earlier we can start coding the earlier the project will be finished.

To add a bit of excitement to this mix make sure that the requirements are vague. The best way to do this is to create a really thick functional specification containing lots and lots of detail about how the application is supposed to work. The trick to making this work is to ensure that this 1,000 page "tree-killer" doesn’t contain any information about what the overall purpose of the application is or the business justification behind the application. After all that kind of information is too high level for mere programmers to be interested in.

If someone has the temerity to suggest that using Use Cases would be a better way of documenting the requirements, make sure that the Use Cases get written after the functional specification is complete. After all your users are familiar with functional specifications, so first the team must give them what they are familiar with and only then can they waste time on creating these new fangled Use Cases. For added fun make sure that everyone who gets involved in writing these Use Cases uses a different style. This is easier than it sounds. All you have to do is buy one of each Use Case book and make sure that each analyst is given an office next to their users who you have thoughtfully loaned one of your Use Case books to.

Having handled the requirements capture process you now have to turn your attention to the application architecture. If you already have a corporate application architecture then your best bet is to make a case that your project is special and needs to use a different application architecture. Select your best designers and programmers and give them a free hand to investigate alternatives. Make sure that they write up their recommendations in the form of a white paper. Once this is in place the rest of your team can ignore the corporate application architecture and do whatever they want to do. When the white paper is eventually ready, even if the recommendation is rejected it will be too late to change all of the code that has already been developed.

If you do not already have a corporate application architecture you are safe. Either roll your own infrastructure or select a bleeding edge vendor. Bleeding edge vendors are best because by the time your application is ready the infrastructure will be stable and state of the art. Make sure that you consider all possible vendors and have your complete evaluation process documented before you start so that nobody can say that the selection process was biased.

Rolling your own infrastructure can also be a winning strategy because these frameworks are not all that complex and you could always sell it to other companies when you are finished. It’s also a great way to use up your highly skilled talent on the project.

With requirements and architecture sorted you now need to turn your attention to the real developers who will be writing your application. Even though you have hired cheap you want to make your team believe that they are the best individual developers in the world. To do this encourage them to display their creativity and intelligence through the code that they write. Also, if any of them have the temerity to ask for a course you can squash that heresy immediately by implying that "if you can't get it out of a book, you must be stupid". This of course helps the entire team think that they are really brilliant and your attitude will prevent genuinely good developers from ever staying long enough to dispel the myth that you are creating.

To encourage developers to creatively express themselves through their code you need to ensure that you have an immensely detailed coding standard. Rather than stifle creativity by insisting on a single placement of braces, let each developer choose a construct and let them define that part of the coding standard. This avoids all those unproductive hours of arguing about the one true brace style and allows every developer to put their stamp on the coding standards. Do the same thing for comments, naming conventions etc., until you have a 200+ page coding standard. Circulate the resulting document throughout the company and set up a mailing list for discussions and feedback because meetings would be much too much of a drag on the project. Encourage flame wars on this mailing list as having an emotional outlet is healthy for the team.

Since code reviews are harmful to the creative expression of individuality by programmers avoid them if at all possible. If you have to do code reviews you must ignore all of the feedback from them. Even if there is a list of items requiring changes, postpone working on that code because it’s much more important that you add more new features to the application.

Remember all that stuff about "encapsulation" that OO books talk about? Don’t touch it. Private methods make it impossible to use inheritance. Ideally everything should be public so that it can be accessed in the most efficient manner. The other problem with encapsulation is that forces developers to write lots of inefficient little methods that are scattered across lots of different classes. To add a simple feature developers have to modify lots of different files and even with the best will in the world it’s easy to make a mistake when modifying lots of files. The best place to put all of the code is either behind the OK button (you only have to go to one place to see what is happening) or in stored procedures in the database (since these give optimal database performance).

The last thing you have to remember is that developers always over estimate the time they need to write the code. You need to question all estimates and make every developer justify why they need to take that long. A good put down line to use is "I’ve written more complex things in half the time." If any developer is unwilling to reduce their estimates find them a much simpler task that even they can do and give their work to a real programmer.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020