Good Talk

Miki Tebeka

353

Story time...

קידום

Few Years Later

  • I would go out of my way to attend a follow up course with Miki
  • Instructor: 5 out of 5
  • Best workshop I had in the last 10 years.
  • ...

Content

ROAM - Reader, Objective, Action, Impression

Writing Without Bullshit

For sale: baby shoes, never worn.

Hemingway

Write drunk, edit sober.

Hemingway

Slides

Amateurs talk about tactics, but professionals study logistics.

General Robert H. Barrow

The 10/20/30 Rule of PowerPoint

Guy Kawasaki
Dark Code
Light Code
screen

Introduction

Modules provide an integrated solution for three key problems that have been a pain point for developers since Go’s initial release:

  • Ability to work with Go code outside of the GOPATH workspace.
  • Ability to version a dependency and identify the most compatible version to use.
  • Ability to manage dependencies natively using the Go tooling.

With the release of Go 1.13, these three problems are a thing of the past. It has taken a lot of engineering effort from the Go team over the past 2 years to get everyone here. In this post, I will focus on the transition from GOPATH to modules and the problems modules are solving. Along the way...


Modules Part 01: Why And What - Bill Kennedy

Why?

display
Conference: HDMI, 16х9
wifi

You

7 P's: Proper Planning and Preparation Prevents Piss Poor Performance.

British Army Saying
hourglass
Dress

Photo by Ruthson Zimmerman on Unsplash
smell
pee
notification

What are your tips?

Thank You

353solutions