iiinova — where your digital self keeps evolving

Andreas Frömer @icanhazstring.bsky.social · 22/09/2025

Maintaining OSS is hard when bug reports just say “doesn’t work.” That’s why I built composer-unused.dev 🛠️ A tool to share reproducible scenarios, so I can turn your problem into a test case + fix it faster. #php #opensource

composer-unused.dev

composer-unused - Show unused composer dependencies

Show unused composer dependencies by scanning your code

010

Andreas Frömer @icanhazstring.bsky.social · 30/06/2025

🚀 Major progress on composer-unused.dev! Docker communication, dynamic environments, and real-time results are now working. Still adding storage and logging. Can't wait to share - it'll help users report bugs better and improve my support! #PHP #Composer #WebDevelopment #OpenSource #DevTools

030

Andreas Frömer @icanhazstring.bsky.social · 27/06/2025

composer-unused.dev just got a redesign! 🌈 New colors 👀 Sneak peek of features 🚧 Still under construction 💡 Feedback and ideas welcome! Check it out: composer-unused.dev #PHP #ComposerUnused #WebDev #OpenSource #WIP

composer-unused.dev

composer-unused - Show unused composer dependencies

Show unused composer dependencies by scanning your code

010

Andreas Frömer @icanhazstring.bsky.social · 25/06/2025

Lately, I've been experimenting with #AI. I have always sought a way to effectively utilize AI in #SoftwareDevelopment. I started a small project to get a one-click integration between server IPs and my terminal, using AI to bootstrap the idea. github.com/icanhazstrin... What do you think?

github.com

GitHub - icanhazstring/sshlink: 🚀 One-click SSH connections from your browser to any terminal

🚀 One-click SSH connections from your browser to any terminal - icanhazstring/sshlink

010

Reposted by Andreas Frömer

Marcin Milewicz @marcinmilewicz.bsky.social · 24/11/2024

DRY isn’t always good! When NOT to DRY: 1️⃣ Premature abstractions lead to tight coupling. 2️⃣ Over-generic code hurts readability. 3️⃣ Similar code may have different purposes. Consider to Write Everything Twice (WET) first, then refactor later. What’s your take on this? #softwaredevelopment #coding

662