I feel like it's a safe investment to avoid anything that can bring about a decision that drastic.
107 karma · joined October 12, 2011
I feel like it's a safe investment to avoid anything that can bring about a decision that drastic.
The comments here have corrected several problems with your understanding of functional languages, which leads one to believe that you have dabbled with them, but really don't know them all that well.
You are attempting to target a more experienced demographic of developer, but your article is catering to newbies. Masquerading as a guide to 'Ace a Startup Engineering Interview' is just salt in the wound.
We don't need any more guides on preparing for interviews. There are several good ones that exist, the advice that already abounds isn't going to expire anytime soon.
edit: Since there are password fields, I guess the question should have been "How many accounts _would_ be compromised by shoulder surfing?" I bet it's a truly insignificant number.
You forget Twitter has been dealing with technical debt for years. The fact that Twitter still runs on Rails and serves as much traffic as it does is testament to what the engineers there have built.
You're making a blanket statement about Twitter developing bad code because of a recent bug. It will be fixed.
Problems:
- Don't use buttons that look so 'bubbly'
- Bad colour scheme
- There are two different Facebook share buttons
- The copy on the about page is terribly written
- On the conversation page, I have to click 'track new conversation' to start fresh; big problem when there aren't any results, I'm essentially stranded with no 'obvious' action
- If I track @blah and @bleh, don't put me there under 'You', it's totally irrelevant to the conversation
What you've defined in the second paragraph is 'the likelihood that the shareholder decides the outcome of a vote'. You can call it control if you like, but don't make the mistake of assuming it's a very intuitive description of what the metric describes.
The first problem to be solved is that most introductory math education is still about calculating and not about applying mathematical principles to real problems. I think that being able to estimate a solution is a valuable skill, but for many problems with a high degree of precision (lots of decimal places) or large numbers, this just becomes problematic.
I'll definitely admit that at the end of a string of transformations of complex numbers, integrations, and other things, the last thing on my mind is guessing whether my solution is close. Understanding all the steps that lead up to that point is more crucial (and worth more marks!). The only thing I worry about is whether I typed the equation into the calculator correctly to get my final result.
That being said, when students are first learning about a new 'operator', like when learning division, multiplication, logarithms, and exponents, this could be a useful tool for enhancing a student's intuition about how that operator works. But after that, I'll stick with a normal calculator.
edit: Assumed an American is making the comment.