a problem we've been thinking for a while: when you built software using third-party APIs and SDKs, those dependencies don't stay the same forever. endpoints get deprecated, SDK methods change, parameters are renamed, and sometimes even model aliases silently point to newer versions. then someone has to investigate what changed, find where it's used across the codebase, figure out the migration and manually fix and test everything. we think this workflow should be automated. so we're building Brinq, a system that connects upstream API changes to the code that depends on them, with the goal of automating impact analysis, migration, and verification. I'd love feedback from developers who maintain applications with multiple external API dependencies: when an API or SDK you depend on introduces a breaking change, how do you figure out which parts of your codebase are affected? how much engineering time does investigating and migrating these changes typically take? have you ever postponed upgrading an API or SDK because the migration effort wasn't worth the time? would you trust a system to identify affected code, implement the migration, run tests, and open a PR for your review? we're working towards an early-access release and would love to have developers try Brinq. you can join the waitlist here: https://waitlist.brinq.dev/ would genuinely appreciate your feedback, including what you're think we're getting wrong.   submitted by   /u/shamikhan005 [link]   [comments]