Cloudflare's security-audit skill for coding agents added 12,600+ GitHub stars this week.
No repo on GitHub Trending added more.
It's the skill that seeded Cloudflare's own vulnerability-hunting harness. It runs an audit in 6 phases:
1. Recon: map the architecture, trust boundaries and every input.
2. Hunt: isolated agents each take one slice of the code.
3. Validate: every candidate goes to a fresh agent that tries to disprove it.
4. Output: each finding is confirmed, needs validation, or rejected.
5. Verify: fresh agents re-check each final claim against the source.
6. Report: written only from the verified records.
Steal phase 3 even if you never install it: never let the agent that found a bug be the one that confirms it.
https://t.co/C0b6Lxjmjo
4 GitHub Repositories to Prepare for 4 Different Types of Software Engineering Interviews:
1. System Design Interviews: https://t.co/pkVpi6LxSV
2. Low Level Design Interviews: https://t.co/ewnEgFdlfF
3. Coding Interviews: https://t.co/oTez9H4sGh
4. Behavioral Interviews: https://t.co/NsN4Ki0wlz
♻️ Repost to help others in you network
Learn about Design Thinking with these Four Excellent Sketch Cheatsheets 🔥🔖
Four FREE Design Thinking Cheatsheets attached 🙌
Overview:
1. DESIGN THINKING OVERVIEW
UNDERSTAND & EMPATHISE
DISCOVER WHAT PEOPLE REALLY NEED. SENSE & SHARE THE SAME FEELINGS THAT OTHERS FEEL
2. SYNTHESIS
COLLATE YOUR UNDERSTANDING IN ORGANISED MANNER FOR SENSE MAKING AND CREATIVE INTERPRETATION
3. EMPATHY
COLLATE YOUR UNDERSTANDING IN ORGANISED MANNER FOR SENSE MAKING, DESIGN CHALLENGE DEANITION AND CREATIVE INTERPRETATION
4. IDEATION
UNLOCK IMAGINATION, UNFOLD POSSIBILITIES AND VISUALISE SOLUTIONS
by @auropradhan
#ux #uxdesign #ui #uidesign #productdesign #uxprocess #uxstrategy #design #designthinking #research #userresearch #uxresearch #usertesting #usability #usabilitytesting #prototyping #agile #mvp #startup #digital #ideation #userexperience #business #startup
This repository contains everything you need to become proficient in #DataAnalytics with 45 end-to-end implemented projects — compiled by @NainaChaturved8
https://t.co/4iaUN4PfTC
Here is the process to design the perfect database:
1- Design your database following the rules you learned at school.
2- Make sure you normalize every table.
3- Write a simple script that generates millions of fake rows.
4- Identify the most important queries that your application will execute on your data.
5- Measure how long each query takes. Any database system will let you measure this.
5- Start denormalizing your data. Break expensive relationships and bring the data together. Measure after every change.
Start following the rules. Measure. Then break the rules.
Frontend Unit Tests.
🟡 The Gold Standard 🟡
Everyone racing for top coverage.
But reality looks much much different.
When NOT to Write Frontend Unit Tests:
• PoCs/MVPs: Here today, irrelevant tomorrow.
• UI part that is changed a lot: Don't waste your time.
• Experimental features: Can change any minute.
• Basic static components: Not worth it.
• Overwhelming mocking: Value > Effort.
• Deadlines: Especially in startups.
• Limited resources: Business value first/early phase.
• Redundant scenarios: 100% coverage is not the goal.
• Backend is more important: Frontend is changing much more often.
When TO Write Frontend Unit Tests:
• Critical features: Some things just can't fail.
• Complex logic: Once stable of course.
• Reusable components: The Foundation.
• Regression prevention: When it breaks often.
• Set in stone features: Worth the effort.
• Documentation: Tests can be great for that.
• Pre-refactoring: Before embarking on refactoring.
• Integration points: Vulnerable places.
Business Perspective:
• User Focus: E2E reflecting customer experience.
• Cost Efficiency: E2E tests can catch critical bugs.
• Time Savings: Reducing emphasis on unit tests can speed up development cycles.
• Real-world Relevance: E2E tests in near-production environments offer tangible insights.
• Simplified Reporting: E2E results are often more digestible for non-technical stakeholders.
• Coverage Overkill: Extensive unit tests can be redundant with a strong E2E suite.
• Maintenance Overhead: Frontend changes might require frequent unit test updates.
Businesses often lean towards ROI.
E2E tests often provide clearer value.