Enterprise developers are serious professionals. They don’t waste their time for creating silly things. They leave this to the hipster developers.
Enterprise developers write software which keeps our society running. They are the backbone of the modern society, and they know it.
Enterprise developers claim that they aren’t driven by money. They are driven by “professionalism” and the will to solve “hard” problems.
Even though enterprise developers claim that money isn’t important to them, they expect to be paid well. Everyone around them seems to be making shitloads of money, and they only want their share of the cash. This feels natural to them. It is how business works.
You must be wondering how you can join the brotherhood of enterprise developers and become a respected member of your community. You can start your journey by following this simple rule:
Use the right technologies!
Technology Evaluation Guide for Enterprise Developers
Because enterprise developers are professionals, they have strict rules for selecting the best tools for the job. These rules are:
Rule One: Use Java
This is the most fundamental rule of the brotherhood of enterprise developers. Enterprise developers know that Java is the best language for writing complex applications which have a long lifespan.
A true enterprise developer loves Java because of the following reasons:
- Java has been around for ages and everyone is using it.
- Java has many great IDEs which make the life of a developer so much easier.
- Java has a very strong ecosystem and there is a library for pretty much everything you have to do.
- A developer can choose between Java EE and Spring Framework. This gives them the possibility to choose the best tool for the job.
- Big vendors have great products which help developers to write enterprise applications with Java.
These are all great benefits but the biggest benefits of Java are stability and backwards compatibility.
Everyone knows that hipster developers have to rewrite their application once a year because they use immature and unstable technologies. Enterprise developers don’t suffer from this problem, and they are proud of it.
Rule Two: Use Stable Frameworks and Libraries
Because enterprise developers build systems which must serve their users at all times, they use only battle-tested frameworks and libraries. These frameworks and libraries are often a bit old, but they are proven to work.
That is the only thing what matters when you are building a system which must be available at all times.
Enterprise developers know that adopting new technologies is a very risky strategy. They know that adopting new technologies can be a career-ending mistake, and that is a risk they don’t want to take.
It is better to stick with familiar tools. These tools might have a few bugs and other problems but the enterprise developers are very good at implementing workarounds for these problems. This makes their code less brittle and more stable.
After all, everyone knows that true professionals write stable code. They don’t take risks just because they want to have the latest toys (like hipsters do).
Rule Three: Favor Commercial Products of Big Vendors
Big vendors spend millions of dollars for creating great products which help developers to write highly scalable applications. These products include application servers, business intelligence products, databases, and integration platforms.
Enterprise developers should use these products because of the following reasons:
- Big vendors have experienced architects and large QA departments. In other words, commercial products are written by using good engineering practices, and they have less bugs than open source products.
- Big vendors offer commercial support (and consulting) which ensures that all problems are solved ASAP.
- These products offer stability which is important for the customers of enterprise developers.
An enterprise developer might use open source libraries and frameworks for trivial tasks but when it is time to do some heavy lifting, a responsible developer will always use a commercial product.
Rule Four: XML Is the Universal Language of APIs and Integration
When it comes to APIs and integration, XML is the enterprise developer’s weapon of choice. XML is the best tool for the job because of the following reasons:
- XML is a proven standard and that is why many commercial (and open source) products have first class support for it.
- XML can be processed by machines and read by humans. This is a huge benefit over other proprietary file formats because it makes debugging problems so much easier.
- The structure of a XML document can be specified by using XML schema. This means that it is easy to validate XML documents and ignore invalid data.
Also, Java programming language has a first class support for both reading and creating XML documents, and because all enterprise developers love Java, using XML is a no-brainer to them.
Rule Five: Use Relational Databases
Real enterprise developers use only relational databases because of the following reasons:
- Relational databases have been around for decades and this makes them very mature. This is very important when you are building systems which must be reliable.
- Relational database vendors can provide high level commercial support which is crucial for big corporations. This guarantees that possible problems are solved ASAP.
- Relational databases have good administration tools, and a great support for analytics and business intelligence. This will keep the DBAs happy and ensure that the management has access to the information they need.
- Relational databases have ACID transactions. This guarantees that database transactions are processed reliably.
- Relational databases have a schema which specifies the structure of the database and enforces referential integrity.
Although some hipsters claim that NoSQL databases are a good choice for solving certain problems, enterprise developers know that NoSQL databases are only toys. They cannot understand why anyone would want to use a “database” which doesn’t have a schema and doesn’t support ACID transactions.
That sounds like a recipe for disaster.
Everyone knows that information is the most valuable property of any business, and relational databases help to keep that information safe. That is why enterprise developers use them.
Nobody Ever Got Fired for Buying IBM
The most important rule of the brotherhood is:
Avoid risks at all cost
You want to look professional. You want to be known as a developer who masters complex enterprise technologies, and more importantly, you want to convince your customers that using these technologies will make them safe.
If you really want to protect your customers, you will follow these rules at all times.
These rules will protect you from being wrong and help you to build a reputation as an enterprise developer who understands that a real professional doesn’t experiment with someone else’s money.
This guide will introduce you to the world of Software Architecture!
This 162 page guide will cover topics within the field of software architecture including: software architecture as a solution balancing the concerns of different stakeholders, quality assurance, methods to describe and evaluate architectures, the influence of architecture on reuse, and the life cycle of a system and its architecture. This guide concludes with a comparison between the professions of software architect and software engineer.