bug-bounty529
xss291
rce161
google135
account-takeover121
bragging-post118
exploit100
privilege-escalation98
facebook96
open-source94
microsoft93
authentication-bypass89
csrf88
malware83
cve78
stored-xss75
access-control71
ai-agents66
web-security65
reflected-xss63
phishing59
writeup57
sql-injection51
input-validation51
ssrf51
smart-contract49
cross-site-scripting49
reverse-engineering49
information-disclosure48
defi48
privacy47
tool47
api-security46
ethereum45
apple43
vulnerability-disclosure42
web-application40
ai-security38
cloudflare38
dos38
responsible-disclosure37
burp-suite37
llm37
opinion37
web336
automation36
browser35
oauth35
remote-code-execution34
race-condition34
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