property-tax-calculator

github.com/Andrewkwame1/property-tax-calculator

2026-01-11 ~ 2026-02-28 · 48 days

README Dreamer

A perfectly functional CI/CD pipeline for an Android app that was never formally released

“Ready for release, but never released”

Death Type

Pipeline Paranoia

This project suffered from 'Pipeline Paranoia', a condition where the deployment infrastructure (`.github/workflows/gradle-publish.yml` with `actions/setup-java@v4` and `gradle/actions/setup-gradle@af1da67850ed9a4cedd57bfd976089dd991e2582`) becomes more complete and functional than the actual product it's meant to ship. It was ready for anything, except actual users.

Cause of Death

1. A 9-day development sprint

All 7 commits by 'Andrew Acheampong' landed between 2026-02-19 and 2026-02-28, indicating a brief, intense burst of activity that quickly ceased.

2. CI/CD without a release

The `.github/workflows/gradle-publish.yml` workflow was fully implemented to publish Gradle packages to GitHub Packages, yet no actual releases were ever published, leaving the pipeline idle.

3. Nocturnal coding habits

A staggering 83% of the project's 7 commits occurred between midnight and 4 AM, suggesting a development pattern unsustainable for long-term project health.

Vibe Score

17/ 100

Hand-coded. Respect.

What They Did

This project, as detailed in its +106/-2 line README.md, aspired to be an 'Android application designed to help homeowners and real estate professionals estimate property taxes'. It meticulously set up a Java 11-based Android app targeting API 36, complete with a GitHub Actions workflow for publishing to GitHub Packages.

JavaAndroidXGradleJUnitEspresso

Burnout Analysis

The developer, 'Andrew Acheampong', compressed all 7 commits into a frantic 9-day window, from 2026-02-19 to 2026-02-28. An astounding 83% of these commits were made between midnight and 4 AM, indicating a punishing nocturnal schedule. After the final 'Resolved merge conflict' commit, 38 days of absolute silence followed, suggesting a swift and decisive end to the project's active life.

Dependency Archaeology

The `app/build.gradle` meticulously declared 7 dependencies, including `androidx.appcompat`, `material`, and testing frameworks `junit` and `espresso.core`. This robust AndroidX stack was assembled for an application that, despite its readiness for formal releases, never calculated a single property tax for an actual homeowner. A full toolbox, for a task left undone.

Autopsy: File Structure

├──README.mdReceived +106 lines, promising 'homeowners and real estate professionals' an app, but delivered badges instead of binaries.

├──.github/workflows/gradle-publish.ymlA perfectly functional CI/CD pipeline, implemented with +88 lines, eagerly awaiting a release that would never arrive.

├──app/build.gradleDeclared 7 dependencies and targeted Android API 36, a full stack for a project that lived for 9 days.

├──app/src/main/java/com/example/propertytaxcalculator/MainActivity.javaThe core logic, with +78 lines, beating for a mere 9 days before falling silent.

├──app/src/main/res/layout/activity_main.xmlReceived +173 lines of XML, extensive UI work for a user base of precisely zero.

├──gradlewGained +251 lines, a testament to build system setup that outlived the application's active development by 38 days.

└──app/src/main/res/drawable/ic_launcher_background.xmlReceived +170 lines, ensuring the app icon was perfectly rendered for a launch that never was.

Eulogy Stats

Total Commits: 7
Ambitious Adjectives: 3
Deploy Config: Yes
Estimated Users: 0 (a certainty, given no releases)

Last Words

“The final commit, 'Resolved merge conflict', on 2026-02-28, marked the last recorded activity, a poignant end to a project that never quite resolved its ultimate conflict with public availability.”