<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Chris Gmyr on Medium]]></title>
        <description><![CDATA[Stories by Chris Gmyr on Medium]]></description>
        <link>https://medium.com/@cmgmyr?source=rss-532198eae774------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*PdaF6SQ2NzAQHfsVuKnXqQ.jpeg</url>
            <title>Stories by Chris Gmyr on Medium</title>
            <link>https://medium.com/@cmgmyr?source=rss-532198eae774------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:51:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cmgmyr/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Revisiting Our Work]]></title>
            <link>https://medium.com/@cmgmyr/revisiting-our-work-ee6fe366142?source=rss-532198eae774------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee6fe366142</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[laravel]]></category>
            <category><![CDATA[rails]]></category>
            <category><![CDATA[best-practices]]></category>
            <dc:creator><![CDATA[Chris Gmyr]]></dc:creator>
            <pubDate>Wed, 28 Feb 2018 15:26:02 GMT</pubDate>
            <atom:updated>2023-10-10T20:37:50.648Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tLIXa6jWWjxfB-6AYjm2Hg.jpeg" /><figcaption>Image By Kevin <a href="https://unsplash.com/photos/w7ZyuGYNpRQ">https://unsplash.com/photos/w7ZyuGYNpRQ</a></figcaption></figure><p>I recently watched David Heinemeier Hansson’s (<a href="https://twitter.com/dhh">@dhh</a>) video on code comments and refactoring. While it’s interesting to see how he tackles these code changes, the most interesting thing to me is what he said he does with the codebase.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FH5i1gdwe1Ls%3Ffeature%3Doembed%26start%3D212&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DH5i1gdwe1Ls&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FH5i1gdwe1Ls%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b4cee23008db9ef95dfbd2a2e7aa7791/href">https://medium.com/media/b4cee23008db9ef95dfbd2a2e7aa7791/href</a></iframe><blockquote><em>“I read through the entire codebase of Basecamp 3 and try to make things better that I don’t think are good enough, or revisit decisions that we’ve made earlier that I think now I have a better idea of how to do”</em></blockquote><p>There’s a lot in that statement, so let’s unpack it.</p><p>First, he reads through the <em>entire</em> codebase! The fact that he does this shows great care for what he does and believes in.</p><p>Second, he makes changes where he doesn’t feel like the code is <em>good enough</em>. While many of us have ideas about what is “good” or not, I’m sure we’ve all gone back through older code and just known when we’ve seen it.</p><p>Lastly, he revisits past decisions that can be better handled now. Programming is an ever-changing space and developers are enhancing their skills and knowledge on a daily basis. So why shouldn’t our code reflect our most up-to-date understandings?</p><p>DHH isn’t the only one who does this though. <a href="https://twitter.com/taylorotwell">Taylor Otwell</a> (creator of Laravel) does something similar.</p><h3>Taylor Otwell 🏄‍♂️ on Twitter</h3><p>Finished read-through and re-factor of the entire framework. Now polishing up Dusk for release!</p><p>Going through code and documentation that you’ve already worked on isn’t the most glamorous job, even quite tedious, but necessary. It’s silly to think that something that was done years, weeks, or even days ago is still “good enough” for today.</p><p>I know I’ve fallen into the habit of not revisiting what I’ve worked on long ago — and maybe some projects don’t need it. However, if the public is using it — like in a current site, app, or package it might be time to take a look through for improvements.</p><h3>Next Steps</h3><p>I’m going to take a hard look at my <a href="https://github.com/cmgmyr/laravel-messenger">messenger</a> package (which needs some love) as well as a few side projects that I haven’t worked on in a while. What projects are you going to look at? Let’s share some successes with each other. Send me a tweet or screenshot on <a href="https://twitter.com/cmgmyr">Twitter</a>, or leave a comment below.</p><p><em>Originally published at </em><a href="https://chrisgmyr.dev/revisiting-our-work-ee6fe366142"><em>chrisgmyr.dev</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee6fe366142" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to order by all() in Laravel]]></title>
            <link>https://medium.com/@cmgmyr/how-to-order-by-all-in-laravel-1a308497de55?source=rss-532198eae774------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a308497de55</guid>
            <category><![CDATA[eloquent]]></category>
            <category><![CDATA[laravel]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Chris Gmyr]]></dc:creator>
            <pubDate>Wed, 31 May 2017 21:19:48 GMT</pubDate>
            <atom:updated>2023-10-10T20:39:02.969Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nzxfolXpDo2tjN5AkU_odg.jpeg" /><figcaption>Photo By <a href="https://unsplash.com/@iammrcup">Fabien Barral</a></figcaption></figure><p>One common issue that I see with Laravel newcomers is that they have <a href="https://stackoverflow.com/questions/17553181/laravel-4-how-to-order-by-using-eloquent-orm/18289241#18289241">hangups</a> using Eloquent correctly. The most basic reference given in the documentation and tutorials is using the all() method.</p><pre>$users = User::all();</pre><p><strong>But what happens when you want to sort your users?</strong></p><p>As a newcomers to the framework, I feel like most are too excited to “jump in and build something” instead of <a href="https://laravel.com/docs/5.4/eloquent#retrieving-models">learning more</a> about it. (But who can blame them, right?!?) So something like this would happen:</p><pre>$users = User::all()-&gt;orderBy(&#39;name&#39;, &#39;ASC&#39;); </pre><pre># BadMethodCallException with message &#39;Method orderBy does not exist.&#39; </pre><pre>// or </pre><pre>$users = User::orderBy(&#39;name&#39;, &#39;ASC&#39;)-&gt;all(); </pre><pre># BadMethodCallException with message &#39;Call to undefined method Illuminate\Database\Query\Builder::all()&#39;</pre><h3>Forget about all()</h3><p>In my experience, I’ve never needed an unordered dump of data in an application.</p><p>Note that all() is a convenience method for get() but does not allow you to chain additional methods. <a href="https://github.com/laravel/framework/blob/5.4/src/Illuminate/Database/Eloquent/Model.php#L340">Take a look</a>:</p><pre>public static function all($columns = [&#39;*&#39;])<br>{<br>    return (new static)-&gt;newQuery()-&gt;get(<br>        is_array($columns) ? $columns : func_get_args()<br>    );<br>}</pre><p>By using get() you’ll be able to achieve the desired results.</p><pre>$users = User::orderBy(&#39;name&#39;, &#39;ASC&#39;)-&gt;get(); </pre><pre>// and </pre><pre>$users = User::where(&#39;email&#39;, &#39;LIKE&#39;, &#39;%@gmail.com&#39;)<br>    -&gt;orderBy(&#39;name&#39;, &#39;ASC&#39;)-&gt;get();</pre><p>So any time you reach for the all() method, I highly recommend using get() instead.</p><p><em>Originally published at </em><a href="https://chrisgmyr.dev/how-to-order-by-all-in-laravel-1a308497de55"><em>chrisgmyr.dev</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a308497de55" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prioritizing Queued Jobs in Laravel]]></title>
            <link>https://medium.com/@cmgmyr/prioritizing-queued-jobs-in-laravel-6f1b688acc1d?source=rss-532198eae774------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f1b688acc1d</guid>
            <category><![CDATA[laravel]]></category>
            <category><![CDATA[message-queue]]></category>
            <category><![CDATA[php]]></category>
            <category><![CDATA[redis]]></category>
            <dc:creator><![CDATA[Chris Gmyr]]></dc:creator>
            <pubDate>Tue, 10 Jan 2017 16:34:49 GMT</pubDate>
            <atom:updated>2023-10-10T20:40:27.681Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tPLQWU0sdyJZ3f4jGV7Y5A.jpeg" /><figcaption>Photo By Paul Dufour — <a href="https://unsplash.com/@bill_bokeh">https://unsplash.com/@bill_bokeh</a></figcaption></figure><p>Laravel queues allow you to defer long running, or resource intensive, processes until a later time. A queue system is imperative for larger applications, but can be helpful for smaller ones as well. But with so many jobs and queues, how can we prioritize them?</p><p>On a current project, I had to figure out how to grab a ton of data from an API (Facebook) that had dependent data — meaning the script cannot proceed to get new data before it’s done with the current data set. This typically ended up being an ID that was needed for the next call as well as some data that needed to be processed.</p><p>In pseudo code, this would look something similar to:</p><pre>$a = $get-&gt;a();<br>$b = $get-&gt;b($a); <br>$c = $get-&gt;c($b); <br>$this-&gt;doSomethingWith($c);</pre><p>As you can see, the code should not move ahead without processing the previous data. In my situation, I had to process all of the “A” jobs, then all of the “B” jobs, and so on, before continuing.</p><p>The data that I needed was quite large and each round needed a good amount of processing before continuing to the next step. Luckily this is where <a href="https://laravel.com/">Laravel</a> and its queue system stepped in to help!</p><p>Laravel let’s you specify a dynamic queue name along with a job, like so:</p><pre>dispatch((new JobA($data))-&gt;onQueue(&#39;a&#39;));</pre><p>In my application in each “JobA” a “JobB” would be called. For each “JobB” a “JobC” would be called. At the end of “JobC”, we’d do some additional work on the whole data collection. So you’d get something like this:</p><pre>// In Controller<br>dispatch((new JobA($data))-&gt;onQueue(&#39;a&#39;)); </pre><pre>// In JobA<br>dispatch((new JobB($data))-&gt;onQueue(&#39;b&#39;));</pre><pre>// In JobB<br>dispatch((new JobC($data))-&gt;onQueue(&#39;c&#39;));</pre><pre>// In JobC<br>dispatch((new JobFinish($data))-&gt;onQueue(&#39;finish&#39;));</pre><p>I wanted to make sure we ran all of the jobs in order, and only continued onto the next set of jobs once the current batch was finished. This was very important since the application could easily have 20, or so, JobAs, 50 JobBs, and hundreds of JobCs.</p><p>In my supervisor config file, I added something similar to this:</p><pre>[program:artisan-queue]<br>command = php artisan queue:work --queue=a,b,c,finish</pre><p>Now all of the jobs on the “a” queue would have to finish before the “b” jobs would start, and “c” would wait for “b”, and so on.</p><p>So there you have it — a prioritized queuing system in only a few lines of code!</p><p>The Laravel Queue system is very robust, and if you haven’t used it, I’d highly recommend trying them in your next project. You can read more about the queue system and queue priorities <a href="https://laravel.com/docs/5.3/queues#queue-priorities">here</a>.</p><p><em>Originally published at </em><a href="https://chrisgmyr.dev/prioritizing-queued-jobs-in-laravel-6f1b688acc1d"><em>chrisgmyr.dev</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f1b688acc1d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moving from self-hosted image service to Cloudinary]]></title>
            <link>https://medium.com/@cmgmyr/moving-from-self-hosted-image-service-to-cloudinary-bd7370317a0d?source=rss-532198eae774------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd7370317a0d</guid>
            <category><![CDATA[web-performance]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[image-processing]]></category>
            <category><![CDATA[cloudinary]]></category>
            <dc:creator><![CDATA[Chris Gmyr]]></dc:creator>
            <pubDate>Tue, 28 Jun 2016 17:59:13 GMT</pubDate>
            <atom:updated>2023-10-10T20:41:32.399Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*7CrSGB37vYF6kWga4PbJGA.png" /></figure><p>Image manipulation is hard. Handling images in the long term is even harder. Here at <a href="http://about.dose.com/">Dose</a> we have a lot of images and a number of ways to serve them. We have Android and iOS apps, as well as completely responsive websites, so each image has the potential of getting manipulated multiple times depending on the device, orientation, and how we optimize an image for a certain platform.</p><h3>Handling this ourselves</h3><p>We used to have an internal image service that took an author’s uploaded image and handled some pre-processing. On upload, we’d make sure it’s within a max width and encoded correctly. Animated <strong>GIF</strong>? We’d have to convert the file to <strong>MP4</strong> and <strong>WEBM</strong> also. This would end up adding extra load on our servers and more space taken in our S3 account.</p><p>When an asset was requested with a certain height/width combination we’d check to see if we had it in our S3 bucket. If not we’d return the master asset and kick off a queue job to create it then add it to the bucket for the next request. As you can imagine, the usage was huge. Want to change the article promo image from 500px width to 475px width? That would invalidate all previous images and we’d need to recreate all new images the next time they were requested. What a mess!</p><p>If your product is not image manipulation, then don’t do this yourself. Services like Cloudinary do this much more efficiently and much better than you will, so use them. And if you’re worried about the cost, think about how much it’ll cost you in development and upkeep, as well as hosting, storage, and delivery costs. More on that later.</p><h3>Getting Started with Cloudinary</h3><blockquote>Cloudinary is the market leader in providing a comprehensive cloud-based image management solution. Cloudinary is being used by tens of thousands of web and mobile application developers all around the world, from small startups to large enterprises. We are here to cover your every image-related need.</blockquote><p><a href="http://cloudinary.com/about">Source</a></p><p>Cloudinary has taken the massive task of handling and manipulating images and broke it down to something very simple — URL manipulation.</p><p>Take the following image url:</p><pre><a href="http://res.cloudinary.com/demo/image/upload/sample.jpg">http://res.cloudinary.com/demo/image/upload/sample.jpg</a></pre><p>Let’s say we’d like to resize this to a max width of 300px, you’d get</p><pre><a href="http://res.cloudinary.com/demo/image/upload/w_300/sample.jpg">http://res.cloudinary.com/demo/image/upload/w_300/sample.jpg</a></pre><p>How about we restrict the height to 150px</p><pre><a href="http://res.cloudinary.com/demo/image/upload/w_300,h_150/sample.jpg">http://res.cloudinary.com/demo/image/upload/w_300,h_150/sample.jpg</a></pre><p>Well, we got the size that we wanted, but it looks <a href="http://res.cloudinary.com/demo/image/upload/w_300,h_150/sample.jpg">pretty bad</a> right now. We’ll need to make some adjustments. Let’s <strong>crop</strong> it to <strong>fit</strong> the space that we need</p><pre><a href="http://res.cloudinary.com/demo/image/upload/w_300,h_150,c_fit/sample.jpg">http://res.cloudinary.com/demo/image/upload/w_300,h_150,c_fit/sample.jpg</a></pre><p>Yeah, <a href="http://res.cloudinary.com/demo/image/upload/w_300,h_150,c_fit/sample.jpg">this looks a lot better</a>!</p><h3>Combining Transformations</h3><p>Combining transformations is just as straightforward as single transformations, all you have to do is add another segment to the URL</p><pre><a href="http://res.cloudinary.com/demo/image/upload/w_300,h_150/c_crop,w_50,h_50,x_100,y_75/sample.jpg">http://res.cloudinary.com/demo/image/upload/w_300,h_150/c_crop,w_50,h_50,x_100,y_75/sample.jpg</a></pre><p>So with this example we are:</p><ol><li>Resizing the image to 300px X 150px then</li><li>Cropping the image to be 50px X 50px and moving the X, Y point to 100, 75 in order to focus in on the <a href="http://res.cloudinary.com/demo/image/upload/w_300,h_150/c_crop,w_50,h_50,x_100,y_75/sample.jpg">yellow part</a> of one of the flowers.</li></ol><p><a href="http://cloudinary.com/documentation/image_transformations#chained_transformations">Learn more</a></p><h3>File Type Transformations</h3><p>This is by far one of the most powerful features of Cloudinary. Say we are uploading a <strong>GIF</strong>, but want to optimize it and change it to a <strong>MP4</strong>.</p><pre><a href="http://res.cloudinary.com/demo/image/upload/kitten_fighting.gif">http://res.cloudinary.com/demo/image/upload/kitten_fighting.gif</a></pre><p>would turn into</p><pre><a href="http://res.cloudinary.com/demo/image/upload/kitten_fighting.mp4">http://res.cloudinary.com/demo/image/upload/kitten_fighting.mp4</a></pre><p>Just by changing the extension of the file in the URL will make this conversion for you. No more keeping track of different file references or different hashes. Only ask for a different file extension!</p><p><a href="http://cloudinary.com/blog/reduce_size_of_animated_gifs_automatically_convert_to_webm_and_mp4">Learn more</a></p><h3>Programmatic SDKs</h3><p>It’s all well and good that we can convert any file asset via a URL, but if you want to make these changes more programmatically, you can use one of their many SDKs. For this example, we’ll be using their <a href="https://github.com/cloudinary/cloudinary_php">PHP SDK</a></p><p>In my initial example, we ended with the final URL of</p><pre><a href="http://res.cloudinary.com/demo/image/upload/w_300,h_150,c_fit/sample.jpg">http://res.cloudinary.com/demo/image/upload/w_300,h_150,c_fit/sample.jpg</a></pre><p>for our image. In the PHP SDK, we’d be able to do</p><pre>$transformations = [&#39;width&#39; =&gt; 100, &#39;height&#39; =&gt; 150, &#39;crop&#39; =&gt; &#39;fill&#39;];<br>$url = cloudinary_url(https://medium.com/&#39;sample.jpg&#39;,%20$transformations);</pre><p>and multiple transformations, like our second example, would look like</p><pre>$transformations = [&#39;transformation&#39; =&gt; [<br>   [&#39;width&#39; =&gt; 300, &#39;height&#39; =&gt; 150],<br>   [&#39;width&#39; =&gt; 50, &#39;height&#39; =&gt; 50, &#39;crop&#39; =&gt; &#39;crop&#39;, &#39;x&#39; =&gt; 100, &#39;y&#39; =&gt; 75]<br>]];<br>$url = cloudinary_url(https://medium.com/&#39;sample.jpg&#39;,%20$transformations);</pre><h3>Migrating to Cloudinary</h3><p>Cloudinary has taken the hard work out of migrating assets over to their platform. There are currently a few options to choose from.</p><ol><li>Add a full URL to your current image and Cloudinary will automatically pull this in for you.</li><li>Set up an auto upload mapping to your S3 bucket. When this “virtual” directory is requested, it will pull the asset from your bucket into your Cloudinary account.</li></ol><p><a href="http://cloudinary.com/blog/how_to_automatically_migrate_all_your_images_to_the_cloud">Learn more</a></p><h3>Why We Chose Cloudinary</h3><p>Before moving forward with anything new, we went through a diligent research period where we were looking at a handful of SaaS options as well as possibly redesigning our current in-house system. As we worked through the options one thought became very clear — handling our own system didn’t make sense. There are a good handful of services that are more cost effective and feature rich than something that we could ever make. Our business is not handling images. Just the cost of AWS instances, storage, and CDN fees were tens of thousands of dollars per month. Now take developer costs to maintain and add to the system, and it adds up quickly. But even more importantly, each time something would break or need to be added to our image service, it would take attention away from more important tasks or services.</p><p>After evaluating a number of image and CDN services, we moved forward with Cloudinary for a number of reasons:</p><ol><li><strong>They were very attentive.</strong> They set up multiple meetings with their sales and tech teams to answer all of our questions and to help get us the best price for the resources we need. Even now, after the “sale”, they continue to reach out personally to share new features that haven’t been published yet and check in on analytics and our performance.</li><li><strong>Price.</strong> Their price is a LOT cheaper than running all of our instances, storage, and CDN through AWS.</li><li><strong>Features.</strong> The flexibility and amount of features they have for image handling is impressive and there would be no realistic way that we’d have the bandwidth in order to make similar features ourselves. Their system makes it very easy to make adjustments on the fly to see what combinations perform, and look better.</li><li><strong>Uptime.</strong> Since the majority of our content is showing images, if the images aren’t available we aren’t able to provide the value to our users that we need to. Since moving to Cloudinary, our image uptime has been spectacular and image responsiveness has been significantly faster too.</li></ol><h3>Summary</h3><p>We have simplified our image handling process over the last 6 months since starting to work with Cloudinary. They can easily handle our <strong>4.5 Million images</strong> (and counting) and over <strong>1.4 Billion requests per month</strong>. They also provide insight to help us further improve our performance on our sites. Site performance and user experience are not taken lightly, so we are very happy with our decision to utilize their services. Some other helpful points are</p><ul><li><a href="http://cloudinary.com/documentation">Great documentation</a></li><li>A bunch of <a href="http://cloudinary.com/addons">add-on plugins</a> like JPEGmini and Imagga</li><li>Tons of transformation options like <a href="http://cloudinary.com/blog/adding_watermarks_credits_badges_and_text_overlays_to_images">watermarks</a>, <a href="http://cloudinary.com/cookbook/pixelate_an_image_or_a_region">custom pixelation</a>, and even <a href="http://cloudinary.com/cookbook/convert_pdf_to_jpg">PDF to image</a> conversion</li><li>Automatic <a href="http://cloudinary.com/blog/introducing_intelligent_responsive_image_breakpoints_solutions">responsive image</a> handling</li><li>Video <a href="http://cloudinary.com/documentation/video_management">management and transformations</a></li><li><a href="http://cloudinary.com/blog/automatic_backup_of_user_uploaded_images_using_cloudinary">Automatic backups to S3</a></li><li>Newly introduced “<a href="http://cloudinary.com/blog/introducing_smart_cropping_intelligent_quality_selection_and_automated_responsive_images">Auto Everything</a>”</li></ul><p>As an aside, we’re just sharing this article and information as happy customers. Cloudinary did not commission this article nor give us any incentive for writing it. We just want to share our experience.</p><p><em>This article was originally posted on </em><a href="https://chrisgmyr.dev/moving-from-self-hosted-image-service-to-cloudinary-bd7370317a0d"><em>chrisgmyr.dev</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd7370317a0d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>