I have had hearing tests done and never had tinnitus before.
I also recently have got Airpods 2 for the last few months. Two weeks ago I started to get tinnitus. I thought it might be the sound canceling on the AP2 so I stopped using them. The tinnitus reduced.
Okay thank you, @fwir, @asdajksah2123, @lathiat
These points make much more sense however
If there is 1.75% of counterparty risk then why do bank transfers charge fixed rates of 0, 3 Euro and alike. If the underlying transfer is swift, sepa, wire then shouldn't this be the baseline?
That or give the option to accept the counter party risk for failure of transfers.
And there surely is signing methods that one could do as an escrow like service to mitigate most of the fee
This is an unmonitored mailbox. To contact DocuSign Support please visit support.docusign.com/contactSupport.
Ceci est une boîte aux lettres non surveillée. Pour contacter le service d'assistance de DocuSign, visitez le site Web support.docusign.com/fr/contactsupport.
Dies ist ein nicht überwachtes Postfach. Um DocuSign Support zu kontaktieren, besuchen Sie bitte support.docusign.com/de/contactsupport.
Esta é uma caixa de correio não monitorada. Para entrar em contato com o suporte da DocuSign, acesse support.docusign.com/br/contactsupport.
No responda a este mensaje automático. Para ponerse en contacto con el Servicio de asistencia al cliente de DocuSign, visite support.docusign.com/es/contactsupport.
"I'm a mechanical engineer, I've designed a ton of cool things, I do it every day. I deeply love it, and get better at it every day because I want to."
is a perfect example to as why anyone should pursue mechanical engineering. It's because you love it and managed to be compensated well.
The question is in the title. I addressed the title, but what I said still applies. There are less Mech engineers to hang out online because they swap to other fields.
I understand what you are saying but this is also a comment. No one is obliged to answer someones prompt when commenting.
Also my comment was based on my own experiences and the experiences of my peers. Out of a cohort of 300 engineers by the end of the course 80 to 90% dropped. Now when ever I meet someone who wants to go into engineering I tell them to step back do your own research, consider the ROI and determine if you want to do it because you love engineering or if you just want to make money.
There are always newspaper titles saying "we need more engineers", "where are all the engineers" or something similar.
To answer that. It's simple. The pay is bad.
We study for 4-5 years to get an Mech engineering degree and are promised 80K AUD+ starting salary (by many Australian universities).
The truth is you end up in debt whilst being removed from the work force for 4-5 years while studying. And you end up earning 40K AUD a year maybe a random few might earn 80K a year.
You end up in a position where you are highly trained and educated just to do CAD file translations. Surrounded by people who are not trained or educated who earn just as much or more then you.
Most Mechanical engineers (if smart) leave engineering and go to finance/software. I'd agree that the world needs more engineers to build things and make things more efficient and automated but the world wants and rewards administration and bureaucracy.
Hey all, didn't think this would be anything more than 1 or 2 comments.
I appreciate everyones passion and level of thought going into the replies. I will try read most of them.
Please note that if you reading this.
My intention of this post was to get a little rant off my chest and find out about potential solutions and gotchas about using GraphQl. It's unproductive attacking me or anyone else for character like "clearly not a senior developer" or "clearly never used API's before" because if anything this is about trying to find a solution and to save each other time.
Hey thanks for taking the time to find the resource
I have used this before this works to get past the errors but doesn't actually solve the issue GraphQL tries to solve. This just hides it so you have to deal with it months later.
- The consumers don't know what the JSON looks like unless they test the query or get told what the query is explicitly. This means that the schema definitions don't capture the problem that the graphql try's to solve "describe your data that you want"
- also some of the other languages that aren't Javascript don't have GraphqlJsonScalar
I think that supporting dictionaries/maps/tables as apart of the Graphql language spec could of been possible as the key and value types are static. They are also iterable so it should be fairly straight forward for a consumer to deal with the data returned.