Protected: theeuropean.de: Streifenpolizistin Tania Kambouri aus Bochum schlägt Alarm

This content is password protected. To view it please enter your password below:

Advertisements

Thomas Fuchs

Thomas Fuchs

Author of Zepto.js, of script.aculo.us, and I’m a Ruby on Rails core alumnus.

The aerogel-weight mobile JavaScript framework, which also works great for Safari and Chrome extensions. The jQuery-compatible API makes it easy to pick up, and it’s just 5k to 7k in size!

Why not try Freckle, the best time tracking software ever! 🙂

Learn how to design things for humans
Stick to a few languages. Master them.
Don’t follow the hype
Stick to a style
Implement that minimum viable solution
Avoid complexity
Coding > Configuration
Never stop learning

Matthew Might, Utah University

Matthew Might, Utah University

Matt Might
Associate Professor
Presidential Scholar

My primary research area is static analysis of higher-order programs.

My broader interests include language design, compiler implementation, security, program optimization, parallelism and program verification.

I run the U Combinator software systems research group.

I am available as an expert witness on subjects within my expertise. With respect to my reports, I am willing to be deposed and to testify.

My son Bertrand was the first patient ever discovered with a rare disorder known as N-Glycanase deficiency. I wrote an essay about the process of scientific discovery, and the aftermath has been covered by an article in The New Yorker and in Der Spiegel. Learn more at NGLY1.org.

Teaching

Spring 2015: Compilers.
Spring 2014: Scripting Languages.
Fall 2013: Advanced Compilers.
Spring 2013: Compilers.
Spring 2012: Scripting Languages.
Spring 2011: Compilers.
Fall 2009: Advanced topics in compilation.
Spring 2009: Programming language analysis.
Spring 2009: Static analysis seminar.

Blog

blog.might.net is really just a collection of short articles.

Here are the 7 most recent:

HOWTO: Get tenure
Counting hash collisions with the birthday paradox
Parsing BibTeX into S-Expressions, JSON, XML and BibTeX
Low-level web programming in Racket
Rare disease match-making via the internet
Desugaring regular operations in context-free grammars
Meeting notes: Small thoughts on large cohorts

Brave New Geek, Introspections of a software engineer

Brave New Geek, Introspections of a software engineer

Everything You Know About Latency Is Wrong
Dissecting Message Queues
You Cannot Have Exactly-Once Delivery
A Look at Nanomsg and Scalability Protocols (Why ZeroMQ Shouldn’t Be Your First Choice)
Go Is Unapologetically Flawed, Here’s Why We Use It

Infrastructure Engineering in the 21st Century
Everything You Know About Latency Is Wrong
Probabilistic algorithms for fun and pseudorandom profit
You Own Your Availability
What You Want Is What You Don’t: Understanding Trade-Offs in Distributed Messaging

Recurse Center

Recurse Center

Founded in 2011, the Recurse Center is a free, self-directed, educational retreat for people who want to get better at programming, whether they’ve been coding for three decades or three months. Participants come from around the world for 12-week batches in New York, where they write open source software and grow together as programmers in a friendly, intellectual, and energizing environment.

With an alumni network of more than 500 people in dozens of countries, we have one of the most tightly-knit, diverse, and supportive programming communities in the world.

Our retreat is free for everyone, and we offer need-based living-expense grants of up to $7,000 to women and people from groups traditionally underrepresented in programming.

Prior to March of 2015, we were (confusingly) named Hacker School.

The Recurse Center is…

Self-directed

We value intrinsic motivation and self-direction, and believe people learn best when they’re free to explore their passions and interests.

Accessible

We’re free for everyone. We also offer need-based grants for living expenses for people from traditionally underrepresented groups in programming.

Stimulating

We look for smart, friendly, self-directed, and intellectually curious people who enjoy programming and want to get dramatically better.

Exceptional

We have exceptional residents including Peter Norvig, Jessica McKellar, Yaron Minsky, Leigh Honeywell, David Nolen, Peter Seibel, Nada Amin, and more.

Thoughtful

The atmosphere here is friendly and intellectual. We have a gender-balanced environment, and lightweight social rules.

Supportive

We have a tight-knit community of more than 600 alumni from over 25 countries. Our motto is “never graduate.”

Project-based

Recursers have made significant contributions to dozens of open source projects and started many of their own.

Connected

We make money by helping great companies hire our alumni. There’s no obligation to take a job if you don’t want one.

codewords.recurse.com: Git from the inside out

codewords.recurse.com: Git from the inside out

Mary Rose Cook

This essay explains how Git works. It assumes you understand Git well enough to use it to version control your projects.

The essay focuses on the graph structure that underpins Git and the way the properties of this graph dictate Git’s behavior. Looking at fundamentals, you build your mental model on the truth rather than on hypotheses constructed from evidence gathered while experimenting with the API. This truer model gives you a better understanding of what Git has done, what it is doing, and what it will do.

The text is structured as a series of Git commands run on a single project. At intervals, there are observations about the graph data structure that Git is built on. These observations illustrate a property of the graph and the behavior that this property produces.

After reading, if you wish to go even deeper into Git, you can look at the heavily annotated source code of my implementation of Git in JavaScript.

Summary

Git is built on a graph. Almost every Git command manipulates this graph. To understand Git deeply, focus on the properties of this graph, not workflows or commands.

To learn more about Git, investigate the .git directory. It’s not scary. Look inside. Change the content of files and see what happens. Create a commit by hand. Try and see how badly you can mess up a repo. Then repair it.