Earlier quoted context omitted.
Chiming in as someone who has lived decades in both South East US and North East US. I've also never heard () called "brackets" only "parentheses". This includes in and out of programming circles. I assumed the comment saying "parens: ()" was talking about US, but the replies seem to be interpreting the opposite.
Never? You guys don't use the BEDMAS acronym in grade school for teaching order of operations? I've only ever called them brackets.
The $440M software error at Knight Capital (2019)
131–140 of 177 posts
Re: The $440M software error at Knight Capital (2019)
#132Re: The $440M software error at Knight Capital (2019)
#133Random, but I interviewed at Knight Capital for a software engineering position a few weeks before this all went down. I was in London, so the interview was done over the phone. Picture me in the evening, handwriting C to solve some problem (the fog of time too thick to remember what that problem was), then reading out what I'd written, semicolons and all, to the interviewer. Because of course there was no shared doc…
Re: The $440M software error at Knight Capital (2019)
#134Earlier quoted context omitted.
> sufficiently senior devs make 7 figures I can confirm, known firm, manager role, offer was $1,3M full cash.
Could anyone (successfully) apply for such a position with no referral but CV only?
Re: The $440M software error at Knight Capital (2019)
#135Earlier quoted context omitted.
like how Credit Suisse is going to reverse their Bill Hwang losses? I guess in this conversation we can't distinguish from irreversible asset value and liquidity issue to misdirected transactions that inherit partial reversibility. similarly, maybe you/they just don't see the headlines of thwarted attacks in DeFi that work specifically due to design considerations. I'll take the permission to fail. The rapid iteratio…
Where is this innovation happening? We’ve had crypto for 13 years now, and just yesterday we had people flat out losing 10k into the ether because their transaction “ran out of gas” without completing. Isn’t that plenty of time to develop systems that avoid basic issues like suddenly burning all your money?
For your strawman argument, all of their client side wallets told them “its not worth it bro”, the people did it anyway. Thats a consumer issue not a technology issue.
Re: The $440M software error at Knight Capital (2019)
#136Random, but I interviewed at Knight Capital for a software engineering position a few weeks before this all went down. I was in London, so the interview was done over the phone. Picture me in the evening, handwriting C to solve some problem (the fog of time too thick to remember what that problem was), then reading out what I'd written, semicolons and all, to the interviewer. Because of course there was no shared doc…
Same! Although I interviewed in person in their NYC office. I was very junior at the time and the team I interviewed with was awesome. I (luckily) didn't get the job. I did a few more interviews and accepted an offer from another company where I met my wife!
That really cheered me up this morning, I met my wife at work as well.
Re: The $440M software error at Knight Capital (2019)
#137Earlier quoted context omitted.
Same is true for blockchain smartcontracts, which have similar catastrophic consequences.
That truly is scary to me. I can easily* write advanced Solidity and could try to make something big. But I won't, because I know I would not be able to handle the stress and responsibility. One tiny logic error and millions lost. Thanks but no thanks. *The fact I believe I could easily do it is probably exactly why I'd end up making some huge mistake. ;)
Re: The $440M software error at Knight Capital (2019)
#138Is it just me, or was this one of the scarier statements in the article? High frequency trading does not seem to add anything, it's not a market instrument to balance anything. It's more like gambling with the odds slightly in your favor.
Oh course, I'm a laymen when it comes to high frequency trading and might totally wrong.
Re: The $440M software error at Knight Capital (2019)
#139Earlier quoted context omitted.
Are brackets different in American English? I'd say the Queen should order a second burning down of Washington but, the way things are going, the locals will probably get to it soon.
One difference is that we don’t have “round brackets” over here, only parentheses. (We do have “square brackets” however.)
Peace, man!
Re: The $440M software error at Knight Capital (2019)
#140Earlier quoted context omitted.
But don’t many (most?) US programmers call () parentheses? I assume non-programmers in the US call them brackets? 1.9M results: lisp "parentheses" -brackets 800k results: lisp "brackets" -parentheses I admit result counts are more similar if lisp is replaced with “python” or “golang”, but square brackets come up more often for those languages. Disclaimer: I am searching from google.co.nz, and I presume search result…
In my lifetime, “parentheses” has been the canonical way to refer to () in the US. “Brackets” is an umbrella term that can describe one or all of (), {}, and []. If you’re in a context where only one of the bracket types would normally be used, you can just call them “brackets.” Since many people never really use [] and {}, “brackets” casually refers to (). To disambiguate, you can call () “open brackets”, [] “square…
Together they are just brackets, not open brackets.