Usually you shouldn't roll your own: - search algorithm - encryption - auth - credit card handling - billing - caching systems - logging framework - csv parsing - html parsing - URL parsing - JSON/XML parsing - floating point math - timezones library - localization - internationalization - postal address handling Do it to learn, to get an appreciation of how hard the domain is. But please don't put it in production unless you have a really, really, really good reason. 😅
If everyone employed this logic, we wouldn't have any of these technologies. 🙃 How do you feel about open libraries vs. closed services that offer these functionalities, Robert Roskam?
- PDF processing - anti-virus file scanning - chat-bot - email service
Postal addresses - that's a big one! Anyone storing addresses in a database, particularly as a SSOT, should be aware of address standardization APIs offered by the USPS. https://developers.usps.com/addressesv3
Truth be told, common authentication frameworks are high-value targets for hackers, and vulnerabilities may be secretly discovered in them. Therefore, in some cases, building your own authentication system if you have the necessary expertise may be a better option.
So true.! Also true - You should use Nimble to build production grade stuff that actually scale Uriel Knorovich
Ah, billing 🥰
We should not forget also using microservices for 10 monthly active users projects
A good reason is to say our application isn't just a very simple app but has all these features. 😂
Add both compiler and interpreter to your list.
Product Engineer (React | Typescript | Node.js | Cloud | LLM Integration)
1wAdd one more ‘really’ for documentation 😂