71
trozan
7y

First law of javascript
Always open your browser console while developing
Second law
Never trust any javascript frameworks

Comments
  • 14
    I actually had to grab a mouse from a junior dev yesterday to open the console.

    10 mins of:

    Me: Ok, well lets see if there's any errors first...
    Him: OH I THINK I GOT IT NOW ... still error.
    Me: ... ok that didn't work so let's look at ...
    Him: OH IT MUST BE THIS ... still error.
    Him: Is it ...
    Me: *grabs mouse* oh look here at all this red ...
    Him: yeah but I think it's ...
    Me: AH YES IT SAYS RIGHT HERE EXACTLY WHAT THE PROBLEM IS

    Next time I go to his desk requires he fills out a form stating what appeared in the console
  • 1
    @practiseSafeHex why is he filling forulm for error messages? Is that a job requirement or something?
  • 1
    Don't trust in frameworks... I feel a need for a new Js framework you can trust in... I am going to call it trustworthify! (after current naming conventions)
  • 0
    And console log the shit out of everything
  • 0
    @practiseSafeHex sheesh. This is what you get if you have never had to stitch a webpage together from scratch.
  • 0
    @chasb96 If it mentions "trust" specifically, I'm going to be sceptical. Like the more of "democratic", "people's" or "republic" a country's name contains, the less those terms are justified.
Add Comment