I'm a trustee on the board of a very small village in Illinois. There was a vote to allow the gaming before I got on the board, and only one vote since then to approve a new license for an establishment. I argued the income-vs-sleaze ratio was lousy, but was out-voted. I wish I'd had this article and its facts to back up my more emotional reasoning for not liking it.
Video gambling is indeed a blight, even if it is profitable, but this article only makes it more depressing to see just how worthless (or actively punitive) it is to all but the companies that apparently wrote the original legislation.
Without context, working for free requires careful thought. But in the context of this conversation "free" means without monetary compensation, but you're still receiving the benefit of the mentorship (and thus not free).
TLDR; No one's advocating working for free. The Warren Buffett approach is "trade money for time with a good mentor."
I don't see Gitlab explicitly listed as a supported service, but wonder if that would be supported or require google or gitlab to make the integration happen. (This is on a GL EE instance we manage).
And what about public-facing web apps developed in-house? Can we add SAML integrations that would work with this for employee access?
These are probably basic questions, but I couldn't seem to find the details on the site.
I think you meant "redacted" vs "retracted". But yeah, there are a lot of stories out there of people assuming a black bar over black text is high security.
Will second the #2 recommendation above - I have a fair amount of sidewalk in front of my house and the front of my office that I bought the snow pushers for. They're fast and move a lot of snow with minimal heavy breathing. 4 years and zero heart attacks. =)
Whatever mechanism makes it likely you'll keep posting is the right one. Thanks a bunch for highlighting some thoughtful approaches to basic design decisions that often get overlooked. The effort is appreciated.
Apropos of nothing, but I just migrated a site to metalsmith, and I've really enjoyed the results and ease of building out any functionality that was lacking in the framework (though most needs were met already).
As with the others, backed it on KS, and I don't feel like you owe me anything more than what you've provided. Keep the money, and do something to keep your dream moving forward.
We dislike managing PG too, so we've been migrating to https://www.compose.io/postgresql/ It's not for every situation, but they have replication and failover and downloadable daily backups with the option for SSH-only access. Been using them for about 6 months on some smaller DB projects, and haven't had any hiccups.
We went through various configurations/deployments of ES in-house, and eventually outsourced the job. The fickle nature of cluster restarts/upgrades were frustrating along with the unassigned & lost indexes that would often result. Then there were cluster partitions that wouldn't heal without a lot of manual intervention.
The tradeoff in value wasn't worth the time it was requiring, so we outsourced to compose.io -- they've been a good fit price & stability-wise, and feel pretty close to a blackbox for the benefit. If you need a large cluster however, you'll pay handsomely with any of the SaaS providers when last I looked at it. For large quantity work we've moved to AWS Redshift.
I've felt a similar pull away from django on a number of apps. Just looking through the Channel docs [0] however, many of the reasons I get frustrated with Django (primarily the lack of a solid websocket/SSE story) are being addressed. Frankly, I'm addicted to Django's built in auth & admin UI, and I'm thrilled I won't have to bolt on a kludged solution if I want to get some realtime behavior. My frankenstein chat system of Node & Django can be put out of its misery... someday.
The mug is as close as I get to woodworking on most days, unfortunately.