<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Leo Zhang</title>
    <link>https://leozhang.me/</link>
    <description>Recent content on Leo Zhang</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <managingEditor>leo@leozhang.me (Leo Zhang)</managingEditor>
    <webMaster>leo@leozhang.me (Leo Zhang)</webMaster>
    <copyright>Copyright Leo Zhang</copyright>
    <lastBuildDate>Mon, 22 Oct 2018 00:00:00 +0000</lastBuildDate><atom:link href="https://leozhang.me/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pathologies of Go package management</title>
      <link>https://leozhang.me/post/2018/10/22/pathologies-of-go-package-management/</link>
      <pubDate>Mon, 22 Oct 2018 00:00:00 +0000</pubDate>
      <author>leo@leozhang.me (Leo Zhang)</author>
      <guid>https://leozhang.me/post/2018/10/22/pathologies-of-go-package-management/</guid>
      <description>EDIT: I&amp;rsquo;ve gotten quite a few responses asking about Go modules and how they fit into this picture. I&amp;rsquo;ve played around with them experimentally, and my initial impression is that they&amp;rsquo;re certainly a step in the right direction. I have some worries on the specification of go.mod files, but we&amp;rsquo;ll have to see how that plays out.
 TL;DR:
 Go package idioms make reproducible builds really easy. (Jump to section) Go package idioms make dependency analysis really hard.</description>
    </item>
    
    <item>
      <title>Reflecting on one year of early-stage engineering</title>
      <link>https://leozhang.me/post/2018/10/17/reflecting-on-one-year-of-early-stage-engineering/</link>
      <pubDate>Wed, 17 Oct 2018 00:00:00 +0000</pubDate>
      <author>leo@leozhang.me (Leo Zhang)</author>
      <guid>https://leozhang.me/post/2018/10/17/reflecting-on-one-year-of-early-stage-engineering/</guid>
      <description>My computer science degree didn&amp;rsquo;t teach me that much about software engineering.
I remember coming fresh out of college with no clue what a Senior Software Engineer did. There was a vague sense that experience was valuable, but it was difficult for me to articulate what that meant in concrete terms.
I spent the year after that at Google. Google is a great place for new grads, because it provides a lot of structure, guidance, and examples of what good engineering management and practices look like.</description>
    </item>
    
    <item>
      <title>About</title>
      <link>https://leozhang.me/about/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <author>leo@leozhang.me (Leo Zhang)</author>
      <guid>https://leozhang.me/about/</guid>
      <description>My name is Leo. I work on the engineering team at FOSSA.
Previously, I&amp;rsquo;ve worked at:
 Google Kloudless Scalable Press Mithril Copia  My interests lie at the intersection of programming systems, education, and human-computer interaction. Some topics that particularly interest me:
 How can we build better primitives for software systems? How can we build software that concretely improves our quality of life? How can we teach people to think critically rather than memorize?</description>
    </item>
    
  </channel>
</rss>
