Write for Us!

Tutorials, reviews, overviews as well as case studies and news are always needed.

We can handle any type of submission but prefer email . Screenshots are always welcome. Try to give us some help by mentioning the subject in the header of the email.

General Guidance

Articles are usually about 800 words per page, although code listings and images will reduce this. If possible try to write full pages.

As we sell in many countries and translate into other languages try not to write in slang or use too many idioms. Try to plan ahead. By the time the magazine reaches your desk it has gone through many stages from production, printing and distribution. This means if you say something will happen next week in an article, in the magazine on your desk that date has already passed.

Please send in your proposals to  edit@admin-magazine.com .

Related content

  • Write for Us

    Write for Us!

  • Tuning I/O Patterns in Python

    In the third article of this three-part series, we look at simple write examples in Python and track the output with strace to see how it affects I/O patterns and performance.

  • Process, Network, and Disk Metrics

    In the continuing story of monitoring HPC systems, we look at code that measures process, network, and disk metrics.

  • Monitoring Storage with iostat

    One tool you can use to monitor the performance of storage devices is iostat. In this article, we talk a bit about iostat, introduce a Python script that takes iostat data and creates an HTML report with charts, and look at a simple example of using iostat to examine storage device behavior while running IOzone.

  • Moving Your Data – It’s Not Always Pleasant

    The world is swimming in data, and the pool is getting deeper at an alarming rate. At some point you will have to migrate data from one set of storage devices to another. Although it sounds easy, is it? We take a look at some tools that can help.

comments powered by Disqus