The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Title :
Pocket Tanks — 2-Player Artillery Game in Java
Short description:
A fully self-developed 2-player artillery game built in Java featuring destructible terrain, multiple weapons, wind physics, animated visuals, and custom synthesized audio.
Project description:
I built Pocket Tanks from scratch as a solo Java development project. The game is designed for two players and includes interactive artillery gameplay with destructible terrain and dynamic wind effects.
Key Features
🎮 2-player local gameplay
💥 Destructible terrain
🔫 7 different weapons
🌬️ Dynamic wind mechanics
🎨 Animated 2D visuals
🔊 Synthesized sound effects and music
🖥️ Desktop application interface
My Role : Solo Developer.
I handled the development of the game's gameplay mechanics, UI, graphics, physics, audio, and overall application structure.
Tools & Technologies :
Java · Swing · Java 2D · IntelliJ IDEA · Git · GitHub
Skills Demonstrated :
Java Development · Game Development · Desktop Applications · Software Engineering · UI Design
Link to the work : https://github.com/mabusabkb/pocket-tanks-java
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Someone asked for a tool like yours on Reddit an hour ago. Did you see it?
Riffle finds buying conversations so you can be the answer.
Waitlist open: rifflehq.com
Nice design
⚠️ Developers: Be careful with project files sent by “clients” or "recruiters".
I recently received a project from someone, who I reported instantly after looking at the malicious codebase. After inspecting the files, I discovered it was a malicious Git repository designed to target developers. I reported the person immediately.
The project looked like a normal Next.js/NestJS application, but the malicious code was hidden inside .git and related folders.
The attack was designed to trigger through normal developer workflows such as:
- git status, git checkout, or git commit
- VS Code/Cursor Git integrations
- AI coding agents that automatically inspect a repository
- Git hooks and other automated tooling
The payload appeared designed to retrieve additional encrypted programs from attacker-controlled infrastructure and execute them with the developer's permissions. The technique also showed characteristics reported in attacks targeting developers through fake freelance/job opportunities.
Important: I did not extract or execute the repository, and I inspected it in an isolated/read-only manner.
Protect yourself. Before opening an unfamiliar project:
- Don't blindly run npm install, git status, scripts, or other commands.
- Be extremely careful with .git, .github, .husky, .claude, and Git hooks.
- Don't open suspicious repositories directly in your normal development environment or AI coding agent.
- Verify who sent the project and why they need you to download it.
- If something feels suspicious, inspect the archive without extracting/executing it.
Don't assume a professional-looking codebase is safe. A developer's normal tools can become the attack surface.
SHA-256 of the archive:
94bc839a9876138b5bdeafdac068b43ece80b42eda240caff95a8e3a35b06a1f
Stay safe out there. 🔐
AI Code Performance Engineer is a developer tool I built to analyze codebases, identify performance bottlenecks, generate optimization candidates, verify correctness, and benchmark whether changes actually improve performance. It combines software performance engineering, automation, testing, CI/CD, and AI-assisted optimization into a single workflow focused on measurable results rather than speculative suggestions.
I'd run the baseline and AI-generated candidate on fixed inputs in the same benchmark job, then compare repeated timings and memory use after the correctness check. How are you filtering out CI runner noise before accepting a speedup?