Skip to content
View MassiGy's full-sized avatar
😇
ready to help
😇
ready to help

Organizations

@fairfield-programming

Block or report MassiGy

Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
MassiGy/README.md

@Massi Gy


BIO

Hi, I’m Massiles Ghernaout ( @MassiGy ), I am very glad that you are here, I' am a junior but very ambitious web developer, constantly learning to give you what you deserve... I am helping people to create anything from basic website to portfolios and even small web apps in order to make their business alive online and improve results.


Keep In Mind !

  • Windows
  • MacOs
  • Linux

Some of my bookmarks

Linux Coding

archwiki
debian references
man pages
ubuntu wiki fr
debian wiki
linux systems programming
AlternativeTo - Crowdsourced software recommendations

hacker's delights
amdahl's law
build your own x
reflections on trusting trust
casey muratori's blogs
design patterns
testing c/c++
python tutor
learn haskell
martin t. blogs
andrew k. ( ziglang creator ) blogs.


[ Email ] [ Linkedin ] [ Gists ]

Pinned Loading

  1. cg101a cg101a Public

    The idea behind this little sketch is to understand how we can go from modal/world space to view space. Put differently, how to go from 3D to 2D.

    Processing 1

  2. LL1p.go LL1p.go Public

    This is a simple LL(1) grammar tokenizer & parser written in Go.

    Go 1

  3. eddy eddy Public

    Eddy - A minimal text editor written in Go ( started only with one file ! ).

    Go 2

  4. C-huffman-text-compression C-huffman-text-compression Public

    This project impelements a basic version of the Huffman text compression algorithm, using the Huffman tree.

    C 1

  5. parallelism.c parallelism.c Public

    Gpu & Cpu side parallelism. Done using Cuda and MPI (Message Passing Interface).

    C 1

  6. Understanding go modules.md Understanding go modules.md
    1
    ## Understanding go modules.
    2
     
    3
     
    4
     
    5
    Before Go 1.11, Go developers had only one choice on how and where to write Go code, they had to be working under $GOPATH. This path is usually under $HOME/go, and in there we can find these directories: