Contact Us | Java Practical Guide

About this contact page

This contact page is the primary channel for readers of Dashboardesk. Whether you have spotted a typo, an example did not compile, you disagree with a recommendation, or you want to request a tutorial on a topic we have not yet covered, this is the right place to start. We are a small editorial team and we genuinely read every message that comes through this form — there is no auto-responder and no triage queue.

For fastest help, please include in your message the URL of the tutorial you are writing about (you can copy it from your browser's address bar) and the Java version you are using (run java -version in your terminal if you are not sure). A sentence like “On https://dashboardesk.com/tutorials/java-arraylist.html, the third code example does not compile on Java 21 with the error ‘cannot find symbol’” gives us enough information to debug the issue immediately. Without that information we will need to email you back to ask for it, which adds a round trip.

If you are reporting a security issue, please do not use this form — email security@dashboardesk.com directly so we can route your message to the right person without delay. For partnership, sponsorship, or business inquiries, choose “Partnership or business” in the subject dropdown below; we route those to the editorial director who handles commercial relationships.

If you have a general question about Java that is not specific to a tutorial — “Should I learn Java or Kotlin?”, “Is Spring Boot still relevant?” — we will do our best to answer, but the answer may end up as a future tutorial rather than a personal reply. The more general the question, the more useful the answer is to other readers, and we prefer to publish long-form answers.

Send a Message

Fill out the form below and hit send. The form does not store any data on the server until you submit it — see our privacy policy for what happens to your message after we receive it.

Frequently asked questions about contacting us

Do you reply to every message?

Yes. We read every message that comes through the contact form and reply to all of them, usually within one to two business days. The only exceptions are messages that are clearly spam, abusive, or commercial solicitations unrelated to Java education. If you have not heard back within five business days, please check your spam folder — our replies occasionally land there, especially with corporate email filters.

Can you help me debug my code?

If your bug is in code you copied from one of our tutorials, yes — send us the URL and the exact error message and we will help. If your bug is in your own project code, we cannot debug it for free, but we can often point you at the relevant tutorial or suggest a Stack Overflow search. For ongoing help with your own projects, consider a paid mentor or a coding bootcamp; we are an editorial site, not a consulting firm.

Can I write a guest post for Dashboardesk?

We are open to guest posts from experienced Java engineers who can write a strong tutorial on a topic we have not yet covered. Pitch us through the contact form with a one-paragraph outline, a sample of code you would include, and links to other writing you have published. We pay a small honorarium for accepted guest posts. We do not accept sponsored content disguised as tutorials — if you want to advertise, choose “Partnership or business” in the subject dropdown.

Can I translate your tutorials into another language?

We grant translation rights on a case-by-case basis. If you want to translate one or more tutorials for non-commercial educational use — for example, to share with a study group — we usually say yes. If you want to publish translations on a monetised website or in a paid course, we charge a small per-tutorial fee. Contact us with the language, the tutorials you want to translate, and the intended audience.

Where is your office located?

We are a fully remote team with no physical office. Editorial team members are based in Canada, India, and the European Union. If you need to send physical mail for any reason, contact us first and we will give you a postal address; do not send unsolicited mail.

How do I report a security vulnerability?

Email security@dashboardesk.com directly with a description of the issue, the steps to reproduce, and the impact. We acknowledge receipt within 48 hours and aim to issue a fix or mitigation within 30 days. We credit researchers who report valid issues in our release notes unless they prefer to remain anonymous.