<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Syntax on Amit Kohli</title><link>https://www.amitkohli.com/tags/syntax/</link><description>Recent content in Syntax on Amit Kohli</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Amit Kohli</copyright><lastBuildDate>Wed, 01 Feb 2017 17:16:57 +0000</lastBuildDate><atom:link href="https://www.amitkohli.com/tags/syntax/index.xml" rel="self" type="application/rss+xml"/><item><title>Announcing ShinyTester - a package that helps you build Shiny apps</title><link>https://www.amitkohli.com/announcing-shinytester-a-package-that-helps-you-build-shiny-apps/</link><pubDate>Wed, 01 Feb 2017 17:16:57 +0000</pubDate><guid>https://www.amitkohli.com/announcing-shinytester-a-package-that-helps-you-build-shiny-apps/</guid><description>&lt;p&gt;Shiny is awesome, but can be a bit daunting and easy to make mistakes in. I recently came back to Shiny after a hiatus of a few years and it was much more challenging than I feel comfortable admitting. I was making bonehead mistakes like writing &lt;code&gt;something&lt;/code&gt; instead of &lt;code&gt;output$something&lt;/code&gt;, confusing where to put &lt;code&gt;Output&lt;/code&gt; commands vs &lt;code&gt;Render&lt;/code&gt; commands, etc. I would eventually find my mistake, curse myself and move on with a crumpled ego. Then I had the realization that maybe if I was a beginner, I wouldn&amp;rsquo;t even know what I was doing wrong. Thusly did I conclude that I was in a unique position to help out the R community: Dumb enough to make mistakes, but experienced enough to eventually remember how to resolve them. So naturally, I wrote an R package that tests the code of the Shiny app itself.&lt;/p&gt;</description></item></channel></rss>