the engineer who built Claude Code just dropped a 28-minute video on how to write prompts that actually work
I've seen $300 courses that don't cover what he shows in the first 10 minutes
CLAUDE.md files, memory shortcuts, parallel sessions, prompting patterns
all in one video and completely free
works whether you're a developer, a beginner, or someone who's been using Claude for months
based on this, I put together 18 things you can copy and use in Claude today
full guide in the article below
🚨 Anthropic just showed a 24-minute workshop on how to actually do prompts for Claude.
Taught by the people who built it.
Free. No registration. No paywall.
I've seen $300 courses that don't cover what they teach in the first 8 minutes.
Watch it and bookmark it now.
Most developers can't explain how Single Sign-On (SSO) works.
This was one of my favorite questions during technical interviews. I love to ask about it because it's not a trivial topic.
Here is a 5-minute overview of how Single Sign-On works.
We all hate passwords; the less we use them, the better, and SSO helps with that.
When you log in to Google once and visit YouTube, Gmail, Drive, and any other connected service without re-entering your password, three players are working behind the scenes:
• A user trying to access an application. You, in this case.
• The application you want to access. For example, YouTube.
• An Identity Provider (IDP) that will verify your identity. Google, in this case.
Here is what happens when you try to access one application for the first time:
1. You try to log in to YouTube, and the application redirects you to the Identity Provider (IDP) for authentication.
2. The IDP (Google) checks your credentials and confirms your identity. It creates a new session for you on its server and sets a session cookie in your browser.
3. The IDP also creates a token for YouTube—a small piece of data that contains information about your identity.
4. Your browser grabs the token and presents it to YouTube.
5. YouTube checks the token, and if it is valid, lets you in.
But then you want to access Google Drive:
1. You go to Google Drive, and the application redirects you to the IDP.
2. The IDP recognizes that you are still logged in because you have the session cookie. It doesn't need to ask for your credentials.
3. Instead, the IDP generates a new token for Drive.
4. Your browser grabs the token and presents it to Google Drive. If the token is valid, Drive lets you in.
You can now access multiple applications without re-entering your password. This is probably one of the best things we've invented since sliced bread!
But, of course, implementing Single Sign-On is a nightmare! If you are a developer, don't try to reinvent the wheel. I've been implementing SSO since dinosaurs were around, and I can tell you you want to check out @auth0.
Auth0 makes implementing SSO 100x easier. They just updated their free plan, and you get a lot without having to pay a single cent. 25,000 monthly active users, unlimited social connections, and you can go to production with custom domains. FOR FREE!
They are sponsoring this post. To save your time, keep your sanity, and have a really solid and secure solution, head over to their website:
https://t.co/P0Z1JM0q4S