Hi HN,

TimeFerret is a beautiful calendar app for iPhones and iPads. It comes with a custom keyboard that lets you access your calendar from any app.

How TimeFerret is different from other calendar apps: 1. Quickly see how much time you have between meetings in the 24-hour "Daily Donut" 2. Calculate Meeting Cost 3. Mark certain hours of the day as "Me Time" and flag meetings that interrupt this time. 4. Carve out a few hours as "Meeting Time" and flag meetings that are outside these hours.

We are happy to answer all your questions about TimeFerret and would love any and all feedback :)

Stencil implements GoImports formatting which is basically GoFmt with a slightly different import ordering. And yes, it would be useful to standardize this somehow, the way go generate is standardized.

The go vet integration with go test looks interesting. I'm currently using github.com/surullabs/lint [1] to run vet and a few other lint tools as part of go test. It provides a nice increase in productivity for my dev cycle. Having vet + other lint tools integrated into my dev+test cycle has caught a number of bugs before they hit CI.

[1] https://github.com/surullabs/lint

Disclaimer: I'm the author of the above library.

Exactly. The sync.Pool will only be useful if net.Conn.Read accepted a Writer instead of []byte.

That wouldn't make much sense since the Reader interface requires []byte, but the specific connection could inherit WriterTo: https://golang.org/pkg/io/#WriterTo

(TCPConn implements ReaderFrom, but not WriterTo)

I wasn't very clear. A hypothetical conn.Read(w Writer) would call Write on w instead of filling a byte array. Write in turn allocates as needed. WriterTo is a cleaner way of doing this.

> A hypothetical conn.Read(w Writer) would call Write on w instead of filling a byte array.

Yes I understand the purpose — hence suggesting WriterTo which is supposed to do that — I simply noted that conn.Read(w Writer) would make Conn not extend io.Reader anymore since it takes a buffer.

Ah right.

Hi,

I'm the author. Please let me know if you have any questions or comments.

This library allows you to run a variety of linters as part of go test. It also supports whitelisting false positives. It reduces the need for build scripts, makes CI integration easy and lets projects enforce linter usage without extra scripts. I built it while working on our mobile app (which is written in Go) and have found it useful so far.

The below example test will check for gofmt usage, run go tool vet --shadow, golint, errcheck, gosimple and gostaticcheck

  import (
      "testing"
      "github.com/surullabs/lint"
  ) 


  func TestLint(t *testing.T) {
      if err := lint.Default.Check("./..."); err != nil {
          t.Fatal("lint failures: %v", err)
      }
  }

Please let me know if you find this useful and if you'd like any features added/removed/modified.

This is something I definitely agree with. I've sometimes found that taking a few seconds to cache state in a notepad before responding to the interruption helps a lot. Having times of day dedicated to meetings also helps reduce fragmentation. At the risk of being overly self-promoting, solving problems with fragmented work days is something my cofounder and I are working on now with TimeFerret (https://www.timeferret.com).

This is very good advice. I've had trouble with flexibility for as long as I can remember. I've recently started some light exercise again and including yoga for just 5 to 10 min has made an enormous difference.

I've used git subrepo [1] for vendoring and been quite happy with it. Doesn't seem to have the problems of git submodule and it's easier to use than git subtree.

[1] https://github.com/ingydotnet/git-subrepo

I'll try it out, thanks :)

Slightly shameless self promotion: If you're looking for an Android solution, we're working on TimeFerret, a calendar app that helps you reduce fragmented meeting schedules and track productivity. It's not released yet though. The iOS version will be out first, followed by Android.

[1] http://www.timeferret.com

> Over Quota

> This application is temporarily over its serving quota. Please try again later.

Thanks for letting us know. I've updated the quota so the website is up now.

EDIT: Changed it to say the website is up, where it said the website will be up shortly.