They've got a pretty big gulf of social-class-stigma to get past, but it seems like McDonalds is at the beginning of a comeback.
Delivery might be a guilty pleasure gateway.
1,111 karma · joined December 14, 2012
They've got a pretty big gulf of social-class-stigma to get past, but it seems like McDonalds is at the beginning of a comeback.
Delivery might be a guilty pleasure gateway.
1. I want to pay you for this.
2. It will be ripped off a dozen ways, and I would rather see you make money rather instead of some horrible knockoff app-vendor.
The worst time I had with Vagrant was due to an authentication bug in v1.8.5. That was compounded by the previous release (1.8.4) being incompatible with the latest VirtualBox (5.1). Hashicorp was slow to release the fix, and we had to tell users to downgrade both tools. That sucked. This was late summer 2016.
It's been smooth since then, and I haven't had to think much about the VM aspect of our tooling in 6 months.
Hopefully Atlassian can learn from what makes Trello so wonderful instead of JIRA-ifying it into oblivion.
So... powdered sugar?
I've got a pile of old iPads that would be nice to resurrect as displays. I downloaded the Mac app but balked and left at the double-digit price. (not to mention the unknown in-app purchase)
However I do wish the React team would pick between ES6 classes and `React.createClass`. I think I remember the main React tutorial was rewritten in ES6 at one point, but then switched back. I've read arguments both ways, but I suspect they ES6 is still too much of a barrier to entry.
People who aren't up to speed with ES6 will still be shaving a lot of yaks before actually jumping into React.
Most of our creative roles are non-technical, but we like designers to have GitHub accounts to keep an eye on projects and for professional development and education. Those accounts very rarely commit code or assets to a project, but engaging our creative team in technical production has been good for us culturally. In a small way, this was inspired by the design of Pixar's lobby as a creative-technical meeting place.
We also hire a number of outside contractors. $9/month isn't especially onerous, but it is one more cost to keep track of.
To keep our costs the same, we'd probably have to kick the designers out of our GitHub organization. While practical, that sounds and feels terrible. So we did nothing, we're still on our old capped-repo plan and we just archive projects off of GitHub when we run out of slots.
GitHub's new pricing seems incompatible with smaller studios and agencies who encourage collaboration from non-developers or which frequently hire outside contractors. Make it easier to understand how those migrations might work.
- http://google.github.io/material-design-icons/#icon-font-for...
My biggest hesitation about WebPack is that it does too much and duplicates so many other tools. If I'm already using Gulp to watch files and BrowserSync (love!) as my local dev server, why do I need WebPack when I'm only going to be using one of its abilities? Isn't this bloat?
I really like Gulp/Browserify/Watchify/BrowserSync, but I'm starting to feel left behind and need to give WebPack an honest try.
[1]: http://blog.namangoel.com/browserify-vs-webpack-js-drama
Reducing the surface area of roads does not magically remove cars from the roads, it just creates congestion and traffic.
If anything, Uber's model would seem to reduce traffic since their cars are more deliberate vs. taxis' aimlessly wandering.
NYC should try to figure out how to partner with Uber. Taxi's are already expensive enough to be something of a luxury (though filthy), Uber is a far better experience.
Read up on Composer and Packagist. It's basically NPM, Gems, or PyPi for PHP. There are now solid interoperable libraries for most common tasks.
Laravel is a great framework, but quite a bit of what's out there seems to be built on the Symfony foundation.
There are also great coding guidelines and tools that are evolving. The PHP Framework Interoperability Group has produced some solid coding standards and tooling has followed.
WordPress...it makes me sad. But it's ubiquitous. If you're stuck doing WP work, take a look at the Roots project. It's a sane, modern approach with good tooling.
I really wanted to like Carousel. I've tried several times, but somewhere in my Dropbox are a mess of backed up websites, most of which aren't even mine. Scrolling through the very lovely Carousel views wasn't quite as rewarding as the demos when the photos I cared about were mixed up with stock photo thumbnails, web graphics and other junk.
Dropbox bought cloud photo services SnapJoy and Loom, they've got good people. But the letting the ability to filter content fall by the wayside for years was a terrible failure of design and likely contributed to Carousel's foundering.
DEV-on?
de-VWAN? (like Juan)
dev-oo-ahn?