>Single Responsibility Principle
>Open/Closed Principle
>Liskov Substitution Principle
>Dependency Inversion
>Don’t repeat Yourself
>>61256450
>>Single Responsibility Principle
Sound as an aspiration
>>Open/Closed Principle
Not fit for real world
>>Liskov Substitution Principle
Too stupid to understand implications
>>Dependency Inversion
Dependency injection? Sound.
>>Don’t repeat Yourself
Very sound
>>61257063
Dumbass
>>61257237
That's the only thanks I ever got. Why are people so fucking ungrateful?
>big data
>revolutionary blockchain technology
>made with cofee and love
>>61257303
>made in california with pride
>>61257063
What does that have to do with sound?
>>61256450
They sounds solid to me.
>>61257382
Dumbass
>>61257464
What sound do solids make and how is it relevant?
>>61257382
>>61258323
The word 'sound' has more than one meaning.
It does not mean only the vibration of air through your eardrums.
>blast processing
>not giving variables arbitrary one to three character names
>event driven architecture
>structured programming
>workplace manners
>web development
>Object oriented programming
>>61258366
A real programmer would have declared the meaning of the word before using it.
>functional programming
All programming is functional. If it wasn't then people wouldn't be using it baka
>>61258586
/thread
>>61257063
>Liskov Substitution Principle
It's just like, interfaces and shit and if two objects of a different type have the same interface they should both work properly when being replaced with each other. No?
> Dependency Inversion
Pretty much the spring-core framework.
> Domain Driven Design
> Event Sourcing
> Message passing
> DevOps
>Rub a dub dub, thanks for the grub!
>deployment story
>Velocity
>>61258839
It's in the standard library
>agile
>Forward-deployed Engineers
>open-plan office
>>61256450
>Single Responsibility Principle
Works for functional programming, not POO.
> Open/Closed Principle
Absolutely retarded and devoid of fundament.
The other three rules are good advice tho.