K/Q and vibecoded doesn't sounds good. I used Q with KDB+ for trading and we should ensure to have the right data / calculus as tiny errors might have huge impact ($).
LoopBack 3
picture recognition
I definitely don't like LoopBack in many ways : - custom relationship (hasMany - hasOne - belongsTo - etc.) - lack of documentation - readability - overriding and custom model methods - console output in bottom banner -…
Here is a link fyi : https://developers.google.com/web/tools/lighthouse/audits/no... Here is the rel attribute desc : https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes... where you will find an explanation :…
Why don't you use Git and multiple work stations ?
404 in the page
We need more information about you and your team
That's right ! Thanks for this accuracy and for sharing. Maybe you can create your own tool which takes good from both architectures ? ;)
I never use serverless because micro-services always works perfectly. Im lazy Thanks for sharing ! I think I won't switch to serverless (maybe this architecture require a specific use case ?)
K/Q and vibecoded doesn't sounds good. I used Q with KDB+ for trading and we should ensure to have the right data / calculus as tiny errors might have huge impact ($).
LoopBack 3
picture recognition
picture recognition
I definitely don't like LoopBack in many ways : - custom relationship (hasMany - hasOne - belongsTo - etc.) - lack of documentation - readability - overriding and custom model methods - console output in bottom banner -…
Here is a link fyi : https://developers.google.com/web/tools/lighthouse/audits/no... Here is the rel attribute desc : https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes... where you will find an explanation :…
Why don't you use Git and multiple work stations ?
404 in the page
We need more information about you and your team
That's right ! Thanks for this accuracy and for sharing. Maybe you can create your own tool which takes good from both architectures ? ;)
I never use serverless because micro-services always works perfectly. Im lazy Thanks for sharing ! I think I won't switch to serverless (maybe this architecture require a specific use case ?)