You'll find the talks here
Approaching frontend as a backend developer, Svelte feels surprisingly pythonic. Let's take a quick look at what's familiar, what's foreign, and how to explore the gap.
You'll find the talks here
Approaching frontend as a backend developer, Svelte feels surprisingly pythonic. Let's take a quick look at what's familiar, what's foreign, and how to explore the gap.
// Try sign-in with AJAX | |
fetch('/signin', { | |
method: 'POST', | |
body: new FormData(e.target), | |
credentials: 'include' | |
}) |
It goes like this: “Once upon a time…something bad happened. The end.” How do you like this story?
Metrics, or stats, are numerical measures recorded by the application, such as counters, gauges, or timers. Metrics are very cheap to collect, since numeric values can be easily aggregated to reduce the overhead of transmitting that data to the monitoring system. They are also fairly accurate, which is why they are very useful for the actual monitoring (as the dictionary defines it) and alerting.
Yet the same capacity for aggregation is what makes metrics ill-suited for explaining the pathological behavior of the application. By aggregating data, we are throwing away all the context we had about the individual transactions.
func productHandler(w http.ResponseWriter, r *http.Request) {
key := r.URL.Path[len("/products/"):]
switch r.Method {
case "GET":
// do GET stuff
case "POST":
// Fo POST stuff
default:
http.Error(w, "Method Not Allowed", 405)
const PASS = ['32']; // green | |
const FAIL = ['31', '1']; // red, bold | |
function logStyle(ansiEscapeCodes, text) { | |
console.log(`\x1b[${ansiEscapeCodes.join(';')}m${text}\x1b[0m`); | |
} | |
class Tester { | |
constructor() {} |
[ | |
{ | |
"url": "http://money.cnn.com", | |
"rss": "http://rss.cnn.com/rss/money_topstories.rss" | |
}, | |
{ | |
"url": "http://thehill.com", | |
"rss": "http://thehill.com/rss/syndicator/19110" | |
}, | |
{ |
// This function works | |
export const appV1 = functions.https.onRequest(app); | |
// This function is not called when a new user is created | |
export const createUserProfile = functions.auth.user().onCreate( async (event) => { | |
console.log("createUserProfile: ", event.data); | |
}); |
func (d *Datastore) GetStuff(userKey, currentAccountKey, defaultAccountKey *cdatastore.Key) (*data.User, error) { | |
errCh := make(chan error, 3) | |
retCh := make(chan bool, 2) | |
done := make(chan bool) | |
u := &dbdata.User{} | |
a := &data.Account{} | |
// Fetch user | |
go func() { |
I hereby claim:
To claim this, I am signing this object: