Skip to content

Instantly share code, notes, and snippets.

View aljab012's full-sized avatar

Alhaitham Al Jabri aljab012

53 followers · 81 following
View GitHub Profile
@CarlosDomingues
CarlosDomingues / python-poetry-cheatsheet.md
Last active July 12, 2024 17:05
Python Poetry Cheatsheet

Create a new project

poetry new <project-name>

Add a new lib

poetry add <library>

Remove a lib




  


  




    


          
    

      

        
        

          

              @bradtraversy
          

          

            
                bradtraversy
                / pipenv_cheat_sheet.md
            
            

              Last active
              July 7, 2024 20:34
            

              
                Pipenv cheat sheet for common commands
              
          

        

      

        

  

      

    
Pipenv Cheat Sheet


Install pipenv


pip3 install pipenv



Activate


pipenv shell




  


  




    


          
    

      

        
        

          

              @dmsul
          

          

            
                dmsul
                / vim_crash_course.md
            
            

              Last active
              July 7, 2024 23:28
            

              
                Vim Crash Course
              
          

        

      

        

  

      

    
NOTE: Specific examples given for options, flags, commands variations, etc., are not comprehensive.


NORMAL MODE


Vim has 2 main "modes", that chance the behavior of all your keys. The default mode of Vim is Normal Mode and is mostly used for moving the cursor and navigating the current file.


Some important (or longer) commands begin with ":" and you will see the text you enter next at the bottom left of the screen.


:q[uit] - quit (the current window of) Vim. ("Window" here is internal to Vim, not if you have multiple OS-level windows of Vim open at once.)

:q! - force quit (if the current buffer has been changed since the last save)

:e[dit] {filename} - read file {filename} into a new buffer.



  


  




    


          
    

      

        
        

          

              @joepie91
          

          

            
                joepie91
                / .md
            
            

              Last active
              April 12, 2024 16:08
            

              
                Prefix codes (explained simply)
              
          

        

      

        

  

      

    
A "prefix code" is a type of encoding mechanism ("code"). For something to be a prefix code, the entire set of possible encoded values ("codewords") must not contain any values that start with any other value in the set.


For example: [3, 11, 22] is a prefix code, because none of the values start with ("have a prefix of") any of the other values. However, [1, 12, 33] is not a prefix code, because one of the values (12) starts with another of the values (1).


Prefix codes are useful because, if you have a complete and accurate sequence of values, you can pick out each value without needing to know where one value starts and ends.


For example, let's say we have the following codewords: [1, 2, 33, 34, 50, 61]. And let's say that the sequence of numbers we've received looks like this:




1611333425012





  


  




    


          
    

      

        
        

          

              @wojteklu
          

          

            
                wojteklu
                / clean_code.md
            
            

              Last active
              July 24, 2024 12:04
            

              
                Summary of 'Clean code' by Robert C. Martin
              
          

        

      

        

  

      

    
Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.




General rules


    

  1. Follow standard conventions.
    2. 

  2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
    3. 

  3. Boy scout rule. Leave the campground cleaner than you found it.
    4. 

  4. Always find root cause. Always look for the root cause of a problem.
    5. 



Design rules



  


  




    


          
    

      

        
        

          

              @scottjbarr
          

          

            
                scottjbarr
                / emacs-cheatsheet.md
            
            

              Last active
              March 17, 2020 04:33
            

              
                Emacs Cheatsheet
              
          

        

      

        

  

      

    
Emacs Cheatsheet


C : Control key


M : Meta key


General


C-g - Exit command



  


  




    


          
    

      

        
        

          

              @hofmannsven
          

          

            
                hofmannsven
                / README.md
            
            

              Last active
              July 16, 2024 01:30
            

              
                Git CLI Cheatsheet