Preparing for a large exam often starts with a familiar problem: the material exists, but it is scattered across old links, downloaded files, and personal notes. That makes it difficult to answer a simple question: which exams and answer keys do I actually have, and can someone else reproduce my setup?
The awesome-poscomp repository solves the archive part of that problem. It collects POSCOMP exam papers and answer keys in one public Git repository, with a year-by-year index. POSCOMP is the Brazilian national exam commonly used in admission processes for graduate computing programs. The official SBC POSCOMP page is the authority for the exam itself; the repository is a convenient, reviewable study archive.
This tutorial shows how to create a local study library, verify that the repository is the one you intended to use, and inspect the available years without relying on an opaque download folder.
TL;DR
Clone paladini/awesome-poscomp, inspect its README and license, list the local PDF files, and compare the result with the repository index. Keep the repository commit with your notes so the study setup can be reproduced later.
Prerequisites
You need:
- Git 2.x installed and available on your PATH.
- A PDF viewer. A command-line PDF text tool is optional.
- A Windows PowerShell, macOS, or Linux shell.
- Enough disk space for the archive and any notes you add.
The repository is public and uses the MIT license. It is an archive of study material, not an official registration system, score calculator, or guarantee that a particular graduate program accepts a result. Check the official SBC material and the rules of the program you are applying to.
1. Clone a known revision
Start with a dedicated directory. The URL below is the public repository URL, so the command is independently checkable.
git clone https://github.com/paladini/awesome-poscomp.git
cd awesome-poscomp
Record the revision used for your study plan:
git rev-parse --short HEAD
git remote -v
The current default branch is master. A commit identifier matters because an archive can gain a new exam or fix a link later. If you share a study checklist with another person, include the commit hash beside it.
2. Read the index before opening PDFs
The repository README is the catalog. It groups the collection by year and links to a question booklet and an answer key when both are available. It currently describes material from 2002 through 2024 and includes a provisional 2025 entry.
Open the README in a browser or inspect it from the shell:
git show HEAD:README.md
The index is useful for two reasons. First, it tells you whether a local file is expected for a particular year. Second, it distinguishes a repository-hosted PDF from a link to an external SBC, university, or publication host. That distinction matters when a link stops working: the repository can preserve some files locally, but it cannot guarantee the availability of an external website.
3. Build a local inventory
On macOS or Linux, list the PDFs with:
find poscomp -type f -iname '*.pdf' | sort
On PowerShell, use:
Get-ChildItem -Path .\poscomp -Recurse -File -Filter *.pdf |
Sort-Object FullName |
Select-Object -ExpandProperty FullName
The output gives you a concrete inventory instead of a vague claim that the archive is complete. You can save it as a review artifact without changing the repository:
find poscomp -type f -iname '*.pdf' | sort > poscomp-pdfs.txt
The file names should make the role of each document clear, such as a question booklet or a gabarito. Do not assume that every year has the same local layout. The README is the source for what each link means.
4. Check that the PDFs are readable
Open one question booklet and its answer key for a recent year, then repeat the check for an older year. This catches incomplete downloads and viewer problems early.
If pdfinfo is installed, you can inspect the document metadata:
pdfinfo poscomp/2024/poscomp_caderno_prova_2024.pdf
pdfinfo poscomp/2024/poscomp_prova_gabarito_2024.pdf
The exact file names may change as the archive evolves, so use the paths returned by your inventory command. A successful metadata read is only a basic integrity check. It does not prove that every answer is correct or that a PDF is an official publication.
For a stronger local check, extract a few pages to text when your PDF tools support it:
pdftotext -f 1 -l 2 poscomp/2024/poscomp_caderno_prova_2024.pdf -
Look for a title, year, or question heading. This is a reproducible sanity check, not a replacement for reading the source document.
5. Turn the archive into a study loop
A repository becomes useful when it supports a repeatable decision process. Pick one year and one subject area from the program topics listed in the README, then work through the question booklet without consulting the key. Save your answers outside the cloned repository or on a separate branch.
After the attempt, compare with the answer key and record only the questions that need review. The README groups the content into areas such as mathematics, foundations of computing, and computing technology. That makes it possible to build a small backlog instead of rereading every subject after every practice session.
For example, a simple weekly routine can be:
- Select one available year from the index.
- Complete a bounded set of questions under a fixed time limit.
- Compare answers with the matching key.
- Tag missed questions by topic.
- Repeat the same topic with another year.
The important detail is the evidence trail. Keep the repository commit, year, PDF path, and your notes together. If a link is later corrected, you can tell which source you used at the time.
Expected result
At the end, you should have a local checkout with an identifiable Git revision, a list of available PDFs, and a study note that points to exact files. A minimal verification report might contain:
Repository: paladini/awesome-poscomp
Revision: <output of git rev-parse --short HEAD>
Archive index: README.md
Recent sample: poscomp/2024/
Older sample: <path selected from the local inventory>
Integrity check: PDF metadata and first-page text read successfully
This result is more useful than a folder named poscomp-final, because another person can reproduce the same starting point and see which parts came from the public archive.
Why the Git workflow helps
Git provides three practical properties for study material. The remote URL identifies the source. The commit hash identifies the exact snapshot. A text inventory identifies the files you actually used. Together, those properties reduce accidental mixing of answer keys from different years or silently missing documents.
The workflow also keeps the boundary between community-maintained convenience and official information visible. The repository links to the SBC and other public sources, but it does not replace them. Always verify current exam dates, registration rules, and program requirements with the responsible institution.
Failure modes and limitations
If git clone fails, check network access and the repository URL. If a PDF is missing, compare your local tree with the README because some entries point to external sites rather than repository files. If a PDF opens but has no selectable text, use a viewer or OCR tool carefully and treat extracted text as a convenience layer.
The archive does not automatically grade answers, generate a personalized curriculum, or certify that a question set is current. It also cannot guarantee that external links remain available. The repository license permits reuse under its terms, but the individual exam documents can have their own provenance and publication context. Preserve source links and attribution when redistributing material.
FAQ
Is this the official POSCOMP website?
No. The SBC POSCOMP page is the official starting point for exam information. This repository is a public study archive.
Do I need to install a programming language?
No. Git and a PDF viewer are enough for the basic workflow. PDF command-line tools are optional verification helpers.
Should I edit the cloned repository with my answers?
Keep personal answers and annotations separate unless you intentionally want to create a reviewable fork. A separate notes directory makes it easier to update the archive without merging personal files into source material.
Can I rely on the newest year shown in the README?
Treat each entry according to its label. A provisional or external link needs separate confirmation. Check the official SBC publication before treating a document as authoritative for a current exam.
Takeaway
awesome-poscomp turns a scattered set of POSCOMP references into a reviewable Git starting point. Clone it, record the revision, inventory the PDFs, verify representative files, and keep your study notes tied to exact paths. That small amount of provenance makes a personal preparation workflow easier to reproduce and safer to update.
Have you found a useful way to turn past POSCOMP questions into a topic-based review backlog without losing the source year and answer-key provenance?
Disclosure: AI assistance was used to organize and edit this tutorial. The repository links, commands, and limitations were checked against the public project and official POSCOMP source pages.
Top comments (0)