If you play games, and keep score...I've just released a passion project that helps with that (for iOS):
https://t.co/0D45mduTVL
Details are available here:
https://t.co/4RdINH3XLd
#boardgames#cardgames#gamenight
The current solution - no more PRs until the board falls under the threshold. So we can work fast, but now we must work slow. Maybe we need Staff Code Reviewers…highly compensated ones.
Such an interesting time to write software. Tools are solid (but imperfect), AI provides context, hints and can write the code by itself if you let it. (I prefer pair). And all this speed makes the PR board a complete nightmare.
I know we have AI assisted code review and it rocks at finding technical flaws like race conditions and edges. But it has no clue what good code looks like. Suggests awful changes and we are left with a huge board we cannot process.
"In every team, there are competent people who make the project possible. There are also people who essentially make it harder for everyone else. And now anyone can produce more code in a day than they used to in a year."
https://t.co/q3CkBCtpZP
Ever sit down to play a game and realize you are out of scoresheets…or you can’t find a pencil? Problem solved.
Coming very soon: Kweli
https://t.co/RQ7ZU3c8Lw
#BoardGames#CardGames#TabletopGames
Working on a little project and curious what everyone’s actually playing these days.
Flip 7? Ark Nova? Catan? Something else entirely?
Drop your current favorites below 👇
#BoardGames#CardGames#TabletopGames
This used to be an issue for different reasons (mostly abandonment) but the bright side is the cause of the issue (AI) is also the way out. It is so easy to build a single purpose library or module to replace the functions you use from a dependency you can no longer trust.
Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).
If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!
I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.
Feeling pretty swell about this mentality with all the supply chain attacks happening.