bug-bounty529
xss289
rce159
google129
account-takeover120
bragging-post118
privilege-escalation97
exploit95
open-source94
facebook92
authentication-bypass89
csrf88
microsoft85
stored-xss75
malware75
cve73
access-control71
ai-agents66
web-security65
reflected-xss63
writeup56
phishing54
input-validation51
ssrf51
sql-injection51
cross-site-scripting49
smart-contract49
defi48
information-disclosure48
tool47
privacy47
reverse-engineering46
api-security46
ethereum45
vulnerability-disclosure42
apple41
web-application40
ai-security38
cloudflare38
burp-suite37
responsible-disclosure37
opinion37
llm37
dos36
automation36
oauth35
web335
lfi34
race-condition34
remote-code-execution34
0
1/10
This article critiques the overuse of the Single-Responsibility Principle in software design and proposes Siedersleben's blood group law as a practical alternative framework for categorizing components into reusable groups (Generic, Technical, Domain, and anti-patterns) to minimize code while maximizing use cases.
software-architecture
solid-principles
code-design
single-responsibility-principle
component-design
reusability
SOLID
Siedersleben
Quasar Architecture Style
Lodash
Bluebird
Luxon
nconf
knex
metascraper
jsonwebtoken
passport