• 1000 word minimum. 
  • Share an experience of the use of RAD Studio (Delphi, C++Builder, InterBase and/or RAD Server) in an enterprise setting. 
  • Theoretical use cases are fine but make that clear (i.e. don’t make false statements, but it is fine to say “here is why I believe you should use Delphi in this use case” 
  • It is great if you are a first party involved with the development of the application, but it is not required. For example if you discovered or heard that a certain company or software uses RAD Studio you can discuss that and how that software benefits. Just don’t misrepresent your knowledge (i.e. don’t imply you wrote the software, instead state how/why you believe it is written with RAD Studio or even why you think it should be). 
  • Facts should be accurate. Opinions are fine, but don’t misrepresent them as facts.
  • Open to all members of the community, including MVPs and Tech Partners. 
  • Must discuss advantages and benefits of RAD Studio’s use in the particular use case or scenario.


  • Use Grammarly or similar tools to check your spelling and grammar.
  • Use good writing techniques like having an introductory and concluding paragraphs.
  • Discuss what makes a successful enterprise application.
  • Mention specific features, components, libraries, tools, etc. that are used.
  • A few small code samples are nice too.
  • You can use a little HTML or Markdown to add basic formatting, links, etc. If you want a lot of formatting or images, then provide a link to a publicly viewable Google Doc. 
  • Any images included must have a note somewhere indicating the source of the image, the public URL of the original image, and the copyright status – for example “author’s own image”, “Licensed from”, “Wikimedia image used with permission and attribution” etc. Google image search isn’t a valid source.
  • The main heading should be AP style with initial caps: “Headline Of Article”, subheadings should be H2 or H3 tags, no extra formatting such as bold or italics and should be in natural case “This is a secondary headline”.
  • The article will be checked for plagiarism. If you have quoted anyone or a document, you must make it clear and include a reference to the original source unless it is apocryphal: “Be yourself; everyone else is already taken.” ― Oscar Wild.
  • Don’t include affiliate links such as Amazon referrer promotional links.
  • Don’t include any offensive language – including words with letters replaced Batman kerpow-style “computer s%ftware”.
  • We reserve the right to edit, truncate, reword (for clarification or to comply with laws and standards) and generally shape the article to fit the space we have available. Any changes will be the minimum we need, and we will take care to avoid changing your ‘voice’ and integrity, or to otherwise make you say something you didn’t.

Either submit the text of the article in the article submission field or enter a URL to a Google Docs where we can access the article.