alexbecker

I don't see the value-add of a scale over, say, a button. I'm going to be interacting with the coffee when I use it, why not just leave the decision to re-order to me then?

We use them to restrict access to some static assets (beta documentation) by checking an authorization endpoint. Haven't had any problems--but we're also doing this at a very small scale.

Coalition | Back-End, Full-Stack, Product Manager | San Francisco, CA | Onsite, Full-Time

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're rapidly growing and scaling our team to accommodate that growth. We are looking to hire engineers and product managers and an engineering manager who can help us maintain a high standard of engineering while increasing the scale and functionality of our products. These roles come with a significant amount of responsibility and autonomy.

Our front-end is in React, our back-end is built on Python 3.6 with some services in Node, 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.

Jira drives me nuts with this. I have a 34" monitor and with six columns in our Kanban board I can see 4, maybe 5 tickets per column. With 10 people on a team it means constant scrolling to see what people are working on.

It finally pushed me over the edge to use user stylesheets. A bunch of "margin: 0 !important" and "display: none" and I get twice as much information on my screen at the cost of... looking polished I guess?

It's a fairly new paradigm, and I've noticed these things spread slowly in the Python ecosystem (Python 3 was released over 10 years ago). But I use it, and I've started seeing it in some other python packages lately.

Also keep in mind it is only for python packages, not applications--the primary benefit is that it is impossible for the tests to access files that are not part of the package build.

It sounds like layout is your primary problem (as it is most people's). You should view (the layout-specific parts of CSS) as a layout description language, which is a class of languages you've never worked with before, and so something that requires significantly more time investment than just learning a new syntax (e.g. JavaScript). My guess is you haven't put in that amount of focused study, so naturally it doesn't click for you.

This is not to say CSS doesn't deserve any blame--it's a bad layout description language, as evidenced in part by the fact that the recent grid+flexbox additions are much better (where supported) than old-school CSS.

> You have to piss clean before you can leave.

This is clearly unconstitutional, unless you have to be tried and convicted of a crime in order to enter, which I suspect would make it less attractive. Not to mention I think your view of what homeless people want/need is, uh, not exactly informed by a lot of experience in the streets.

I suspect that the manufacturing costs for many medical devices are quite low, e.g. stints, but this is not public data to my knowledge. But the manufacturers make a killing because they charge a high price.

The medical device industry (at least in the US) is very special. It does not have retailers per se, but there are a lot of middlemen who take varying, often enormous cuts. Medical device manufacturers make enormous amounts of money though. I am not sure how much of this is specific to the internal US market vs. carries over to US exports.

For a good treatment of this and many other aspects of US healthcare costs, see An American Sickness by Elisabeth Rosenthal.

But there is no money or prestige in that. Harvard didn't get a $37B endowment by trying to level the playing field.

Lots of people have no sense though.

Isn't this what git branches are for?

#1 is not false. They say:

> their capacity is largely fixed... Bitcoin has an estimated maximum of 7 transactions per second vs 24,000 for visa

Yes, Bitcoin could raise their artificial transaction cap. But they haven't recently, despite fees and delays getting quite large. So clearly there are significant difficulties in increasing the throughput meaningfully, and it is unclear how high it can go. To a user used to pre-existing transaction mechanisms, that's a "largely fixed" capacity.

There are two kinds of lazy loading--that which blocks the content, and that which doesn't. If you have e.g. a bunch of JS libraries that aren't necessary to display the page, only for certain interactions, it makes sense to lazily load those. This is what "lazy loading" meant in my front-end team at Google anyway. (Whether you should even have all of this JS to begin with is another question, however.)

Oh man, I used to be on the team that built that. It's just enormous. If you're on Chrome, the optimizations are sometimes enough to make it smooth. If you're on any other browser, god help you. I used to see 30s(!) reflows in Firefox.

Scrolling even on desktop was janky for me, and it was hard to center the paragraphs that were supposed to overlay the maps.

Coalition | Back-End, Full-Stack, Product Manager, Engineering Manager | San Francisco, CA | Onsite, Full-Time

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're rapidly growing and scaling our team to accommodate that growth. We are looking to hire engineers, product managers and an engineering manager who can help us maintain a high standard of engineering while increasing the scale and functionality of our products. These roles come with a significant amount of responsibility and autonomy.

Our front-end is in React, our back-end is built with Flask running on Python 3.6, with some services in Node, 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.

I got so frustrated using pipenv at work that I created an alternative package manager: https://pypi.org/project/dotlock/. It's not 1.0 yet but if it suits your needs I'd love if you tried it out.

This is Simpson's Paradox[0]--Iowa comes out on top because it has more white students, and white students in Iowa do better than non-white students in Texas.

[0] https://en.wikipedia.org/wiki/Simpson%27s_paradox

Pretty much. Shelters are either provided by charity or the local government, and state/federal money is only for very sympathetic classes like women with infant children.

I think they mean if you can tell that it's a .NET app (e.g. because they left the X-Powered-By header on), not if it's a .NET app in general.

That's because the 14th Amendment extends the "due process" requirement to the states, and under the [Incorporation Doctrine](https://www.law.cornell.edu/wex/incorporation_doctrine) respecting the 4th Amendment has been considered part of "due process".

Archive link: https://web.archive.org/web/*/http://mchap.io/using-foia-dat...

Coalition | SRE/DevOps | San Francisco, CA | Onsite, Full-Time

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 hire our first dedicated Site Reliability Engineer, who would streamline our deployment process, improve our monitoring and tune our services to keep them highly available and performant. This role comes with a significant amount of responsibility and autonomy.

Our front-end is in React, our back-end is built with Flask running on Python 3.6, with some services in Node, 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.

Navigation in particular is nearly impossible for me.

Can the URL of this be changed to a non-AMP page?

Coalition | SRE/DevOps | San Francisco, CA | Onsite, Full-Time

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 hire our first dedicated Site Reliability Engineer, who would streamline our deployment process, improve our monitoring and tune our services to keep them highly available and performant. This role comes with a significant amount of responsibility and autonomy.

Our front-end is in React, our back-end is built with Flask running on Python 3.6, with some services in Node, 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.

Is the implementation at the end of the article complete? I don't see anything that looks like the "galloping" behavior described just prior.

Back when I was working on Django codebases, I saw almost no use of `full_clean()`, largely because some validation was performed on `save()` (by virtue of being database constraints, e.g. non-nullability) while other validation was not, and there was no indication in the APIs which was which.

In a world in which Django applications were always written by people who read and understood the docs in full, I would totally agree with you about these criticisms. But I've never had such an opportunity outside of my own projects. I've only dealt with codebases that were written with falty assumptions, enabled by Django's choice to hide some but not all tricky work from its users. By then the database constraints would be incredibly painful to add since there was lots of data already violating it, and switching global defaults like ATOMIC_SAVE were nearly as bad since code had widely relied on other behavior.

You must not have read the section "Validation defined on the model is only enforced on the form". The validations I referenced, e.g. `choices`, are only run in when [`full_clean()`](https://docs.djangoproject.com/en/dev/ref/models/instances/?...) is called, and it's not called on `save()`--it is usually called through form validation.

Regarding computed columns, it looks like the specific issue I ran into repeatedly was [fixed in 1.8](https://docs.djangoproject.com/en/2.0/releases/1.8/#query-ex...). I should have been explicit that I was referring to not being able to define such computed columns on the model the way one would a normal column, not to being unable to use `F`-expressions.