Skip to content

Instantly share code, notes, and snippets.

View danielnegri's full-sized avatar
Coffee first.

Daniel Negri danielnegri

Coffee first.
View GitHub Profile
@danielnegri
danielnegri / .tmux.conf
Created April 5, 2022 00:32
$HOME/.tmux.conf
#set -g default-terminal "screen-256color"
# change prefix command to C-z
set -g prefix C-z
unbind C-b
bind C-z last-window
bind z send-prefix
# Turn on mouse support
setw -g mouse on
@danielnegri
danielnegri / alacritty.yml
Created April 5, 2022 00:09
$HOME/.config/alacritty/alacritty.yml
# Configuration for Alacritty, the GPU enhanced terminal emulator.
# Import additional configuration files
#
# Imports are loaded in order, skipping all missing files, with the importing
# file being loaded last. If a field is already present in a previous import, it
# will be replaced.
#
# All imports must either be absolute paths starting with `/`, or paths relative
# to the user's home directory starting with `~/`.
Lista Filmes
http://bit.do/jorgedejorge_maisfilmes
http://bit.do/BoxFilmesSD
http://bit.do/jorgedejorge_filmes
http://bitly.com/jorgedejorge_subs
Lista Canais TV
http://bit.ly/JC-CANAIS
@danielnegri
danielnegri / tmuxfixer.js
Created July 24, 2020 14:19 — forked from maxdavid/tmuxfixer.js
Simple script for updating tmux config files, converting deprecated -fg, -bg, and -attr options to the combined -style option
#!/usr/bin/env node
/*
tmuxfixer.js
USAGE:
$ node tmuxfixer.js old-conf-path [new-conf-path]
PURPOSE & CONTEXT: This script takes in a tmux configuration file and combines
all deprecated -fg, -bg, and -attr into a single -style option line.
@danielnegri
danielnegri / FB-PE-InterviewTips.md
Created July 1, 2020 00:32 — forked from ameenkhan07/FB-PE-InterviewTips.md
Facebook Production Engineering Interview

What to Expect and Tips

• 45-minute systems interview, focus on responding to real world problems with an unhealthy service, such as a web server or database. The interview will start off at a high level troubleshooting a likely scenario, dig deeper to find the cause and some possible solutions for it. The goal is to probe your knowledge of systems at scale and under load, so keep in mind the challenges of the Facebook environment.
• Focus on things such as tooling, memory management and unix process lifecycle.

Systems

More specifically, linux troubleshooting and debugging. Understanding things like memory, io, cpu, shell, memory etc. would be pretty helpful. Knowing how to actually write a unix shell would also be a good idea. What tools might you use to debug something? On another note, this interview will likely push your boundaries of what you know (and how to implement it).

Design/Architecture 

Interview is all about taking an ambiguous question of how you might build a system and letting

@danielnegri
danielnegri / FB-PE-InterviewTips.md
Created July 1, 2020 00:32 — forked from ameenkhan07/FB-PE-InterviewTips.md
Facebook Production Engineering Interview

What to Expect and Tips

• 45-minute systems interview, focus on responding to real world problems with an unhealthy service, such as a web server or database. The interview will start off at a high level troubleshooting a likely scenario, dig deeper to find the cause and some possible solutions for it. The goal is to probe your knowledge of systems at scale and under load, so keep in mind the challenges of the Facebook environment.
• Focus on things such as tooling, memory management and unix process lifecycle.

Systems

More specifically, linux troubleshooting and debugging. Understanding things like memory, io, cpu, shell, memory etc. would be pretty helpful. Knowing how to actually write a unix shell would also be a good idea. What tools might you use to debug something? On another note, this interview will likely push your boundaries of what you know (and how to implement it).

Design/Architecture 

Interview is all about taking an ambiguous question of how you might build a system and letting

@danielnegri
danielnegri / FB-PE-InterviewTips.md
Created July 1, 2020 00:32 — forked from ameenkhan07/FB-PE-InterviewTips.md
Facebook Production Engineering Interview

What to Expect and Tips

• 45-minute systems interview, focus on responding to real world problems with an unhealthy service, such as a web server or database. The interview will start off at a high level troubleshooting a likely scenario, dig deeper to find the cause and some possible solutions for it. The goal is to probe your knowledge of systems at scale and under load, so keep in mind the challenges of the Facebook environment.
• Focus on things such as tooling, memory management and unix process lifecycle.

Systems

More specifically, linux troubleshooting and debugging. Understanding things like memory, io, cpu, shell, memory etc. would be pretty helpful. Knowing how to actually write a unix shell would also be a good idea. What tools might you use to debug something? On another note, this interview will likely push your boundaries of what you know (and how to implement it).

Design/Architecture 

Interview is all about taking an ambiguous question of how you might build a system and letting

@danielnegri
danielnegri / settings.json
Last active February 10, 2023 18:04
Visual Studio Code
// Place your settings in this file to overwrite the default settings
{
"workbench.iconTheme": "material-icon-theme",
"files.trimTrailingWhitespace": true,
"files.insertFinalNewline": true,
"editor.fontFamily": "JetBrains Mono, Consolas, 'Courier New', monospace",
"editor.fontSize": 14,
"editor.fontWeight": "300",
"editor.lineHeight": 24,
"editor.letterSpacing": 0.5,
@danielnegri
danielnegri / Rules
Created September 28, 2019 01:32
uBlock
no-large-media: behind-the-scene false
no-scripting: estadao.com.br true
no-scripting: folha.com.br true
no-scripting: uol.com.br true
no-scripting: www.nytimes.com true
behind-the-scene * * noop
behind-the-scene * 1p-script noop
behind-the-scene * 3p noop
behind-the-scene * 3p-frame noop
behind-the-scene * 3p-script noop
@danielnegri
danielnegri / trrprefs.md
Created June 7, 2019 01:35 — forked from bagder/trrprefs.md
trr prefs

NOTE

A blog post with more updated info then this has been posted here

Preferences

All preferences for the DNS-over-HTTPS functionality in Firefox are located under the "network.trr" prefix (TRR == Trusted Recursive Resolver). The support for these are targeted for shipping in release Firefox 62.

network.trr.mode

set which resolver mode you want.