244 karma · joined April 13, 2015
"GitLab Runners do not offer secure isolation between projects that they do builds for. You are TRUSTING all GitLab users who can push code to project A, B or C to run shell scripts on the machine hosting runner X."
Seems like a very strong reason to use one's own paid DigitalOcean instances for runners instead of using the free shared runners, at least for commercial projects. I was wondering if anyone from GitLab could expand further on this?
To be fair, it was misleading that the WSJ article said "Google is changing its search algorithm Tuesday to favor sites that look good on smartphones."
Automated meaning pip with any arguments run by another script.
1) Desktop-friendly websites appear higher in the rankings for searches made from desktop computers
2) Mobile-friendly websites appear higher in the rankings for searches made from mobile devices
These graphs are very insightful. Thanks for offering us some visibility into the Python package download picture.
Perhaps it's just that sample of developers who skew toward INTJ, ENTJ and INTP.
I suspect that the results would be different in a survey of developers from a more open source-focused community, e.g. if GitHub conducted that survey and a lot of idealistic open source developer types responded.
By this, I mean generating the following individually: 1) the HTML with a class applied to a sample element to be centered 2) the separate CSS for that particular class selector
This is just a little nitpick based on my preference for avoiding inline styles; overall, nice work!
Word and Google Docs do save revision history, but they slow to a crawl when you have a document with a lot of pages, to the point of being unworkable.
Apparently they accept amateur runners and you can do a 10k, half marathon, or full marathon.
However, in between contracts I have the ability to take long breaks to work on my own projects or travel. Overall, the benefits have outweighed the risks for me, but then again, I'm just one data point.
Would it be a combination of 1) demonstrating past successes gaining traction and 2) having a catchy prototype? Or are there other things?
Perhaps similar to how while Google acquires all sorts of interesting startups, it doesn't mean they're shifting away from search/ads.
Part of why the painting is so elegant is because of its balanced composition: the arms along the top of the golden spiral, the table edge along the top of the inner spiral, etc.
On a startup's first MVP iteration, how little graphic design effort can you get away with? Does it depend on the product, perhaps? Should all iterations be visually polished?
Having open-sourced a number of components and then seen them get better from community contributions with little effort, this is a good thing to do.
There seems to be a lot of under-explored potential for building useful, pluggable D3 widgets along these lines. I'd love to see more interactive widgets like this.