Editorial Policy

1. Who We Are

GetUp is an independent Java engineering blog based in Bangalore, India. We publish long-form technical articles on chess engine internals — board representation, move generation, search, and evaluation — and on Java and JVM behaviour, particularly the exceptions that commonly catch developers out.

Every article is written by a developer who implemented the code it describes. We do not publish articles on topics the author has not worked through in practice.

2. Content Standards

Accuracy First

We publish only information we can verify. This means:

• Claims about Java or JVM behaviour are checked against the language specification, the official javadoc, or the OpenJDK source
• Performance figures — node counts, perft results, timings — come from runs we performed ourselves, with the conditions stated
• We clearly distinguish between what we have personally implemented and tested and what we report from third-party sources

Original Reporting

All content on GetUp is original. We do not republish, paraphrase, or scrape content from other publications. When we cite external sources, we link to them directly and credit them appropriately. Summaries of official announcements or research are clearly attributed.

Timeliness and Updates

Java releases change behaviour, and APIs are deprecated. When information we've published becomes outdated, we update the article and note the revision date at the top. We do not silently delete or rewrite articles in ways that misrepresent what was originally said.

3. Our Content Creation Process

1. Topic Selection — Topics come from problems encountered while building. If a problem was hard to solve because no clear explanation existed, that is a strong signal it is worth writing up. We do not create content purely for SEO volume.
2. Implementation — The code is written and made to work first. Articles describe working implementations, not hypothetical ones.
3. Research — We consult primary sources: the Java Language Specification, official javadoc, the OpenJDK source, and established chess programming references. Where a technique is standard, we credit its origin.
4. Writing — Articles are written by the developer who implemented the code. We avoid filler, keyword-stuffing, and padding that wastes the reader's time.
5. Verification — Before publishing, code samples are re-run and figures re-checked. Move generation claims are validated against known perft counts.
6. Publishing — We include publish dates, and update dates when articles are revised, so readers know how current the content is.
7. Post-publish Monitoring — We monitor articles for reader feedback and update them when the underlying information changes.

4. Techniques and Recommendations

When we recommend an approach, a data structure, or a library, we aim to give a complete picture — including its costs and the cases where it is the wrong choice. Recommendations come from having used the technique, not from its documentation alone.

• We do not accept payment in exchange for favourable coverage
• Sponsored content, if any, is clearly labeled as such at the top of the article
• Trade-offs are stated explicitly — where an approach is slower, more complex, or only suitable in narrow cases, we say so rather than presenting it as a general fix

5. Corrections and Retractions

We take accuracy seriously. If you spot an error in any of our articles, please contact us using the information below. We will:

• Investigate the reported error promptly
• Correct factual inaccuracies and note the correction at the bottom of the article
• Issue a retraction if an article is found to be substantially incorrect

We do not alter published articles to hide errors without noting the change.

6. Conflicts of Interest

We disclose any relationship that could reasonably influence how we cover a topic. This includes:

• Advertising: This site displays ads served by Google AdSense. Advertising is handled entirely by Google and has no influence on what we publish or what we conclude. See our Privacy Policy for how ad cookies are used.
• Affiliate Links: We currently have no affiliate relationships and earn no commission from links in our articles. If that changes, affected links will be disclosed in the article itself.
• Sponsored Content: We have not published any sponsored content to date. Any article written with sponsorship or compensation would be labeled "Sponsored" at the top, with editorial conclusions remaining our own.

7. Privacy and Sensitive Content

We follow responsible disclosure practices when covering topics related to personal data or security vulnerabilities. We do not publish personal information about private individuals without their consent.

8. User-Generated Content

Currently, GetUp does not host user-generated content or public comments. If this changes, this policy will be updated to reflect how such content is moderated.

9. AI-Assisted Writing Disclosure

We may use AI writing tools as research or drafting aids. However, all published content is reviewed, edited, and verified by the author, who takes responsibility for its accuracy — including re-running the code and confirming the figures. We do not publish raw AI output without significant human oversight and editing.

10. Contact Our Editorial Team

For corrections, editorial feedback, partnership inquiries, or concerns about any published content, please reach out: