Marcus Zarra on the dangers of misinformation:
As developers, we are frequently using the internet to help us solve issues. We run across an error code, a crash, or another type of problem and we usually go to the internet. With the vast amount of knowledge that is available, and the incredible search engines that we have at our disposal, it is pretty easy to find someone else who has already run across the issue. Sites like StackOverflow make it even easier to find other people who have experienced the issue we are running across.
The issue is that we don’t really know if the information being shared with us is accurate. The author of that post, or response, may be guessing. They may have found a hack or workaround that kind of works, for now. They may be completely wrong and are treating a symptom as the actual problem.
I agree with the premise of this whole article. It’s so hard in the ever changing world of tech to know what is still accurate and what isn’t. Just today I had to update a tutorial I wrote back in September. The basics of it was the same, but the dependencies changed enough to make it not work and in turn cause frustration for readers.
I’ve noticed in my own searching habits, that when looking for tutorials I always look for the published date. If it’s over six months old chances are it isn’t even accurate.
A few months back I created a tutorial on Setting up Gulp, Bower, Bootstrap Sass, & FontAwesome. If you had problems with the tutorial I’m sorry. Apparently the
gulp-ruby-sass npm module I used is undergoing some changes causing the SASS to error out and never compile. I have updated that post to recommend sticking with version
^0.7.1 until v1 stables out.
I’ve also created a GitHub repo with everything setup. This way you can see the exact versions of dependencies I used in the tutorial.
What I do find odd is I had a similar problem with Laravel Elixir a few weeks back. It uses node-sass but something must be going on with the development of both of these plugins. Hopefully, it will all be sorted out and I can stop pulling out my hair.
There are certain times when using Laravel that you would like to migrate and seed the database. Typically this is done via the Artisan command line tool with:
php artisan migrate --seed
You can also call this in your code with the following:
Artisan::call('migrate', ['--seed' => true]);
Nice and simple but the second parameter always trips me up.
Pro Tip: don’t babysit that time consuming command line task. Just tack on “; say ‘finished doing X'” and let your computer tell you.
Continue reading “Use the “Say” command for long running tasks”
Behind the App is a new documentary style podcast series about iOS app development. It has the feel of the popular Serial podcast and sets a new bar for other tech podcasts.
I’m personally excited about this and I’m hoping it starts a shift to a more polished style. Instead of the typical, here’s our guest, now we’ll talk for an hour.