<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Chris Briggs</title>
    <description>The latest articles on DEV Community by Chris Briggs (@keskyle17).</description>
    <link>https://dev.to/keskyle17</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F617699%2F7169c190-6f91-4a0c-af57-b6e90ce6e295.jpeg</url>
      <title>DEV Community: Chris Briggs</title>
      <link>https://dev.to/keskyle17</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/keskyle17"/>
    <language>en</language>
    <item>
      <title>Vizhub: VSC Without Hubbub</title>
      <dc:creator>Chris Briggs</dc:creator>
      <pubDate>Sat, 20 Nov 2021 09:18:52 +0000</pubDate>
      <link>https://dev.to/keskyle17/vizhub-vsc-without-hubub-41pd</link>
      <guid>https://dev.to/keskyle17/vizhub-vsc-without-hubub-41pd</guid>
      <description>&lt;p&gt;If you're learning Javascript, React and have an interest in visualising data using the excellent D3 libraries, then check out &lt;a href="https://vizhub.com/"&gt;Vizhub&lt;/a&gt; by Curran Kelleher from &lt;a href="https://datavis.tech/vizhub/"&gt;Datavis.tech&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It's an extremely intuitive, compact online platform that supports collaboration and a forum for those seeking a road into analysis and visualisation. Curran has produced a super informative 17 hour &lt;a href="https://www.youtube.com/watch?v=2LhoCfjm8R4"&gt;free course&lt;/a&gt; on YouTube, via freecodeCamp that takes you on a thorough journey through the functionality of D3 with React.&lt;/p&gt;

&lt;p&gt;The course is given in two parts, and I'm tempted to say start with &lt;a href="https://www.youtube.com/watch?v=H2qPeJx1RDI&amp;amp;t=0s"&gt;Part II&lt;/a&gt;, at least for the first few hours, as Curran explores visualising COVID-19 data. There is some crossover of subject matter between Parts I and II (that's no bad thing), but I found the second part to be gentler for beginners. &lt;/p&gt;

&lt;p&gt;Even if graphs aren't your thing, the application of React in context of data visualisation makes the use of hooks very intuitive. In general, I'm not a fan of 'type-n-teach' tutorials, but Curran has a very engaging and methodical way of instructing that by and large avoids the "&lt;em&gt;and then I do this, and then I do that...&lt;/em&gt;" pitfalls of this style. Regardless of the visualisation focus, I believe this to be one of the best courses for appreciating React itself, its strength and gotchas. &lt;/p&gt;

&lt;p&gt;Vizhub is free, open source, and it supports forking of existing visualisations for practice and analysis. Furthermore, all your projects can be shared publicly as links for free ($5/month for private collaboration).  &lt;/p&gt;

&lt;p&gt;Vizhub is not a replacement for VSC, but it provides a compact platform for learning JS with less fuss, and completely online.&lt;/p&gt;

&lt;p&gt;IMPORTANT: In Part II, the final section on graphs cuts off, so watch the full video &lt;a href="https://www.youtube.com/watch?v=y7DxbW9nwmo&amp;amp;list=PL9yYRbwpkykuK6LSMLH3bAaPpXaDUXcLV&amp;amp;index=58"&gt;here&lt;/a&gt;. &lt;/p&gt;

</description>
      <category>react</category>
      <category>d3</category>
      <category>javascript</category>
      <category>graphs</category>
    </item>
    <item>
      <title>Thinking About Recursion</title>
      <dc:creator>Chris Briggs</dc:creator>
      <pubDate>Mon, 25 Oct 2021 09:54:11 +0000</pubDate>
      <link>https://dev.to/keskyle17/thinking-about-recursion-43h0</link>
      <guid>https://dev.to/keskyle17/thinking-about-recursion-43h0</guid>
      <description>&lt;p&gt;A route into appreciating recursion is to read the following article in &lt;a href="https://tinyurl.com/3jmbsw"&gt;Scientific American&lt;/a&gt;. Learning recursion in terms of algorithms alone is somewhat limiting. It is more than a fancy way of creating loops, and its application is far-reaching within programming. It might be said that recursion is fundamental to thinking like a human, despite its perceived difficulties in conceptualising the process in computers.&lt;/p&gt;

&lt;p&gt;There's an 'inside out' process to recursion, that follows with programming in general. A program is typically a series of mini-puzzles within a puzzle. Many puzzle or adventure games have a primary objective (to win) and secondary objectives in the form of tasks that must be completed in order to continue. An experienced player might be able to devise a strategy to win, having learned and memorised the tactics and consequences of completing each mini-puzzle. A novice player may find completing each mini-game to be enough of a challenge without even considering the consequences.&lt;/p&gt;

&lt;p&gt;An experienced programmer will 'see' patterns that novices haven't encountered. It took me a while to speak Spanish with some confidence because the rules were getting in the way of applying them in conversation; I had to let go of the ropes and speak without thinking, and it took quite a few iterations to do so; words became phrases became sentences became paragraphs, with lots of syntactical rules to take into account. Once I had 'modelled' the sentences, I was able to focus on what I wanted to say, not how to say it. I used the feedback of others to refine my ability, and so I was learning Spanish recursively. It is the same process in programming.&lt;/p&gt;

&lt;p&gt;The mistake I have repeatedly made in programming and learning in general is thinking someone could teach me. I found those with experience often lacked the viewpoint of beginners, and either over-simplified or over-complicated explanations, usually swinging from one to the other with little warning. I found too many explanations were obfuscated with terminology, similar to grammar clouding my Spanish with terms such as 'participles', 'gerunds' and 'conjunctions'. This type of vocabulary is useful to talk to other programmers or linguists, but it tells you nothing how things work; personal practice and failure tell you these things, along with learning to teach.&lt;/p&gt;

&lt;p&gt;Two of my heroes are &lt;a href="https://en.wikipedia.org/wiki/Claude_Shannon"&gt;Claude Shannon&lt;/a&gt; and &lt;a href="https://en.wikipedia.org/wiki/Richard_Feynman"&gt;Richard Feynman&lt;/a&gt; due to the way they applied learning. In his book, &lt;a href="https://www.goodreads.com/book/show/10260.The_Pleasure_of_Finding_Things_Out"&gt;The Pleasure of Finding Things Out&lt;/a&gt;, along with his renowned &lt;a href="https://www.colorado.edu/artssciences-advising/resource-library/life-skills/the-feynman-technique-in-academic-coaching"&gt;learning technique&lt;/a&gt;, Feynman demonstrates that the faculty of learning and teaching are entwined: teach yourself as you mean to teach others, which is a form of recursion.&lt;/p&gt;

&lt;p&gt;So, if you want to learn recursion, study it then write about recursion in a way you and anyone else can understand, or study more until that point.  What better way to appreciate recursion than to embody it in your way of learning.&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>algorithms</category>
    </item>
    <item>
      <title>How I improved my coding</title>
      <dc:creator>Chris Briggs</dc:creator>
      <pubDate>Mon, 05 Jul 2021 15:10:10 +0000</pubDate>
      <link>https://dev.to/keskyle17/how-i-improved-my-coding-33nf</link>
      <guid>https://dev.to/keskyle17/how-i-improved-my-coding-33nf</guid>
      <description>&lt;p&gt;Reading technical books and applying the knowledge instead of watching videos or even using interactive websites had notably increased my retention span and pace of comprehension. The tortoise outpaces the hare.&lt;/p&gt;

</description>
      <category>books</category>
    </item>
    <item>
      <title>Style is servient to content</title>
      <dc:creator>Chris Briggs</dc:creator>
      <pubDate>Sun, 04 Jul 2021 11:31:14 +0000</pubDate>
      <link>https://dev.to/keskyle17/style-is-servient-to-content-4d5g</link>
      <guid>https://dev.to/keskyle17/style-is-servient-to-content-4d5g</guid>
      <description>&lt;p&gt;An extremely short post that highlights a key consideration regarding the use of CSS to style HTML content:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Documents that use style attributes on any of their elements &lt;strong&gt;&lt;em&gt;must still be comprehensible and usable&lt;/em&gt;&lt;/strong&gt; if those attributes were removed. (Section 3.2.6.5 The style attribute)&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This is a direct quote from the &lt;a href="https://html.spec.whatwg.org/#dom"&gt;HTML Spec&lt;/a&gt;, as a reminder that content trumps style and it's a good idea to temporarily disable stylesheets (if feasible) prior to production just to make sure this holds true. &lt;/p&gt;

</description>
      <category>css</category>
      <category>style</category>
      <category>content</category>
      <category>html</category>
    </item>
  </channel>
</rss>
