johnjames4214

3 ms·

1. 1.▲
   Peak Slop: Why the "Wrapper" Era Collapses in 2026(johnjames.blog)

   1 points by johnjames4214 9mo ago|0 comments
2. 2.▲
   Complexity Ceilings and Licensing Wars: My 2026 Predictions(johnjames.blog)

   2 points by johnjames4214 9mo ago|0 comments
3. 3.▲
   by johnjames4214 10mo ago

   Exactly. If it's that verbose and painful for a public API like Shopify/GitHub (where the 'flexibility' argument is strongest), it makes even less sense for internal enterprise apps. We are paying that same complexity ta
4. 4.▲
   GraphQL: The enterprise honeymoon is over(johnjames.blog)

   255 points by johnjames4214 10mo ago|235 comments
5. 5.▲
   Automating dependabot reviews how AI cut dependency research time(johnjames.blog)

   3 points by johnjames4214 11mo ago|0 comments
6. 6.▲
   by johnjames4214 1y ago

   yeah you can definitely point it at lodash (or any utility lib) and it’ll surface spots where it’s imported but never really used. but for “we could just rewrite this tiny helper ourselves” type stuff, knip won’t judge code quality. it’s mo
7. 7.▲
   by johnjames4214 1y ago

   in a decade+ old fintech monorepo w/ microfrontends + BFFs + mixed stacks/design systems (react, angular, express, apollo, chakra, tw) the cruft builds up fast. every time we migrate stuff (like the recent shift to next.js), old a