Skip to content

Instantly share code, notes, and snippets.

View jsimpson's full-sized avatar

Jonathan Simpson jsimpson

27 followers · 42 following
  • California
View GitHub Profile
@jsimpson
jsimpson / falsehoods-programming-time-list.md
Created August 23, 2022 06:54 — forked from timvisee/falsehoods-programming-time-list.md
Falsehoods programmers believe about time, in a single list

Falsehoods programmers believe about time

This is a compiled list of falsehoods programmers tend to believe about working with time.

Don't re-invent a date time library yourself. If you think you understand everything about time, you're probably doing it wrong.

Falsehoods

  • There are always 24 hours in a day.
  • February is always 28 days long.
  • Any 24-hour period will always begin and end in the same day (or week, or month).
@jsimpson
jsimpson / arel_cheatsheet_on_steroids.md
Created February 7, 2020 21:51 — forked from ProGM/arel_cheatsheet_on_steroids.md
Arel cheatsheet on Steroids

Arel Cheatsheet on Steroids

A (more) complete cheatsheet for Arel, including NamedFunction functions, raw SQL and window functions.

Tables

posts = Arel::Table.new(:posts)
posts = Post.arel_table # ActiveRecord

Table alias




  


  




    


          
    

      

        
        

          

              @jsimpson
          

          

            
                jsimpson
                / custom_game_engines_small_study.md
            
            

              Created
              April 24, 2020 21:58
                — forked from raysan5/custom_game_engines_small_study.md
            

              
                A small state-of-the-art study on custom engines
              
          

        

      

        

  

      

    
CUSTOM GAME ENGINES: A Small Study


a_plague_tale


A couple of weeks ago I played (and finished) A Plague Tale, a game by Asobo Studio. I was really captivated by the game, not only by the beautiful graphics but also by the story and the locations in the game. I decided to investigate a bit about the game tech and I was surprised to see it was developed with a custom engine by a relatively small studio. I know there are some companies using custom engines but it's very difficult to find a detailed market study with that kind of information curated and updated. So this article.


Nowadays lots of companies choose engines like Unreal or Unity for their games (or that's what lot of people think) becaus



  


  




    


          
    

      

        
        

          

              @jsimpson
          

          

            
                jsimpson
                / bash_profile
            
            

              Created
              March 3, 2020 22:46
            

          

        

      

        

  

    
    


        



  


  

        

          
          export PATH="/usr/local/opt/coreutils/libexec/gnubin:/usr/local/bin:$PATH"
        

        

          
          export MANPATH="/usr/local/opt/coreutils/libexec/gnuman:$MANPATH"
        

        

          
          

        

        

          
          HISTCONTROL=$HISTCONTROL${HISTCONTROL+:}ignoredups
        

        

          
          HISTCONTROL=ignoreboth
        

        

          
          export HISTIGNORE="&:[ ]*:exit"
        

        

          
          shopt -s histappend
        

        

          
          export HISTFILE=~/.long_history
        

        

          
          export HISTSIZE=9999
        

        

          
          export HISTFILESIZE=9999
        

  





    


  




    


          
    

      

        
        

          

              @jsimpson
          

          

            
                jsimpson
                / octal_x86.txt
            
            

              Created
              January 12, 2020 06:39
                — forked from seanjensengrey/octal_x86.txt
            

              
                x86 is an octal machine
              
          

        

      

        

  

    
    


        



  


  

        

          
          # source:http://reocities.com/SiliconValley/heights/7052/opcode.txt
        

        

          
          From: mark@omnifest.uwm.edu (Mark Hopkins)
        

        

          
          Newsgroups: alt.lang.asm
        

        

          
          Subject: A Summary of the 80486 Opcodes and Instructions
        

        

          
          

        

        

          
          (1) The 80x86 is an Octal Machine
        

        

          
             This is a follow-up and revision of an article posted in alt.lang.asm on
        

        

          
          7-5-92 concerning the 80x86 instruction encoding.
        

        

          
           
        

        

          
             The only proper way to understand 80x86 coding is to realize that ALL 80x86
        

  





    


  




    


          
    

      

        
        

          

              @jsimpson
          

          

            
                jsimpson
                / stimulus.md
            
            

              Created
              September 16, 2019 19:36
                — forked from mrmartineau/stimulus.md
            

              
                Stimulus cheatsheet
              
          

        

      

        

  

      

    
  


  




    


          
    

      

        
        

          

              @jsimpson
          

          

            
                jsimpson
                / Principles-of-Adult-Behavior.md
            
            

              Created
              April 19, 2019 16:48
                — forked from hernamesbarbara/Principles-of-Adult-Behavior.md
            

          

        

      

        

  

      

    
Principles of Adult Behavior


    

  1. Be patient. No matter what.
    2. 

  2. Don’t badmouth: Assign responsibility, not blame. Say nothing of another you wouldn’t say to him.
    3. 

  3. Never assume the motives of others are, to them, less noble than yours are to you.
    4. 

  4. Expand your sense of the possible.
    5. 

  5. Don’t trouble yourself with matters you truly cannot change.
    6. 

  6. Expect no more of anyone than you can deliver yourself.
    7. 

  7. Tolerate ambiguity.
    8. 

  8. Laugh at yourself frequently.
    9. 




  


  




    


          
    

      

        
        

          

              @jsimpson
          

          

            
                jsimpson
                / agile-vs-fragile-summary.md
            
            

              Created
              April 18, 2019 04:51
                — forked from teohm/agile-vs-fragile-summary.md
            

              
                Agile vs Fragile - Summary
              
          

        

      

        

  

      

    
Agile vs Fragile - Summary


My personal notes on Brian Copeland's blog series: Agile vs Fragile


(If you are unable to access the blog post, try using a US proxy or web-based proxy service e.g. http://hideme.be)


1) Deliver value to customer


    

  • Agile: focus on deliver valuable software to customer
    • 

  • Fragile: focus on meeting delivery period
    • 




  


  




    


          
    

      

        
        

          

              @jsimpson
          

          

            
                jsimpson
                / gist:8f01bacf3ab0c5d37bc77e7f52359ca8
            
            

              Created
              February 23, 2019 21:55
                — forked from tomwwright/gist:f88e2ddb344cf99f299935e1312da880
            

              
                Dell XPS 15 9560: Ubuntu 17.10 + Nvidia 384.90 + Nvidia Prime (No Bumblebee) https://medium.com/@tomwwright/better-battery-life-on-ubuntu-17-10-4588b7f72def
              
          

        

      

        

  

    
    


        



  


  

        

          
          # perform a fresh install of Ubuntu 17.10
        

        

          
          

        

        

          
          # upgrade the kernel to v4.13.10
        

        

          
          mkdir ~/kernel-v4.13.10
        

        

          
          cd ~/kernel-v4.13.10
        

        

          
          wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.10/linux-headers-4.13.10-041310_4.13.10-041310.201710270531_all.deb
        

        

          
          wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.10/linux-headers-4.13.10-041310-generic_4.13.10-041310.201710270531_amd64.deb
        

        

          
          wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.10/linux-image-4.13.10-041310-generic_4.13.10-041310.201710270531_amd64.deb
        

        

          
          sudo dpkg -i *.deb
        

  





    


  




    


          
    

      

        
        

          

              @jsimpson
          

          

            
                jsimpson
                / triangle-workflow.md
            
            

              Created
              February 22, 2019 17:53
                — forked from anjohnson/triangle-workflow.md
            

              
                Triangle workflows
              
          

        

      

        

  

      

    
Triangle Workflows


A triangle workflow involves an upstream project and a personal fork containing a development branch of the project.
This configuration makes git pull merge changes from the upstream but git push send local commits to the personal fork.
However those config settings only work on relatively recent versions of git; 1.7.9 doesn't support the required remote.pushdefault config setting so you will have to explicitly tell git push which remote to push to.


This gist does not attempt to explain exactly what these commands do, it's intended as a cheat-sheet/reminder.


To set up a project area