1,201 karma · joined February 8, 2013
This excellent paper is by Karl N. Llewellyn and is called "Remarks on the Theory of Appellate Decisions and the Ruled or Canons about how Statutes are to be Construed"[1] I once read almost the whole thing, and the following quote from the first page sums up his main point pretty nicely.
"The major defect in [the legal system] is a mistaken idea which many lawyers have about it—to wit, the idea that the cases themselves in and of themselves, plus the correct rules on how to handle cases, provide one single correct answer to a disputed issue of law. In fact the available correct answers are two, three, or ten. The question is: Which of the available correct answers will the court select—and why? For, since there is always more than one available correct answer, the court always has to select."
IIRC, he discusses the role of precedent as an important aspect of deciding how to apply the law, but also the ability of a judge to decide to overturn a precedent for a wide variety of reasons. He also discusses the role played by the intention of law makers when passing law, which is ultimately a subjective judgment made by a person, and which is not spelled out in the actual written law itself.
The paper is considered something of a classic, and I would encourage everyone to take a look at it.
[1] http://mtweb.mtsu.edu/cewillis/Hermeneutics/Llewellyn%20on%2...
Productivity in programming is measured from the time you start a project till the time you finish. So much time is often spent trying to find and fix bugs, and being productive is all about writing code in a way that minimizes the amount of bugs that show up, and being able to quickly find and fix them when they do.
Writing code at the optimal level of generality is a major factor, No amount of editor tricks can make up for choosing the wrong level of generality to write your methods. Too much generality and you are wasting time, too little and you have to deal with a bunch of special cases, or else rewrite large portions of code at some point.
It's important to be able to learn things very quickly on the spot when you have no other choice, but it's better to be able to immediately deal with situations without having to incur all of the productively losses that comes with doing that. So much time is saved by being able to get the algorithm's and the numbers right on the first try.
It's also about a psychological battle of how hard you can push yourself without burning out, which is no trivial matter.
Once you are good at all that, then basically it's nice to also be able to pick up an extra few seconds here and there with a keyboard shortcut, an editor trick, or some precision mouse mechanics.
Maybe the problem isn't that most game designers suck, but that the major studio's have calculated that they can be more profitable if they don't bother spending the time and money it takes to make games that are actually well designed.
I suppose the reason I made my comment is one day I realized that it was actually a positive thing to "procrastinate" for a non-trivial amount of time before I even start working; as long as I actually do start before it gets out of control.
I suppose it was also helpful for me to get rid of the psychological baggage of feeling guilty about "procrastinating", and I wanted to give a word of caution about not over-compensating by going to an extreme of never taking a break, or taking too short of a break, because of feeling guilty or afraid of not being able to start working again if you do.
I absolutely love to procrastinate and it's very important to me. Actually I am procrastinating by writing this comment right now. Allow me to explain:
When I program, or do math, it's very important to me to have a clear head; and I take procrastinating very seriously because I know if I don't do certain things then I will have a hard time concentrating when I sit down to work, and that will prevent me from going into "the zone", or achieving what some people call "flow".
There is such a huge difference between not only the amount of work I get down, but the quality of that work, when I am in the zone as opposed to when I am not; and procrastinating is sort of a ritual for me. I have to have a clean room, I have to have my desk nice and tidy, I have to have a glass of water, or a cup of coffee, in the same place on my desk that it always goes, I need to open my notebook to review my notes from the day before, and so on. Maybe I'm slightly OCD, but I do these things on purpose as part of a ritual to get into the zone.
If I have an urge to check HN, I log in and do it. Otherwise when I start working I have an awful nagging thought that won't go away saying "hey you know, there is probably something awesome on HN!" and the fact is I need that extra space in my brain to load up all the details of the code I am working on.
Then I load up my music playlist, put on my headphones, fire up my code editor, and the next thing I know it's 4 hours later and my stomach is growling because I have completely lost track of time. Guess what? Time to procrastinate again, otherwise productivity starts trailing off, and the quality of the work suffers.
Sometimes I keep coding anyway, but then I come back the next day and say to myself, "Jesus, what was I thinking when I wrote this crap! I wish I hadn't closed Eclipse before I went to bed, because now I can't ctrl-z out of this mess!" So it's actually a bad idea for me to keep programming when I start getting distracted by random things because then I have to waste a bunch of time the next time I sit down, just undoing a bunch of crap.
I love procrastinating, and I don't consider it a form of laziness at all, but just for a different reason.
Lets think about it with this example: if it takes a worker 2 hours to make product X, but then a new technology comes along which makes it only take 1 hour to make product X, then the value of labor has doubled.
Then the owner has a choice, he can either double all the salaries of his employees and have the same income for himself, or else fire half his employees and double his profit.
This example shows that unemployment is not a result of new technology, but of choices made by people who have the most power in a society.
The point of life should be to work on a job that you find fulfilling. If the boring things are all automated, then everyone can have a job they enjoy, and sitting around all day doing nothing gets boring really fast.
Turing's Cathedral has a ton of really interesting historical details about the history of computers, and LOTS of details about the political fight Von Nueman waged to even be allowed to work on the first computers at IAS. I didn't realize how big a role he actually played, and I would encourage people to read that book because its pretty good.
David Hilbert wanted to redo mathematics from square one, basing everything on set theory, axioms, and rigorous proofs. In 1900, Hilbert gave his famous address where he stated the Hilbert Problems. One of these was to prove that mathematics is "complete" in the sense that every possible statement is either provable or disprovable from the axioms.
In an effort to solve this problem, Alan Turing wrote his famous paper "On Computable Numbers" where he conceived for the first time his "Turing Machines". Although his approach didn't work to solve the Hilbert problem, it greatly inspired Von Nueman who at the time was pretty much working on pure mathematics.
Godel came along and proved that mathematics is not "complete", because there are some statements about natural numbers which cannot be proved or disproved from the axioms, but rather are undecidable.
Von Nueman was so upset by Godel's result that he decided he no longer wanted to work in pure mathematics, because if it's not complete then whats the point anyway. Instead he decided to work on applied math and physics. Since he loved the work of Turing, he wanted to build a physical Turing Machine to help out with computations, and he figured there would probably be a lot of other uses for such a machine that no one had thought of yet, and that would only become apparent once the machine was built.
While at the Institute for Advanced Study, Von Nueman fought a hard political fight to secure funding and permission to build the first computers, the MANIAC and the ENIAC, to the horror of the faculty at the time, including Einstein.
Since I am posting this at 4:30am in a thread that is 12 hours old, I will be happy if someone reads it :P
[1] http://books.google.com/books/about/Turing_s_Cathedral.html?...
If pi is defined as the ratio of the circumference of a circle to its diameter, then a gravitational field indeed changes pi, and by measuring this change, its possible to measure the strength of gravity.
A quick way to understand this is to realize that "straight lines" (geodesics) are defined as the path taken by a beam of light, and gravity causes the path of light to bend. Measuring the difference is the same as measuring the curvature of space time, which when multiplied by a constant IS the strength of the gravitational field according to general relativity.
Another way to see it: take a sphere and draw a circle on it, then measure pi. You can determine the curvature of the sphere once you measure the difference with pi on a flat piece of paper.
"Eagles are Manwe’s birds, and they play a much more interventioinst role in the earlier ages because the Valar played a more interevtionist role in earlier ages of ME. The Eagles thus effectively withdraw in the Third Age other than for the intervention at Orthanc and at Mount Doom, as the Valar themselves no longer directly intervene-using instead the Istari, who themselves have strict limtations placed on their powers"
"I have been walking through mazes my whole life with my eyes closed, and I make progress by feeling the walls with my hands. In order to get through each maze I need to remember lots of facts about how the walls in the different mazes feel when I touch them. If I opened my eyes now, it would take too much time, and be too painful to adjust to the light. I never tried to open my eyes, and even though a lot of people keep telling me it's a lot easier to get through mazes with your eyes open, I think they are wrong. Besides, the few and far between times I get stuck, I can always ask one of the people who can see where I should go next. And if you think I need to keep my eyes open, then the next thing you are going to tell me is I should use my sense of hearing and smell too."
Second of all, like you said, you can get the "hack" done without math. I would say the less hacks you have to use in your programs the better, and the best practice is to code at a high enough level of generality that you don't need any hacks at all. Without math, so much time is spent (or wasted) tinkering around, and you don't often end up with the optimal solution. Whereas a strong math background lets you skip all that tinkering, because you are able to properly plan a solution before you even write a single line of code.
"Thanks go to Ben Alpert for helping me understand the linear algebra / cross-product magic ...I ended up going w/ a cruder slope-based approach, mostly b/c I’ve lost all intuitive understanding of linear algebra"
Let that be a wake up call to all of the programmers who continue to claim that you can "get away" with out knowing much math. In this case, the author admits that he used an inferior solution at first because it was based on the math he was comfortable with.
There are so many reasons that math is important in programming, but this article added another item to my list, namely: the level of math that you are comfortable with heavily informs and influences the various options available to you in forming a plan of attack against all types of problems, even those as simple as a drop down menu on a website.
Computer predictions seems to work, but only get you half way there. I don't trust them because they are from a computer, but if I wrote the program myself I would trust it 100 times less. As with baseball, guessing the home team will win works at least half the time. Our recommendation engine works, and people read articles we recommend 4 times longer.
Conclusion: computer based recommendation engines are 50% placebo.
Is capital growth decoupled from job growth? No it isn't: all the jobs are simply being shipped off to places with forced/slave labor, abysmal working conditions, and don't even think about benefits.
Green jobs might help, sure, but why can't we manufacture clothes, computer chips, smart phones and tablets in america?