Writing About Performance [Prompts]

DZone 's Guide to

Writing About Performance [Prompts]

Writer's block? Say no more.

· Performance Zone ·
Free Resource

Prompts to banish writer's block.

Prompts to banish writer's block.

Trying to write an article but have nothing to write about? You're in the right place! This is the solution to all your writer's block needs! No more excuses, just solutions. Below, you will find a couple of prompts to get you started in writing for our Performance zone!

Find these helpful? Have ideas for future prompts? Hate it more than writer's block? Comment below and let us know!

Need help? Here's how to submit a post to DZone!

Prompt #1: Testing Vs. Engineering

One of the most common questions when it comes to performance is: What is the difference between performance testing and performance engineering? Do you know? Write an article outlining and similarities and differences, and when each is appropriate.

Don't know the difference? Write about another common misconception when it comes to performance!

Prompt #2: A Day in the Life

Are you a performance tester? Tell us about your job! What time do you get to work? What kinds of tasks do you complete? What are the meetings you attend? We want to know! 

Do you have tips for aspiring performance testers? Ideas to help keep applications running smoothly? Tricks of the trade? Write it all down! Give our developers insight into the performance world.

Prompt #3: Front-End Testing

Tell us everything you know! Send in your tutorial for front-end testing, what are the benefits of it? What are the processes that go into it? What frameworks do you use, and how can other developers use them as well?

Write about how to make front-end testing as fast and effective as possible.

Did that help? Please comment below and let us know! Have ideas for prompts or articles? Have questions about submitting to DZone? Let us know!

performance, performance engineering, performance testing, prompts, writing

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}