Point being, these two things are orthogonal to one another.
625 karma · joined September 8, 2010
Point being, these two things are orthogonal to one another.
(1) correct an error in the question which renders it unsolvable (a_3 should be 9, not 7)
(2) guess that the invented term "convolution series" doesn't have anything to do with the mathematical concept of convolution[1]
(3) a_n = nth square number minus nth prime minus nth Fibonacci number.
Staring you right in the face!
What sequence is this and what is the justification for 28 being the next number?
[1] http://oeis.org/
What I'm saying is that making software good is hard. It takes a lot of different skills in addition to mere coding. Actually writing the code - pressing buttons on a computer to enter text into an editor - is one stage in a long process, and all of these stages are as important as each other.
Some of these are skills which you probably have! So calling yourself a mere coder is underselling yourself.
The clock was there to provide a Groundhog Day-like structure and a more genuine "approaching apocalypse" atmosphere. If you don't act, the world really does end. And by the end of the game, you've not just saved the world, but got to know everybody in the game world and made a difference in their lives. It was much more emotional game than other Zeldas, especially in comparison with its predecessor, Ocarina Of Time, which is what it had to measure up to.
I'm saying that pragmatically, unrecoverable errors don't need testing, and NASA's class of possible unrecoverable errors is much wider than any airline's. The fact that SpaceX feels the need to test so rigorously is a good sign about what they want to be "recoverable" and therefore about how safe their hardware is intended to be.
The main reason why I maintain that you do need some classroom time or tutoring or book-learning is that we are adults now.
...
> But still, nothing is as bad as the common "On Error Resume Next" that so many terrible VB programs start with.
Assuming "On Error Resume Next" does what I think it does, you can't complain about both of these at once.
say @{$ref}->[0];
This raises a deprecation warning for me. say @{$ref}[0];
This is technically correct, as the leading sigil "@" indicates you are returning an array, but since you're only returning one element in that array, this should probably be "${$ref}[0]" which returns a scalar only. say $ref->[0];
This the only form which I would consider correct or "clean".This example proves nothing about Perl's power, though. The fact that difficult and fiddly reference handling shenanigans are necessary to handle something as trivial as nested arrays and hashes shows quite the opposite.
This is a deliberate feature of Perl, whose motto is "There's More Than One Way To Do It".
Not to defend the practice, since the fact that there are 10 ways to do something means that (1) there's a 90% chance that when you look at somebody else's code you can't understand it, unless you learned all 10 ways and (2) at least 50% of those ways are objectively worse than the alternatives, but people will still use them because Perl programmers are encouraged to solve problems in whatever way they can.
Contrast with Python, where "There should be one - and preferably only one - obvious way to do it".
http://en.wikipedia.org/wiki/Global_Positioning_System#Restr...
Any links? I've found a few results from months ago, but results/feedback there weren't so positive.
http://design.canonical.com/2010/11/usability-testing-of-uni... http://lwn.net/Articles/438678/