buff-a

>Ray tracing involves projecting light from the "eye" towards the scene, whereas in real life the light is being projected from the scene towards the eye.

I can't write a decent reply to this without having terrifying flashbacks of late night cramming for third year physics exams. But basically, raytracing's idea that "if it didn't hit your eye, who cares" is somewhat backed up by theory =)

Any good hacker will code around bullshit.

Of course there is evidence: the stock market wasn't invented until 1999. Before 1999, noone dared buy stocks because they were afraid they couldn't sell it later. Its historical fact.

This [1] was a joke.

This [2] was for real.

  [1] http://www.youtube.com/watch?feature=player_embedded&v=Qi_AAqi0RZM#%21

  [2] http://www.readwriteweb.com/enterprise/2012/03/how-casual-sexism-put-sqoot-in.php

I think you hit the nail on the head. The number of brogrammer entrepreneurs out there is huge. They are equivalent to Big Jims Baha XTReme Racing Shop that slaps lifted suspension on other people's 2WD Tundras.

But then there are a few start-ups who are designing and building fuel efficient diesel engines, or fully electric cars built from the ground up. These guys will absolutely know thermodynamics etc.

So if someone built "mycollegematehavingsex.com" and got 40,000 sign-ups via launchrock, who fucking cares. If they made twitter-for-squirrels and got 10,000,000 active users before the Great Nut Famine of 2015 killed the company, then there may conversations to be had.

Because its actually:

file.rb:

  require 'stuff'

  class foo
    def something
      alert = UIAlertView._alloc \
        ._initWithTitle _S("Hello"),
        :message, _S("I'm MobiRuby"),
        :delegate, nil,
        :cancelButtonTitle, _S("I know!"),
        :otherButtonTitles, nil
      alert._show
    end
  end

Instead of

file.h

  #import <stuff>
  @interface foo
    -(void)something:(BOOL)what andthen:(CGRect)thisthing
  @end

and then file.m

  #import <otherstuff>
  #import <yetmorestuff>
  #import "file.h"
  #import <oh shit is this in the right place?.h>
  #import <i think this is ok>
  #define SOME_HACK
  #import <this better come after that define up there.h>

  @implementation foo

  -(void)something:(BOOL)what butthen:(CGRect)thisthing
  {
   alert = [[UIAlertView alloc] 
                initWithTitle:@"Hello"
                message:@"I'm ObjC"
                delegate:nil
                cancelButtonTitle:@"I know!"
                otherButtonTitles:nil];
     [alert show];
  }

Fuck that.

1. Don't Repeat Yourself. Computer have more memory than 1986.

2. Don't forget to turn on warnings-as-errors, otherwise that code above will compile and then break because (of course you noticed) the method declaration doesn't actually match the declaration but the compiler doesn't care because its a brutal hack.

>Sounds like a reason not to buy a 2015 Honda.

Ah yes, the "free market" in action. That has worked so well for us in protecting our privacy, as evidenced by the plethora of commercial software with EULAs that respects the user's rights.

Or are you saying Richard Stallman is going to build us a car next?

Here's how it works:

1. Government is constitutionally forbidden from collecting this information.

2. Government observes that private corporations can collect this information.

3. Government grants private corporations immunity from prosecution and civil liability if it collects this information and hands it to the government. Threatens prosecution and civil liability if corporations fails to collect information and "something bad happens".

4. US Supreme Court pretends this is acceptable by ignoring "intent" and "consequences" and then goes on to uphold "intent" and "consequences" in every other case before it.

Honda Civic 2015 EULA:

23.1.23.44 (Page 198 of 301) "Your use of this vehicle grants us your irrevocable and permanent consent to download, transmit, or otherwise obtain the information contained in the onboard data recorder, and to share that data with third parties, including but not limited to law enforcement (without a court order), and marketing companies."

  * A wiki.
  * Google Docs.
  * Assembla.

Passing around a word document via email (or shared folder) makes about as much sense as passing around a C++ file, or the text of a facebook status.

"suffice it to say that among the people who actually design operating systems, the debate is essentially over."

A lesson for us all.

Like I said, its a book about dogma and cherry-picked studies. The dogma and studies were wrong. So if you want books about broken dogma and studies, read Code Complete.

Have to agree on Code Complete. The first edition was a load of waterfall bollocks and I couldn't believe anyone wrote code like that. It actively put me off a "proper" programming career. The second edition, apparently, reduced that shite, but by that point I wondered "if the author is just reproducing dogma, why bother?"

Sounds like someone said, "Make me a language that is hard to reverse engineer using IDA Pro".

But of course, to be allowed textual format for asset metadata, you have to buy the pro version. Or did they change that in 3.5?