We are investigating unauthorized access to GitHub’s internal repositories. While we currently have no evidence of impact to customer information stored outside of GitHub’s internal repositories (such as our customers’ enterprises, organizations, and repositories), we are closely monitoring our infrastructure for follow-on activity.
must read. doesn't matter if you're just entering the AI space, deep in the trenches building, or sitting in corporate wondering how to actually use this stuff.
this is the most complete claude breakdown i've seen and i've been using it daily for over a year.
covers:
- prompt engineering that actually gets elite outputs (not the generic "be specific" advice)
- which model to use and when (sonnet for 80% of work, opus when you need it to think)
- connectors, projects, research mode, the tools most people don't even know exist
- cowork, claude code, skills, plug-ins, the advanced stuff that changes how you work
if you're still defaulting to chatgpt for everything you're genuinely leaving performance on the table. claude's suite right now is unmatched for getting real work done.
bookmark this, but actually give it a read.
I know 90% of you bookmark fiens aren’t reading anything
Reflecting on what engineers love about Claude Code, one thing that jumps out is its customizability: hooks, plugins, LSPs, MCPs, skills, effort, custom agents, status lines, output styles, etc.
Every engineer uses their tools differently. We built Claude Code from the ground up to not just have great defaults, but to also be incredibly customizable. This is a reason why developers fall in love with the product, and why Claude Code's growth continues to accelerate.
I wanted to share a few ways we're seeing people and teams customize their Claudes.