A guide that explains general ideas and patterns behind a multi-tenant system using Firestore, Security Rules and Cloud Functions.
Humans seek a state of psychological consistency in which our mental attitudes and actions match up. How do we act when this is not the case?
Asynchronous systems need to be able to notify their users about changes — which can be persisted as events and distributed through webhooks.
I recently read the book „The Subtle Art of Not Giving a F*ck“ by Mark Manson — these are my key learnings and thoughts from it.
D stands for Dependency Inversion and promotes depending on abstractions rather than concrete implementations.
I stands for Interface Segregation Principle and encourages only the implementation of behaviour that is actually required.
L stands for Liskov Substitution Principle and encourages architectures that allow exchanging base classes for their subclasses without breaking things.
O stands for Open Closed Principle and promotes extension over modification.
S stands for „Single Responsibility“, which means to do only one thing, but do it well.
As early as in the 1940s people started to think about how to mimic the human brain. But only since about 2006 has the right hardware and large amount of collected data enabled us to effectively pursue and research this option.
Laravel provides neat testing helpers for working with the filesystem — however if you run your tests in parallel, issues are inevitable.
Nova allows to extend most of its parts through custom composer packages. This is great for easy sharing with the community, however this is not so great if you need a truly custom extension.
Looks like you've reached the end :)