- Detect secrets in code
- Identify secrets committed to version control
- Flag hardcoded credentials
- Identify missing authentication checks
- Detect improper authorization patterns
**Project Approach** | |
* Always check for a PRD (Product Requirements Document) before starting a new task and follow it closely | |
* Look for comprehensive project documentation to understand requirements before making changes | |
* Focus only on code areas relevant to the assigned task | |
* Prefer iterating on existing code rather than creating new solutions | |
* Keep solutions simple and avoid introducing unnecessary complexity | |
**Code Quality** |
Disclaimer: I'm in the Top 1% of StackOverflow contributors with 23,315 rep points.
I asked 1 high-quality question in 2024, and it was closed almost immediately, and I haven't engaged with the site since.
If someone with 20,000+ karma has their nicely-formatted questions closed so quickly, what must the newbies and rank-in-file encounter? This is probably a big reason why it's declining.
hi, i'm daniel. i'm a 15-year-old with some programming experience and i do a little bug hunting in my free time. here's the insane story of how I found a single bug that affected over half of all Fortune 500 companies:
If you've spent some time online, you’ve probably come across Zendesk.
Zendesk is a customer service tool used by some of the world’s top companies. It’s easy to set up: you link it to your company’s support email (like [email protected]), and Zendesk starts managing incoming emails and creating tickets. You can handle these tickets yourself or have a support team do it for you. Zendesk is a billion-dollar company, trusted by big names like Cloudflare.
Personally, I’ve always found it surprising that these massive companies, worth billions, rely on third-party tools like Zendesk instead of building their own in-house ticketing systems.
# SETUP # | |
DOMAIN=example.com | |
PROJECT_REPO="[email protected]:example.com/app.git" | |
AMOUNT_KEEP_RELEASES=5 | |
RELEASE_NAME=$(date +%s--%Y_%m_%d--%H_%M_%S) | |
RELEASES_DIRECTORY=~/$DOMAIN/releases | |
DEPLOYMENT_DIRECTORY=$RELEASES_DIRECTORY/$RELEASE_NAME | |
# stop script on error signal (-e) and undefined variables (-u) |
Some things you need :
When using this prompts, make sure to reply to Clyde's last message to continue the prompt. Everytime you ping Clyde, you start a new session.
These are my unstructured notes from the workshop. Read with caution (they're biased to my own interpretation).
1,000,000 Julian.com visitors Part 1: What's your objective for your article? Part 2: pair it with an objective objective + motivation good nonfiction = 70% novelty + 25% story + 5% style