@kaarmann I got scammed, it hurts to say it, but I've been a victim of social engineering and they managed to steal money from my bank account.
All I got from @Wise was "we didn't see anything wrong, so no refund" and they stopped responding me.
Worst experience in my life.
Parcel delivery firm DPD have replaced their customer service chat with an AI robot thing. It’s utterly useless at answering any queries, and when asked, it happily produced a poem about how terrible they are as a company. It also swore at me. 😂
PSA
Images circulating of Defence Forces vehicles in Dublin City Centre are not from this evening, but from a separate routine operation and have no connection to this evening's events.
We ask everyone to be sensitive to the spreading disinformation, and to take care.
@matiasfha@mattpocockuk I think the case by my colleague was that you should "always" pass the Error as a union type alongside the data, it didn't sound right to me. Sure, in some cases it might be useful, but I assume that the Promise itself will handle the Error
@mattpocockuk do you think is a good practice to set as a return value of a function that resolve in a promise, to also set the Error as a return value if the function might throw an error? Like this Promise<MyData | Error>
@mattpocockuk That's what I thought, but talking with another dev this morning planted the seed of doubt hehe
Thanks for responding and have a great weekend
Trying out #nestjs , and I'm already disappointed as by default when you create a new project they set the version as 0.0.1.
Get your SemVer straight gents, you are not patching an empty folder, you should always start with 0.1.0.
#webdevelopment@nestframework
Another video on YT where somebody starts a software with 0.0.1 version, which is silly, because it's like you are saying "I'm fixing an empty folder". You should never start a software with that version, use 0.1.0 instead, as stated here https://t.co/MWps87cdPp
@csdojo404 You still need to know CSS, the latter is a framework, it can speed up development, but it's the same as saying "React or Javascript", not a proper comparision IMHO
@browserstack any chance we are going to see support for Cypress 11/12 soon? Working with NX 15 and I have to downgrade to Cypress 10 only because of BrowserStack