Sevag H sevagh

## lapsync.go
////////////////////////////////////////////////////////////////////////////////
// The MIT License (MIT)
//
// Copyright (c) 2015 Mark LaPerriere
//
// Permission is hereby granted, free of charge, to any person obtaining a copy
// of this software and associated documentation files (the "Software"), to deal
// in the Software without restriction, including without limitation the rights
// to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
// copies of the Software, and to permit persons to whom the Software is

## delete_git_submodule.md

      
              1 file
            
          
              361 forks
            
          
              195 comments
            
          
              2382 stars
            
          
                myusuf3
                / delete_git_submodule.md
            
            
              Created
              November 3, 2014 17:36
            
              
                How effectively delete a git submodule.
              
          
    To remove a submodule you need to:

Delete the relevant section from the .gitmodules file.
Stage the .gitmodules changes git add .gitmodules
Delete the relevant section from .git/config.
Run git rm --cached path_to_submodule (no trailing slash).
Run rm -rf .git/modules/path_to_submodule (no trailing slash).
Commit git commit -m "Removed submodule "
Delete the now untracked submodule files rm -rf path_to_submodule


## .bashrc
export PYFLAKES_BUILTINS="__salt__,__opts__,__grains__,__pillars__,__context__"

## xymodem-mini.c
/*
 * Minimalistic implementation of the XModem/YModem protocol suite, including
 * a compact version of an CRC16 algorithm. The code is just enough to upload
 * an image to an MCU that bootstraps itself over an UART.
 *
 * Copyright (c) 2014 Daniel Mack <github@zonque.org>
 *
 * License: MIT
 */

## The Technical Interview Cheat Sheet.md

      
              1 file
            
          
              3400 forks
            
          
              904 comments
            
          
              8425 stars
            
          
                tsiege
                / The Technical Interview Cheat Sheet.md
            
            
              Last active
              May 9, 2024 13:54
            
              
                This is my technical interview cheat sheet. Feel free to fork it or do whatever you want with it. PLEASE let me know if there are any errors or if anything crucial is missing. I will add more links soon.
              
          
    ANNOUNCEMENT

I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!


\

  
## magic_ring.cpp
#define _CRT_SECURE_NO_DEPRECATE

#include <stdio.h>
#include <string.h>
#include <Windows.h>

// This allocates a "magic ring buffer" that is mapped twice, with the two
// copies being contiguous in (virtual) memory. The advantage of this is
// that this allows any function that expects data to be contiguous in
// memory to read from (or write to) such a buffer. It also means that
	////////////////////////////////////////////////////////////////////////////////
	// The MIT License (MIT)
	//
	// Copyright (c) 2015 Mark LaPerriere
	//
	// Permission is hereby granted, free of charge, to any person obtaining a copy
	// of this software and associated documentation files (the "Software"), to deal
	// in the Software without restriction, including without limitation the rights
	// to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
	// copies of the Software, and to permit persons to whom the Software is
	/*
	* Minimalistic implementation of the XModem/YModem protocol suite, including
	* a compact version of an CRC16 algorithm. The code is just enough to upload
	* an image to an MCU that bootstraps itself over an UART.
	*
	* Copyright (c) 2014 Daniel Mack <github@zonque.org>
	*
	* License: MIT
	*/
	#define _CRT_SECURE_NO_DEPRECATE

	#include <stdio.h>
	#include <string.h>
	#include <Windows.h>

	// This allocates a "magic ring buffer" that is mapped twice, with the two
	// copies being contiguous in (virtual) memory. The advantage of this is
	// that this allows any function that expects data to be contiguous in
	// memory to read from (or write to) such a buffer. It also means that