jbmsf

16 ms·

121.
by jbmsf 7y ago
It's always a bit risky to document contracts with the left hand and implement them with the right. The best case to me is a framework that serves both functions at once. I built something like this at my last job by having an opiniona
122.
by jbmsf 7y ago
Also: set PIP_REQUIRE_VIRTUALENV=true You won't be able to install with pip unless you are in a virtualenv.
123.
by jbmsf 7y ago
In general, I believe in this kind of system. I've long been a fan of public engineering ladders (see: Rent the Runway) and create a real career path for non-managers. But... I see a lot of companies hiring at the senior end of the man
124.
by jbmsf 7y ago
Excellent post, thank you. I've run into similar challenges in a number of (mostly microservice) systems that also avoided monorepos (for various practical and philosophical reasons). Parts of the solution space here are very familiar,
125.
by jbmsf 7y ago
Until/unless we find some solution for regulatory capture, this direction is a lot less appealing to me. I hardly think the current regulation of telecoms is a good example of what's best for the public.
126.
by jbmsf 8y ago
Rings true to me.
127.
by jbmsf 8y ago
re: why review; I commented about this above, but: 1. We prefer to be able to say that everything is reviewed, but that in this particular case the review works automatically. Requiring a PR review is important to our security model (an
128.
by jbmsf 8y ago
I don't agree at all. (Aside: I work with the author, so I am biased. We all are.) Some relevant context: - Despite your interpretation, we believe strongly in PR review outside of this narrow area. In our business, security and appro
129.
by jbmsf 9y ago
We also try to avoid the you/they dichotomy. It's bad culture.
130.
by jbmsf 9y ago
Who's ready to buy Behemoth?