janslow

4 ms·

1.
by janslow 3y ago
I try to use Make to bootstrap project-specific tooling when missing, by getting it to download (then verify) the tools, then delegate everything else to something like knit (or just/cargo/npm). That way, there's very few pre
2.
by janslow 5y ago
Agreed. I wasn't originally a fan of Go's error handling, but I do find it forces me to explicitly handle the error, I very rarely use a plain `return err` statement, instead wrapping it with additional parameters. Whereas when I
3.
by janslow 5y ago
This is unacceptable, in my opinion. Most of the properties I've rented in the UK have only have only had an inspection at the end, although one has had a mid-tenancy inspection, where they took photos of the (previously) damaged part
4.
by janslow 5y ago
In most cases, a breaking tooling change should only impact the root project (e.g., they need to change their readme from `go get` to `go install`), so there's only one codebase to fix and it's in the control of the person upgradi
5.
by janslow 6y ago
The lack of support for context.Context rules out this project for me. All our cross-cutting concerns (tracing/monitoring, auth, timeouts) are built on top of the context pattern (and it works great compared to other languages). Someth
6.
by janslow 8y ago
One of the issues is that it's tied quite heavily to the Java compiler, so you may need to wait until Lombok supports a new Java version before you can use it. Also as it is compiler magic, it can be a bit confusing to developers who h
7.
by janslow 10y ago
Whilst Swagger Codegen doesn't create perfect libraries and some of the generators don't support all the features, once it's set up, it's just as easy to create a client for every language as it is for just one. For exam