2,508 karma · joined January 22, 2008
One benefit of this is that continuations become trivial to implement (they're just a snapshot of the call stack at a given point).
Admittedly, almost all write-your-own-Lisp tutorials omit this, and use a bunch of recursive calls (in the implementation language) instead, which makes it very hard to do TCO, continuations or anything else that requires a real call stack (exception tracebacks, for example).
(I hope this answer makes sense; it's 3 in the morning here, so clarity might suffer a bit. ;-) But as it happens, I am writing a (hopefully non-toy) Lisp interpreter myself, in Go, so the question attracted my interest.
Could we please stop perpetuating this myth? If there really was a shortage, companies would fall over each other trying to hire anyone they could, not make it almost impossible to get hired by imposing ridiculous and long interview processes.
From what I have seen, many companies do indeed complain about a shortage of developers, yet their actions are completely at odds with this.
[1] http://www.bls.gov/ooh/computer-and-information-technology/s...
Remote: Yes
Willing to relocate: No
Technologies: Python, Delphi, Javascript, Android, C#, Xamarin, SQL Server, MySQL, Postgres, Scheme, Prolog, Windows, Mac OS X, Linux
Résumé/CV: http://aquila.blue/misc/resume.html
Email: zephyrfalcon@gmail.com
Remote: Yes
Willing to relocate: No
Technologies: Python, Delphi, Javascript, Android, C#, Xamarin, SQL Server, MySQL, Postgres, Scheme, Prolog, Windows, Mac OS X, Linux
Résumé/CV: http://aquila.blue/misc/resume.html
Email: zephyrfalcon@gmail.com
No, they don't. $7.25 * 40 * 52 = $15,080. Before taxes.
(40 hours, assuming you are lucky enough to get full-time, which is often not the case, esp. at fast food places and such. Also 52 weeks, which is more realistic since you're not likely to get paid vacation. The $7.25 is the current minium wage for the US as a whole [1], may differ per state.)
[1] https://www.google.com/search?q=minimum+wage+us&oq=minim
Remote: Yes
Willing to relocate: No
Technologies: Python, Delphi, Javascript, Android, C#, Xamarin, Scheme, Prolog, SQL Server, MySQL, Postgres
Résumé/CV: http://aquila.blue/misc/resume.html
Email: zephyrfalcon@gmail.com
0.0.0 is kind of weird... for some reason it suggests to me that zero lines of code have been written so far. (If there was code, the version number would have been higher.) But this is obviously not the case here. I do wonder what versions they used before this release?
Then again, I know of at least one non-trivial project that used negative version numbers... I guess, in the end, it just means what the developers say it means.
I'm talking about things like, what happens if you press this button; is this calculation correct; does this lookup give me the desired results; does X get stored in the database correctly (or retrieved from it); etc. I don't know of any type system that lets you check these things.
(Also, I assume s/strongly/statically; Python is a strongly typed language. Granted, not everybody agrees about the terminology...)
No, but the idea is that such a method would be hard to test, considering it (presumably) does so much. So in order to test it properly, you are encouraged to break it up into smaller methods. (Whether somebody actually does that is a different story, of course...)
I'm not sure where you got that information. You don't actually write tests to catch types. You write tests to check behavior. While it is possible that actual type errors come out of the woodwork while doing that, that is not the reason why the test was written in the first place; and after fixing such a type error, the test itself is still valid (again because it is making sure that the code exhibits the desired behavior).
I don't think I have EVER written a test just to check for types (in Python). Neither do I pepper my code with 'assert isinstance(x, some_class)' because it just goes against the grain of a dynamically typed language.
For an extrovert, yes. :) Or for the introvert who knows these things and knows how to do them credibly. For some of us, it's neither easy nor obvious.
I have, of course, noticed these things too, in school- and work situations... If you are talkative, it's OK, but if you're not, you are "weird", "aloof", "arrogant", or people simply think you dislike them. Yes, you can learn to make superficial conversation, but personally it all feels really fake to me.
True, although I think that had more to do with making kids obedient, or expecting them to be obedient, rather than school being "designed for introverts". Also, putting a bunch of kids together in a room, and expecting them to speak up or do things in front of the class, certainly don't favor the introverted.
Yes -- and the problem is that very few places actually teach these skills to introverts. Rather, you are supposed to already know them.
"This is like saying that people who don't enjoy physical activity should skip P.E. class -- in both cases there is both a developmental and health component at play."
It's funny you should bring up PE here, because the same mechanism is usually at play there. PE classes don't focus on the kids who are bad at sports. They focus on those who are already good at it, for whatever reason.