bug-bounty528
xss287
rce155
google126
account-takeover120
bragging-post118
privilege-escalation96
open-source94
exploit93
facebook91
authentication-bypass89
csrf88
microsoft83
stored-xss75
malware74
cve71
access-control71
ai-agents66
web-security65
reflected-xss63
writeup56
phishing53
input-validation51
sql-injection51
ssrf51
smart-contract49
cross-site-scripting49
defi48
information-disclosure48
privacy47
tool47
reverse-engineering46
api-security46
ethereum45
vulnerability-disclosure42
apple40
web-application40
ai-security38
responsible-disclosure37
burp-suite37
opinion37
cloudflare37
llm37
automation36
dos36
web335
oauth35
lfi34
remote-code-execution34
idor33
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