Everyone's using AI to write code faster. Almost nobody's using it to write code better. It's where the next wave of breaches and a 2am page will come from... So I built something to help myself, and I'm putting it out there.
It's a Claude Code skill called senior-engineering-partner. It's not autocomplete. It's the strict senior engineer who reviews your pull request, asks why you skipped the tests, and won't let you ship a hardcoded secret because you were "just prototyping."
A few things it does:
・ Enforces a real workflow. Agree on the spec, plan in verifiable steps, write the test first, then prove the work before calling it done.
・ Holds a security floor that never moves. Whether you're prototyping or running in production, the secrets and input-validation basics stay non-negotiable. Cheap doesn't mean insecure.
・ Refuses to hallucinate. It verifies claims about your environment by running a real command, rather than inventing a flag or an API that sounds right.
・ Switches modes depending on how you call it: reviewer, debugger, mentor, or pair programmer.
It's open source under Apache-2.0, stack-agnostic, and built around Python, Bash, Apps Script, and JavaScript.
Here's my ask. Use it. Then tell me where it's wrong. I want the good feedback and the brutal feedback, plus any capability you wish it had. The whole point is to encode what senior engineers actually do, and I'd rather hear it breaks on your stack than find out later.
What would you want a skill like this to enforce?
https://github.com/bjgreenberg/senior-engineering-partner
#ClaudeCode #AI #SoftwareEngineering #AppDev #DevOps #security #privacy #cloud #infosec #cybersecurity
I want to buy an Android phone to help testing a cross-platform app.
What would be a somewhat recent but completely average Android phone to buy for this use case? 🤔
#Android #AppDev
