1,107 karma · joined August 25, 2014
In general, I think Django makes it way too easy to shoot yourself in the foot.
Yes, it is.
However, Google uses the same interview process for all software engineers, and mostly decides what job they will do after deciding whether to hire them. So they really can't tailor their questions without changing their entire process. I think they should change it, but I understand why they haven't.
Evaluating performance is tough. Evaluating performance without greatly distorting incentives is much tougher. I agree fairness should be a consideration, but it is not the primary purpose of a business.
Coalition is working to solve cyber risk. We are a small team of security experts, insurance professionals, and intelligence community veterans building a better cyber insurance product. Coalition is automating risk assessment to make purchasing insurance easy, and using our knowledge to educate clients and mitigate risk where possible. We've raised $10m recently.
We are looking to expand our 11-person engineering team. These roles come with significant amounts of responsibility and autonomy. The data science role in particular is quite broad: areas of focus include expanding on our novel computational statistical tools for risk-assessment and optimizing our overall insurance portfolio.
Our front-end is in React, our back-end is built with Flask running on Python 3.6, and our infrastructure is hosted on AWS. We are also always open to new technologies; we believe in using the best tool for the job.
Email jobs@thecoalition.com for more information.
- Hover over each symbol one-by-one until tooltip shows itself (sometimes takes multiple tries); or
- Google "how to find X in JIRA"
Coalition is working to solve cyber risk. We are a small team of security experts, insurance professionals, and intelligence community veterans building a better cyber insurance product. Coalition is automating risk assessment to make purchasing insurance easy, and using our knowledge to educate clients and mitigate risk where possible. We've raised $10m recently.
We are looking to expand our 11-person engineering team. These roles come with significant amounts of responsibility and autonomy. The data science role in particular is quite broad: areas of focus include expanding on our novel computational statistical tools for risk-assessment and optimizing our overall insurance portfolio.
Our front-end is in React, our back-end is built with Flask running on Python 3.6, and our infrastructure is hosted on AWS. We are also always open to new technologies; we believe in using the best tool for the job.
Email jobs@thecoalition.com for more information.
- It's very slow: re-locking after updating 1 dependency often takes me ~1 minute.
- It has lots of bugs. To name a few in 11.6.9: clobbers comments in the Pipfile, inconsistently includes dependencies for other build environments in Pipfile.lock, stores the wrong index in Pipfile.lock for packages not on PyPI.
- They release multiple times per day, often breaking things in patch releases.
- Kenneth Reitz is quite unpleasant to deal with in GitHub issues, which I often have to because of the previous 2 issues.
From what I've heard, Pipenv "has been officially blessed" only insofar as its maintainer got commit access to PyPA's documentation and inserted a recommendation.
It occurred to me that while I learned in college how to show, using Galois theory, that quintic equations are not generally solvable by radicals, I had no idea how Galois theory really relates to the process of finding roots. So I went back and derived the quadratic formula, the cubic formula, and sketched the quartic formula to see how the process used the ideas formalized by Galois theory and where it breaks down. I've tried to write the result up in a motivated and understandable way, instead of like a math textbook: https://alexcbecker.net/mathematics.html#the-quadratic-equat...
OrderedDict is fundamentally different because it is designed to allow inserting/removing keys in the middle of the ordering in O(1) time. It does not use the new dict under the hood, or vice-versa.
Coalition is working to solve cyber risk. We are a small, well-funded team of security experts, insurance professionals, and intelligence community veterans building a better cyber insurance product. Coalition is automating risk assessment to make purchasing insurance easy, and using our knowledge to educate clients and mitigate risk where possible.
We are looking to expand our 5-person engineering team, especially on the back-end and API. These roles come with significant amounts of responsibility and autonomy. Our front-end is in React, our back-end is in Python 3.6, and our infrastructure is hosted on AWS. We are also always open to new technologies; we believe in using the best tool for the job.
Email jobs@thecoalition.com for more information.
That being said you need to actively pursue international sales for this to work, and i18n software is only a part of this. If you aren't making the effort on the sales side it probably isn't worth it on the engineering side.
1. Client requests X.html (which requires Y.css and Z.js) from Proxy.
2. Proxy forwards client's X.html request to Server.
3. [Server takes a long time to respond]
4. Server sends a 200 response to Proxy with X.html.
5. Proxy, per some configuration, adds Preload headers to this response indicating that Y.css and Z.js should be immediately loaded once this response is received, and sends it to Client.
6. Client requests Y.css and Z.js.
With the 103 status code, this would look like:
1. Client requests X.html (which requires Y.css and Z.js) from Proxy.
2. Proxy forwards client's X.html request to server and, per some configuration, immediately sends a 103 response with Preload headers for Y.css and Z.js to Client.
3. [Server takes a long time to respond]
4. In parallel, Client requests Y.css and Z.js.
5. Server sends a 200 response to Proxy with X.html.
6. Proxy sends this response to Client.
Note that since Y.css and Z.js are requested sooner, the final load time should be less.