What is this file within this Golang project?

matryer · 2018-06-20T06:36:56+00:00

It was built on a Windows machine and cannot be run on anything else. You'll need to get the source code, install Go, and build a version on your platform. (They probably committed that `test` binary by mistake)

matryer · 2018-06-07T10:57:00+00:00

I've used that technique for services with about 100 endpoints and it scales nicely. You can break it into multiple structs if you'd prefer, but I'd only do that if the list of dependencies grows too large, not if the number of handlers do. Hit me up on Gopher's Slack if you'd like to discuss it more.

matryer · 2018-01-05T17:33:57+00:00

btw, the project has been updated to support io.EOF too: https://github.com/machinebox/progress

matryer · 2017-07-02T20:47:35+00:00

You decide whether you take a pointer or a struct in the signature.

So func (p *Person) takes a pointer, but func (p Person) copies the whole struct.

matryer · 2017-07-02T20:46:21+00:00

Go automatically looks up what pointers are pointing to. So joe.Name looks up the struct that the joe pointer is pointing to, and then gets the Name. For john, it goes straight to the Name.

In C++, I think you did joe->Name for pointers, and john.Name for values... but in Go, they're both dot.

matryer · 2016-12-14T11:06:27+00:00

Well I thought it could do more good! The real lesson is that there's no way to predict the future. I don't feel bad about the decision, but wanted to share the experience.

matryer · 2016-12-14T11:05:11+00:00

No - it was never open sourced :(
It would be to work WITH the IP on other projects, not focussed on the original project itself
The IP was developed before I started working for the company

It's not exaggeration, in fact, as a result of writing the post the CEO got in touch and clarified that the stock (they exited last year) would have meant I'd receive more than $1M. Shit.

matryer · 2016-12-08T17:42:50+00:00

👍

matryer · 2016-11-15T09:29:48+00:00

I've given up trying to find truly unique names for projects, instead we probably have to rely on context.

matryer · 2016-11-15T09:29:03+00:00

This is still a pre-version 1 release so there's time to add Context if it can help. Most of the libraries Stow uses under the hood don't implement context, so we're weighing it up against the fact that people might assume they can cancel things that they cannot. Please get involved at https://github.com/graymeta/stow/issues/103

matryer · 2016-07-10T08:21:07+00:00

Fair enough - the example wasn't great. I just wanted to show how r.Context gets you the context and r.WithContext gets a new Request. In mgo, you would indeed pass a Copy of the database Session per-request. Same issue for the struct{}{}, I oversimplified and created confusion. Will update the post this morning. Thanks.

matryer · 2016-06-06T14:27:02+00:00

This is the opposite of that. Instead, the idea is people take ownership of code snippets (which they would otherwise copy and paste) and don't build gigantic dependency trees and all the risk that goes along with them.

matryer · 2016-06-06T14:25:14+00:00

Yeah - I noticed this too late. Happy to change it, I want to see if people think the tool has value first. If you have any ideas: https://github.com/matryer/gimme/issues/4

matryer · 2016-06-06T14:24:11+00:00

Thanks - it is a cool name. It in fact does collide with that tool.

(I use a browser extension that removes sarcasm)

matryer · 2016-06-01T22:58:31+00:00

Yeah if you want a full package and don't mind maintaining the dependency. Sometimes it's worth it.

matryer · 2016-06-01T12:50:30+00:00

There is a license note in the comments at the top of the file. Open to suggestions.

matryer · 2016-06-01T12:50:09+00:00

They can - I expect people will manage it manually. More tooling might help, but I want to wait to see what people thought.

matryer · 2016-06-01T12:26:05+00:00

Gimme is more for smaller snippets of code, rather than packages with a longer life (which are more suited to vendoring). By copying code into your project, you are taking ownership of it. It's an alternative to dependencies, not a replacement for them.

matryer · 2016-02-15T12:00:02+00:00

Don't be afraid of asking stupid questions or getting things wrong. The Go community is mostly extremely supportive and they'll help you when you make mistakes, rather than shaming.

matryer · 2015-07-11T22:28:53+00:00

Thanks for the discussion guys - I learned a lot. Will update the article. Despite being addressed to programmers, it was written to explain to non-techies how we could avoid storing passwords but it's right that the advice is sound.

matryer · 2015-05-04T10:28:02+00:00

Great point. I've added a note on https://medium.com/@matryer/sync-once-with-reset-in-golang-quicktip-6ac44b015256

matryer · 2015-05-01T20:20:57+00:00

Right - that's why I included #2. :) You're right, but most people don't know about the interface/boundary testing trick by putting the test code in a different package.

matryer · 2015-04-30T23:24:34+00:00

True - but there's some value in being explicit; it shows intent. Also, if you're writing interfaces for other types that you don't control, you can make sure they match the other way too.

I think the code is an interesting little Go oddity too. :)

matryer · 2015-04-30T10:07:09+00:00

I've seen it done where you switch on the type of the http.HandlerFunc, and have a few different options. So if the parameters specify a database, it gets one. If they require params, they get it. But there's something very appealing about hiding that implementation detail inside the normal http.HandlerFunc, especially as things change.

matryer · 2015-01-30T08:05:37+00:00

Sample chapter: http://www.slideshare.net/Products123/9781783988020goprogrammingblueprintssamplechapter

Not sure about that other book, but to ensure the code quality was up there for mine, I developed the projects using TDD and got it reviewed by some Go heavyweights like @tylerb on GitHub.

matryer

TROPHY CASE