This list is meant to be a both a quick guide and reference for further research into these topics. It's basically a summary of that comp sci course you never took or forgot about, so there's no way it can cover everything in depth. It also will be available as a gist on Github for everyone to edit and add to.
###Array ####Definition:
I'm particularly interested in Tor onion services. I hope that they can facilitate widely deployed self-authenticating encrypted communication channels at scale.
Anecdotal reports suggest that the current onion services infrastructure does not scale well [1, #8902]. In particular onion service introduction points are susceptible to hammering by clients and malicious attackers. Denial of service attacks where a single Tor process is overloaded by an attackers have also been experienced recently [#15463].
In contrast to modern distribute
You are extremely enthusiastic (and rightfully so) about a new product or business idea that you have. Or maybe someone approaching you is (but I'm going to assume that you're the one with the idea for simplicity). You want to bring a cofounder (or an investor) onboard. This can involve a lot of back and forth calls and/or emails that takes up a lot of time. To help paint a clear picture about your product/business idea, here is a questionnaire you can fill up and
Performance should linearly increase with added nodes and no extra effort. If the number of people required to maintain a system doubles with doubled capacity, you're doing it wrong.
Errors shouldn't cause growing data smell and should be quick to recover from.
The lesser locks there are in the system, the better it is.
Don't depend on something that wouldn't scale or keep up with the rest of the application.
| #!/usr/bin/env bash | |
| #################################################################################### | |
| # Chipr Globals | |
| #################################################################################### | |
| GIT_REMOTE="$(git remote)" | |
| #################################################################################### | |
| # Chipr Functions |
| package client | |
| import ( | |
| "context" | |
| "crypto/md5" | |
| "crypto/tls" | |
| "encoding/json" | |
| "errors" | |
| "fmt" | |
| "net" |
The following books are ordered in descending order of Matthew's preference.
by Avinash K. Dixit
Recommended by Ted Neward. A different perspective and writing style from the other volumes listed.
“I am hard pressed to think of another book that can match the combination of practical insights and reading enjoyment.”—Steven Levitt
| package main | |
| import ( | |
| "encoding/json" | |
| "fmt" | |
| "reflect" | |
| elastic "gopkg.in/olivere/elastic.v3" | |
| ) |
https://webassembly-summit.org/
https://www.youtube.com/watch?v=IBZFJzGnBoU
this is my goto copy paste answer that I post everywhere and I'm going to explain you how to solve an issue using an example so I cannot assure you that this would work in case of every issue but my aim is to try to make you understand what and how to think like when solving an issue.
Note this guide assumes that you have some exposure to software devleopment and have built at least one or two of your own applications as a side project. If not then try building a few projects before starting out with OSS dev it would certainly help. Use this guide for ideas.
Get familiar with git and github if you are not already. Best way to do this is to make a little side project and push it to github. You have a lot of time for GSoC so you can make lots of side projects and experiment around with those until you are familiar with the git workflow
Pick up a software that you find interesting
