<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for scottgardner</title><link>http://disqus.com/by/scottgardner/</link><description></description><atom:link href="http://disqus.com/scottgardner/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 07 Feb 2022 08:10:35 -0000</lastBuildDate><item><title>Re: Dear Wilson</title><link>https://www.davidhoang.com/blog/dear-wilson#comment-5724892982</link><description>&lt;p&gt;So touching. Thanks for sharing. Very sorry for your loss. But I’m even happier for your gain, that is, nearly twenty years of having such a great friend by your side.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Mon, 07 Feb 2022 08:10:35 -0000</pubDate></item><item><title>Re: Tips for using Xcode Playground</title><link>https://fluffy.es/tips-for-using-xcode-playground-reduce-crash-lol/#comment-3900324530</link><description>&lt;p&gt;Nice article 👏 You can also call `PlaygroundPage.current.finishExecution()` in completion handlers (and also in any error handling) so that you don't have to remember to click the Stop button.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Mon, 14 May 2018 13:06:41 -0000</pubDate></item><item><title>Re: 
                
                The Right Way To Write a Singleton
                
              </title><link>http://krakendev.io/blog/the-right-way-to-write-a-singleton#comment-2970186017</link><description>&lt;p&gt;In case anyone is interested in how to define a singleton that has properties that can be set during initialization:&lt;/p&gt;&lt;p&gt;&lt;a href="http://stackoverflow.com/a/40269575/616764" rel="nofollow noopener" target="_blank" title="http://stackoverflow.com/a/40269575/616764"&gt;http://stackoverflow.com/a/...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Wed, 26 Oct 2016 14:25:54 -0000</pubDate></item><item><title>Re: ABI Compatibility: Whoopdty Do, What Does It All Mean?</title><link>http://www.bensnider.com/abi-compatibility-whoopdty-do-what-does-it-all-mean.html#comment-2702802978</link><description>&lt;p&gt;My reaction to the announcement was that, lack of ABI stability implies that there will not be API compatibility, either. I think that is where the rub is for the majority of developers, and for anyone wanting to learn Swift, or publish educational material about Swift. It makes it not only more challenging to develop apps using Swift, but also to learn or teach Swift. If there are going to be breaking changes in a future release--no matter what--then why not stabilize Swift for now and run those breaking changes all at once?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Mon, 30 May 2016 08:41:57 -0000</pubDate></item><item><title>Re: Creating Your First CocoaPod</title><link>http://code.tutsplus.com/tutorials/creating-your-first-cocoapod--cms-24332#comment-2694375606</link><description>&lt;p&gt;Great post, thanks!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Wed, 25 May 2016 07:18:01 -0000</pubDate></item><item><title>Re: On benchmarks</title><link>http://ruiper.es/2015/11/23/on-benchmarks/#comment-2631650619</link><description>&lt;p&gt;Thanks for this post and the tests! I created a project to run your tests: &lt;a href="https://github.com/scotteg/ReactiveTesting" rel="nofollow noopener" target="_blank" title="https://github.com/scotteg/ReactiveTesting"&gt;https://github.com/scotteg/...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Tue, 19 Apr 2016 10:51:51 -0000</pubDate></item><item><title>Re: Capturing Reference Types</title><link>http://as.ync.io/capturing-reference-types/#comment-2610853065</link><description>&lt;p&gt;bindNext(_:) includes error handling. It calls subscribe(_:onError:) and throws a fatal error onError (in DEBUG). subscribeNext(_:) only handles onNext and does not throw an error.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Thu, 07 Apr 2016 06:19:42 -0000</pubDate></item><item><title>Re: I 💖 Storyboards &amp;#038; Nibs</title><link>https://www.natashatherobot.com/i-heart-storyboards-nibs/#comment-2593042463</link><description>&lt;p&gt;I completely agree, and actually just released a course on &lt;a href="http://lynda.com" rel="nofollow noopener" target="_blank" title="lynda.com"&gt;lynda.com&lt;/a&gt; this subject. Interface Builder is not without its own learning curve, and challenges at times. Yet I prefer to use IB over code for several reasons. I find it much easier to design visually. Doing so also benefits collaboration with clients, designers, and product managers. I as well as our designers design directly in storyboards (and use PaintCode to create UI elements, custom controls, etc.). Every line of code you don't write is a line of code you don't have to write...or test, or maintain; when Apple changes UI or AL APIs, storyboards will automatically be updated. Stack views make laying out UIs--even complex ones--much easier than using AL constraints. And as you mentioned, storyboard references making breaking up large storyboards into multiple ones easy, which addresses the issue of using storyboards on teams. The one issue that still remains is that just accessing a storyboard file marks it dirty for source control, so you have to remember to discard unintended changes before committing. We use a Trello board to keep track of who has what storyboards checked out. This is a small price to pay for all the advantages.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Mon, 28 Mar 2016 10:28:12 -0000</pubDate></item><item><title>Re: 
                
                The Right Way To Write a Singleton
                
              </title><link>http://krakendev.io/blog/the-right-way-to-write-a-singleton#comment-2347527980</link><description>&lt;p&gt;I linked to this article in my &lt;a href="http://lynda.com" rel="nofollow noopener" target="_blank" title="lynda.com"&gt;lynda.com&lt;/a&gt; course Swift 2.0 Essential training (Working with Singletons in chapter 8 at 2:21). &lt;a href="http://www.lynda.com/Swift-tutorials/Working-singletons/422096/447985-4.html" rel="nofollow noopener" target="_blank" title="http://www.lynda.com/Swift-tutorials/Working-singletons/422096/447985-4.html"&gt;http://www.lynda.com/Swift-...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Sat, 07 Nov 2015 11:19:44 -0000</pubDate></item><item><title>Re: 
                
                The Right Way To Write a Singleton
                
              </title><link>http://krakendev.io/blog/the-right-way-to-write-a-singleton#comment-2150743182</link><description>&lt;p&gt;You have to put the class in a different file in order to effect scope (otherwise private is still scoped to the main playground file, so the init() is still accessible). Check out this repo which also has a playground with the class defined in a separate file in Sources: &lt;a href="https://github.com/scotteg/SwiftSingleton" rel="nofollow noopener" target="_blank" title="https://github.com/scotteg/SwiftSingleton"&gt;https://github.com/scotteg/...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Wed, 22 Jul 2015 07:48:20 -0000</pubDate></item><item><title>Re: 
                
                The Right Way To Write a Singleton
                
              </title><link>http://krakendev.io/blog/the-right-way-to-write-a-singleton#comment-2149113229</link><description>&lt;p&gt;Here's a repo of the project I created for that screenshot, and a playground, too: &lt;a href="https://github.com/scotteg/SwiftSingleton" rel="nofollow noopener" target="_blank" title="https://github.com/scotteg/SwiftSingleton"&gt;https://github.com/scotteg/...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Tue, 21 Jul 2015 12:12:45 -0000</pubDate></item><item><title>Re: 
                
                The Right Way To Write a Singleton
                
              </title><link>http://krakendev.io/blog/the-right-way-to-write-a-singleton#comment-2148808807</link><description>&lt;p&gt;Great post, thanks! Here's a screenshot showing the one-liner: &lt;a href="http://bit.ly/SwiftSingleton" rel="nofollow noopener" target="_blank" title="http://bit.ly/SwiftSingleton"&gt;http://bit.ly/SwiftSingleton&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Tue, 21 Jul 2015 10:10:38 -0000</pubDate></item><item><title>Re: RestKit - CoreData - NSScreencast</title><link>https://nsscreencast.com/episodes/52-restkit-coredata#comment-1557414195</link><description>&lt;p&gt;In the project for this episode, you inadvertently did not set the mapping identificationAtttributes property. As a result, every launch inserts a new set of beer styles (currently 162 records). This is not noticeable in the UI, though, because you're setting the data source to the response array, vs., e.g., using a fetch results controller. Add the following to +[MappingProvider beerStyleMapping] to resolve the issue:&lt;/p&gt;&lt;p&gt;mapping.identificationAttributes = @[@"styleId"];&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Sun, 24 Aug 2014 17:16:29 -0000</pubDate></item><item><title>Re: CSS3 rem units</title><link>http://www.sitepoint.com/css3-rem-units/#comment-1167636596</link><description>&lt;p&gt;Great explanation of Rems. Thanks!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Tue, 17 Dec 2013 12:09:51 -0000</pubDate></item><item><title>Re: Is One Company About to Lock Up the Electronic Medical Records Market?</title><link>http://www.theatlantic.com/technology/archive/2012/06/is-one-company-about-to-lock-up-the-electronic-medical-records-market/258473/#comment-1053902178</link><description>&lt;p&gt;The problem for long-time client-server-based solutions is how to get out of their own way (they're encumbered by their old code), and not only embrace the paradigm shift to cloud technologies, but help to _better_ it. It's going to take pioneering minds with deep industry insight to solve this problem, to innovate new approaches to interface and exchangeability, and influence behavior change starting with the patient. In other words, as you alluded, healthcare needs an Apple.&lt;/p&gt;&lt;p&gt;My company is tackling one important aspect of this challenge to create interoperability. Over half of America's physicians are _still_ self-employed, and a majority of those private practices run on client-server-based practice management and clinical systems. We are helping this contingent to extend the capabilities of their current system up into the cloud.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Sat, 21 Sep 2013 10:02:08 -0000</pubDate></item><item><title>Re: The Biopsy |During medical school, we’re supposed to train on...|</title><link>http://www.thebiopsy.com/post/59168220291#comment-1020406879</link><description>&lt;p&gt;This is brilliant, and I think entirely do-able.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Wed, 28 Aug 2013 07:44:54 -0000</pubDate></item><item><title>Re: 10 Crucial Sublime Text 2 Plugins for the PHP Craftsman</title><link>http://www.neverstopbuilding.com/sublime-plugins-for-php#comment-888413468</link><description>&lt;p&gt;I ran php-cs-fixer with the -psr0 parameter but it still did not resolve any of the issues.&lt;/p&gt;&lt;p&gt;Here's the code...&lt;br&gt;&lt;a href="https://gist.github.com/scotteg/781af08d43735efd888b" rel="nofollow noopener" target="_blank" title="https://gist.github.com/scotteg/781af08d43735efd888b"&gt;https://gist.github.com/sco...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;I appreciate your help!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Tue, 07 May 2013 15:04:44 -0000</pubDate></item><item><title>Re: 10 Crucial Sublime Text 2 Plugins for the PHP Craftsman</title><link>http://www.neverstopbuilding.com/sublime-plugins-for-php#comment-888119117</link><description>&lt;p&gt;My path settings appear to be correct (it matches which php-cs-fixer)...&lt;br&gt;    // Path to where you have the php-cs-fixer installed&lt;br&gt;    "php_cs_fixer_executable_path": "/usr/local/bin/php-cs-fixer",&lt;/p&gt;&lt;p&gt;When I right-click on a file in Sublime and select PHP Code Sniffer &amp;gt; Fix this file/directory (PHP-CS-Fixer), nothing happens. The file is not fixed. Yet when I run PHP Code Sniffer on the file I do get a list of infractions, e.g., "Closing parenthesis of a multi-line function call must be on a line by itself."&lt;/p&gt;&lt;p&gt;When I run php-cs-fixer on the same file from the CLI, I get an error, "[File] should have at least a vendor namespace according to PSR-0 rules."&lt;/p&gt;&lt;p&gt;When I run php-cs-fixer on a simple test file, e.g., one that has the same closing parenthesis issue, the php-cs-fixer finishes without an error, but the file is unchanged. Running it verbose produces no output, either.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Tue, 07 May 2013 08:47:38 -0000</pubDate></item><item><title>Re: 10 Crucial Sublime Text 2 Plugins for the PHP Craftsman</title><link>http://www.neverstopbuilding.com/sublime-plugins-for-php#comment-884250737</link><description>&lt;p&gt;Thanks for these very useful tips! Is php-cs-fixer working for you?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Sat, 04 May 2013 13:12:31 -0000</pubDate></item><item><title>Re: Zurmo Open Source CRM Releases 1.5</title><link>http://zurmo.org/features/zurmo-open-source-crm-releases-1-5#comment-873433441</link><description>&lt;p&gt;Congrats! Zurmo looks very impressive.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Tue, 23 Apr 2013 13:45:52 -0000</pubDate></item><item><title>Re: The Beard Rocks WWDC &amp;#8212; IT&amp;#8217;S A PARTY!</title><link>http://www.loopinsight.com/2012/05/07/the-beard-rocks-wwdc-its-a-party/#comment-529313664</link><description>&lt;p&gt;Apple &amp;amp; Karaoke, I'm in...can you send me an invite please?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Tue, 15 May 2012 10:42:28 -0000</pubDate></item><item><title>Re: How Doctors Can Use Evernote As A Professional Memory Accessible Anywhere, Part 3: How to Use Evernote as an Electronic Health Record (EHR)</title><link>http://efficientmd.blogspot.com/2008/08/how-doctors-can-use-evernote-as_30.html#comment-2325834</link><description>&lt;p&gt;Really great article, thanks! It was linked to me by a good friend/client (an Osteopath) whom I was discussing the possibilities of Evernote with a while ago. I had called the company to inquire about integrating their technology (e.g., into a client/server app), but never got a response. I also second your sentiments about the Fujitsu ScanSnap and Textexapander. We've set up many offices using these two indispensable tools. Evernote makes it a troika!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott G.</dc:creator><pubDate>Sat, 13 Sep 2008 05:30:48 -0000</pubDate></item></channel></rss>