<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
      <title></title>
      <link>/</link>
      <description></description>
      <generator>Zola</generator>
      <language>en</language>
      <atom:link href="/rss.xml" rel="self" type="application/rss+xml"/>
      <lastBuildDate>Wed, 15 Oct 2025 00:00:00 +0000</lastBuildDate>
      <item>
          <title>Initial Post</title>
          <pubDate>Wed, 15 Oct 2025 00:00:00 +0000</pubDate>
          <author>Unknown</author>
          <link>/blog/initial-post/</link>
          <guid>/blog/initial-post/</guid>
          <description xml:base="/blog/initial-post/">&lt;p&gt;I honestly don&#39;t know what to write here but I do need a starter blog post so here it is.&lt;/p&gt;
&lt;h1 id=&quot;welcome-to-my-blog&quot;&gt;Welcome to my blog&lt;/h1&gt;
&lt;p&gt;This a blog / portfolio / general indie website based on the coolish things I do, as well as the not so cool things I do. Whatever the case, this is that site.&lt;/p&gt;
&lt;p&gt;Some important things to know about me, I&#39;m a trans woman so generally I&#39;m socially inept but I do try and help people and get enjoyment from doing so.
I&#39;m a support main because I like making other peoples jobs easier, be that in games or in a workplace.
I&#39;m a pretty good Gamemaster and I&#39;m ADHD as evidenced by this post.&lt;/p&gt;
&lt;p&gt;Finally I have &lt;strong&gt;OPINIONS&lt;/strong&gt;, So if I decide that the internet needs to know those opinions they will end up in a blog post here.&lt;/p&gt;
&lt;p&gt;All that to say, Thanks for viewing the site and enduring my rambling blog entries!&lt;/p&gt;
</description>
      </item>
      <item>
          <title>Terminal Portfolio Site</title>
          <pubDate>Sat, 15 Mar 2025 00:00:00 +0000</pubDate>
          <author>Unknown</author>
          <link>/projects/portfolio-terminal-site/</link>
          <guid>/projects/portfolio-terminal-site/</guid>
          <description xml:base="/projects/portfolio-terminal-site/">&lt;h1 id=&quot;terminal-portfolio-site&quot;&gt;Terminal Portfolio Site&lt;/h1&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://git.b1rdh0use.com/cr0w/birdhouse.git&quot;&gt;Repository&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This is the site you are likely reading this off now. What do you thonk?&lt;/p&gt;
&lt;h2 id=&quot;stack&quot;&gt;Stack&lt;/h2&gt;
&lt;p&gt;Portfolio and blog built with jQuery Terminal and Zola for displaying blog contents using an interactive terminal interface&lt;/p&gt;
&lt;h3 id=&quot;technology&quot;&gt;Technology&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Zola (Static Site Generator)&lt;/li&gt;
&lt;li&gt;Tera (Template Engine)&lt;/li&gt;
&lt;li&gt;Vite (Asset Bundler)&lt;/li&gt;
&lt;li&gt;Bun (Package Manager &amp;amp; Runtime)&lt;/li&gt;
&lt;li&gt;jQuery Terminal (Terminal emulator interface)&lt;/li&gt;
&lt;li&gt;WebTUI CSS (TUI-styled component library)&lt;/li&gt;
&lt;li&gt;Sass/SCSS (Stylesheet preprocessing)&lt;/li&gt;
&lt;li&gt;Peggy (Markdown parsing grammar)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;key-features&quot;&gt;Key Features&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Interactive terminal shell with &lt;code&gt;ls&lt;/code&gt;, &lt;code&gt;cd&lt;/code&gt;, &lt;code&gt;cat&lt;/code&gt;, &lt;code&gt;pwd&lt;/code&gt;, &lt;code&gt;help&lt;/code&gt;, &lt;code&gt;clear&lt;/code&gt;, &lt;code&gt;tree&lt;/code&gt;, &lt;code&gt;find&lt;/code&gt; commands&lt;/li&gt;
&lt;li&gt;Tab completion and command history&lt;/li&gt;
&lt;li&gt;Dual navigation system (tree sidebar + terminal interface)&lt;/li&gt;
&lt;li&gt;Virtual filesystem synchronized with browser history&lt;/li&gt;
&lt;li&gt;Responsive mobile navigation with collapsible drawer&lt;/li&gt;
&lt;li&gt;Progressive enhancement (content works without JavaScript)&lt;/li&gt;
&lt;li&gt;Custom Markdown processing with Peggy grammar&lt;/li&gt;
&lt;li&gt;Syntax highlighting for code blocks&lt;/li&gt;
&lt;li&gt;Content organized by month for blog posts&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;learning-focus&quot;&gt;Learning Focus&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Piecing together differing technologies&lt;/li&gt;
&lt;li&gt;Learning WCAG 2.2 accessibility guidelines&lt;/li&gt;
&lt;li&gt;Working with AI coding tools&lt;/li&gt;
&lt;li&gt;Using conventional commits&lt;/li&gt;
&lt;li&gt;ADHD Management&lt;/li&gt;
&lt;li&gt;Making deliberate technology choices&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;ramblings&quot;&gt;Ramblings&lt;/h2&gt;
&lt;p&gt;This was an interesting project. I hadn&#39;t worked on code stuff for a while after leaving my tech job and this project was just going to be a simple portfolio. What ended up pushing me to make something more complex was the idea of the indie web. I wanted a site that shouted me and I wanted it to be interactive and cool. I decided that a terminal in the site would be a pretty cool portfolio and reading experience.&lt;/p&gt;
&lt;p&gt;One of the challenges I faced while making the site was my own ADHD. I don&#39;t have a lot of free time and I find myself struggling to do anything productive after I get home from work. So, I ended up utilizing my mornings and breaks to work on this site. An interesting side effect of having so little time to work on the site was that I gave in and started using AI coding agents to accelerate my development. As someone with ADHD and also despises AI slop it&#39;s mixed feelings when it comes to using them for development. On one hand I know I&#39;m not building each function or section of code and thinking about how it specifically gets implemented at the beginning. On the other hand the AI often does the thing that is hard for me to do with ADHD, breaking down tasks.&lt;/p&gt;
&lt;p&gt;In the past I&#39;ve had problems with context switching and going from development to debugging when whatever I wrote broke down. Now, I&#39;m usually in debugging and review mode and it&#39;s easier to stay in that headspace. Having the AI grease the wheels when I start working makes it easier for me to stay working for much longer without losing focus. The last thing I&#39;ll say on this is that while I despise AI for most of the uses that corporations want to stuff down our throats, Coding is one of the few areas I think these models are truly useful.&lt;/p&gt;
</description>
      </item>
      <item>
          <title>Angular Golf Scorecard</title>
          <pubDate>Mon, 27 Jan 2025 00:00:00 +0000</pubDate>
          <author>Unknown</author>
          <link>/projects/angular-golf-scorecard/</link>
          <guid>/projects/angular-golf-scorecard/</guid>
          <description xml:base="/projects/angular-golf-scorecard/">&lt;h1 id=&quot;angular-golf-scorecard&quot;&gt;Angular Golf Scorecard&lt;/h1&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://git.b1rdh0use.com/cr0w/angular-golf-scorecard.git&quot;&gt;Repository&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This project was a capstone, we were to take the basic golf project and re-create it using Angular and with all the concepts that have been learned previously.&lt;/p&gt;
&lt;h2 id=&quot;stack&quot;&gt;Stack&lt;/h2&gt;
&lt;p&gt;Full production-ready Angular application for tracking golf scores with Firebase backend and external API integration.&lt;/p&gt;
&lt;h3 id=&quot;technology&quot;&gt;Technology&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Angular 7 with TypeScript&lt;/li&gt;
&lt;li&gt;Angular Material for UI components&lt;/li&gt;
&lt;li&gt;Firebase (authentication + backend)&lt;/li&gt;
&lt;li&gt;Angular Bootstrap&lt;/li&gt;
&lt;li&gt;RxJS for reactive programming&lt;/li&gt;
&lt;li&gt;Karma + Jasmine for testing&lt;/li&gt;
&lt;li&gt;Protractor for e2e tests&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;key-features&quot;&gt;Key Features&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Unit test suite&lt;/li&gt;
&lt;li&gt;All functionality from &lt;a href=&quot;/projects/js-golf-project/&quot;&gt;js-golfProject&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Reactive automatic score calculation&lt;/li&gt;
&lt;li&gt;Database use and access&lt;/li&gt;
&lt;li&gt;Production authentication&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;learning-focus&quot;&gt;Learning Focus&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Refactoring projects&lt;/li&gt;
&lt;li&gt;Test Driven Development&lt;/li&gt;
&lt;li&gt;Angular Component Lifecycle&lt;/li&gt;
&lt;li&gt;Authentication&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;ramblings&quot;&gt;Ramblings&lt;/h2&gt;
&lt;p&gt;I did not enjoy this project mostly because I had to use Angular and it was going through a similar development process as react at the time I was working on it as well. A lot of the conventional patterns for working with authentication and firebase were no longer up to date and I also had to trial and error my way into getting it working. What I did enjoy was some of the conventions of angular itself in using ng-container and how you could retrieve data just by wrapping the variable in double curly braces. This helped me in my next job as they were using angularJS and .NET and the evaluations within the braces were consistent between the versions.&lt;/p&gt;
&lt;p&gt;After doing projects with these frameworks I found that I do not like how bloated they are in bundle size and development overhead. They do make writing code in a group easier but the problem I&#39;ve found is that creating these projects as a single page application slows the user&#39;s browser down even creating small apps such as these. If you aren&#39;t creating a heavy number crunching application with a massive dashboard it&#39;s pretty overkill. I make an exception for React Native as being able to hook directly into operating system functionality can be great for specific projects.
On second reflection no matter what the language or framework it all depends on the project requirements.&lt;/p&gt;
&lt;p&gt;Next project: &lt;a href=&quot;/projects/portfolio-terminal-site/&quot;&gt;Portfolio Terminal Site&lt;/a&gt;&lt;/p&gt;
</description>
      </item>
      <item>
          <title>JavaScript Fortune Teller</title>
          <pubDate>Mon, 27 Jan 2025 00:00:00 +0000</pubDate>
          <author>Unknown</author>
          <link>/projects/js-fortune-teller/</link>
          <guid>/projects/js-fortune-teller/</guid>
          <description xml:base="/projects/js-fortune-teller/">&lt;h1 id=&quot;javascript-fortune-teller&quot;&gt;JavaScript Fortune Teller&lt;/h1&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://git.b1rdh0use.com/cr0w/js-fortuneTeller.git&quot;&gt;Repository&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This project was a fun holiday exercise mainly to keep working with JavaScript and play with some holiday themed assets in creating a page like audio files and an animated GIF.&lt;/p&gt;
&lt;h2 id=&quot;stack&quot;&gt;Stack&lt;/h2&gt;
&lt;p&gt;Christmas-themed fortune generator with sound effects, animations, and &quot;Naughty or Nice&quot; holiday humor using JavaScript.&lt;/p&gt;
&lt;h3 id=&quot;technology&quot;&gt;Technology&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Vanilla JavaScript&lt;/li&gt;
&lt;li&gt;Bootstrap 4&lt;/li&gt;
&lt;li&gt;FontAwesome&lt;/li&gt;
&lt;li&gt;HTML5 Audio API&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;key-features&quot;&gt;Key Features&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Random fortune selection&lt;/li&gt;
&lt;li&gt;Sound plays based on positive or negative fortune&lt;/li&gt;
&lt;li&gt;GIF to keep users entertained&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;learning-focus&quot;&gt;Learning Focus&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Using more JavaScript built-in utilities like Math&lt;/li&gt;
&lt;li&gt;Constructing fortune strings from templates&lt;/li&gt;
&lt;li&gt;Managing audio playback&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;ramblings&quot;&gt;Ramblings&lt;/h2&gt;
&lt;p&gt;While I think this project was my first introduction to the Math built-ins and creating pseudo random number generation, I more remember this project because I got to write a few tongue in cheek christmas fortunes. For example: &quot;Your grandmother will be ran over by a reindeer, the broken hip leads to severe medical debt&quot; and &quot;A loved one will take you christmas shopping for 5 hours, and will not buy anything&quot;&lt;/p&gt;
&lt;p&gt;All in all, this was a goofy little project that wasn&#39;t too complicated to allow us to focus on the holidays.&lt;/p&gt;
&lt;p&gt;Next project: &lt;a href=&quot;/projects/js-todo-app/&quot;&gt;JavaScript Todo Application&lt;/a&gt;&lt;/p&gt;
</description>
      </item>
      <item>
          <title>JavaScript Todo Application</title>
          <pubDate>Mon, 27 Jan 2025 00:00:00 +0000</pubDate>
          <author>Unknown</author>
          <link>/projects/js-todo-app/</link>
          <guid>/projects/js-todo-app/</guid>
          <description xml:base="/projects/js-todo-app/">&lt;h1 id=&quot;javascript-todo-application&quot;&gt;JavaScript Todo Application&lt;/h1&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://git.b1rdh0use.com/cr0w/js-TodoApp.git&quot;&gt;Repository&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This project was my first toe dipped into web application development. It&#39;s a todo list with all features required for a minimum viable product.&lt;/p&gt;
&lt;h2 id=&quot;stack&quot;&gt;Stack&lt;/h2&gt;
&lt;p&gt;Interactive todo list manager supporting multiple named lists with drag-and-drop functionality using JavaScript and JQuery for UI animation.&lt;/p&gt;
&lt;h3 id=&quot;technology&quot;&gt;Technology&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Vanilla JavaScript with jQuery&lt;/li&gt;
&lt;li&gt;Bootstrap 4 for styling&lt;/li&gt;
&lt;li&gt;FontAwesome icons&lt;/li&gt;
&lt;li&gt;Google Fonts (Roboto)&lt;/li&gt;
&lt;li&gt;jQuery UI for animations&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;key-features&quot;&gt;Key Features&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Create, Update, Read, and Delete functionality&lt;/li&gt;
&lt;li&gt;FontAwesome Icons for intuitive usage&lt;/li&gt;
&lt;li&gt;Funky colors for fun&lt;/li&gt;
&lt;li&gt;Drag and Drop powered by JQuery&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;learning-focus&quot;&gt;Learning Focus&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;CRUD operations&lt;/li&gt;
&lt;li&gt;Product requirements&lt;/li&gt;
&lt;li&gt;Wireframing&lt;/li&gt;
&lt;li&gt;Waterfall development&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;ramblings&quot;&gt;Ramblings&lt;/h2&gt;
&lt;p&gt;This project was focused on taking a set of product requirements all the way through the development cycle. I was given the task of creating a todo application where I could create, check off and delete items. I was asked to wireframe the application before writing it so I knew how it should look. Currently nothing is saved anywhere and all the data remains in the DOM where it will be lost on refresh. I learned about using local storage later so I didn&#39;t add it at the time although if I were to rewrite the project I would consider it an necessity.&lt;/p&gt;
&lt;p&gt;Next project: &lt;a href=&quot;/projects/react-e-commerce/&quot;&gt;React E-Commerce Site&lt;/a&gt;&lt;/p&gt;
</description>
      </item>
      <item>
          <title>HTML5 Web Workers Demo</title>
          <pubDate>Mon, 27 Jan 2025 00:00:00 +0000</pubDate>
          <author>Unknown</author>
          <link>/projects/js-webworkers/</link>
          <guid>/projects/js-webworkers/</guid>
          <description xml:base="/projects/js-webworkers/">&lt;h1 id=&quot;html5-web-workers-demo&quot;&gt;HTML5 Web Workers Demo&lt;/h1&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://git.b1rdh0use.com/cr0w/js-webworkers.git&quot;&gt;Repository&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This project is a simple lab about learning to create and interact with Web Workers&lt;/p&gt;
&lt;h2 id=&quot;stack&quot;&gt;Stack&lt;/h2&gt;
&lt;p&gt;Educational demonstration of HTML5 Web Workers API showing multi-threading capabilities in JavaScript with browser fallback handling.&lt;/p&gt;
&lt;h3 id=&quot;technology&quot;&gt;Technology&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Vanilla JavaScript&lt;/li&gt;
&lt;li&gt;HTML5 Web Workers API&lt;/li&gt;
&lt;li&gt;Bootstrap 4&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;key-features&quot;&gt;Key Features&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Timer using a simple dedicated worker thread&lt;/li&gt;
&lt;li&gt;Button that starts and stops worker thread&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;learning-focus&quot;&gt;Learning Focus&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;What a Web Worker is&lt;/li&gt;
&lt;li&gt;Moving synchronous operations to background thrads&lt;/li&gt;
&lt;li&gt;Communicating with workers from main script&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;ramblings&quot;&gt;Ramblings&lt;/h2&gt;
&lt;p&gt;This project is deceptively simple. On the surface and in actuality it is a timer, but the important thing is that I learned about creating background processes and services for web applications. Web workers are good for heavy number crunching if you can spin up a few to do chunks of the calculation. They&#39;re good for allowing apps to function without network access if you setup a service worker, and they&#39;re good for code reuse as multiple scripts can use a shared worker.&lt;/p&gt;
&lt;p&gt;Next project: &lt;a href=&quot;/projects/js-fortune-teller/&quot;&gt;JavaScript Fortune Teller&lt;/a&gt;&lt;/p&gt;
</description>
      </item>
      <item>
          <title>React E-Commerce Site</title>
          <pubDate>Mon, 27 Jan 2025 00:00:00 +0000</pubDate>
          <author>Unknown</author>
          <link>/projects/react-e-commerce/</link>
          <guid>/projects/react-e-commerce/</guid>
          <description xml:base="/projects/react-e-commerce/">&lt;h1 id=&quot;react-e-commerce-site&quot;&gt;React E-Commerce Site&lt;/h1&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://git.b1rdh0use.com/cr0w/react-e-commerse.git&quot;&gt;Repository&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This project was a complete e-commerse site for selling comic books using a full JavaScript framework&lt;/p&gt;
&lt;h2 id=&quot;stack&quot;&gt;Stack&lt;/h2&gt;
&lt;p&gt;Full-featured e-commerce site with shopping cart, product catalog, and checkout flow built with React and styled components.&lt;/p&gt;
&lt;h3 id=&quot;technology&quot;&gt;Technology&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;React 16.8.6 (Hooks era but uses class components)&lt;/li&gt;
&lt;li&gt;React Router for navigation&lt;/li&gt;
&lt;li&gt;Bootstrap-styled components&lt;/li&gt;
&lt;li&gt;Styled Components&lt;/li&gt;
&lt;li&gt;FontAwesome icons&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;key-features&quot;&gt;Key Features&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Shopping cart using state management&lt;/li&gt;
&lt;li&gt;Product catalog with lazy loading of products&lt;/li&gt;
&lt;li&gt;Automatic cart totals&lt;/li&gt;
&lt;li&gt;Details pages for each product&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;learning-focus&quot;&gt;Learning Focus&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;State management with react redux&lt;/li&gt;
&lt;li&gt;React framework&lt;/li&gt;
&lt;li&gt;TypeScript interfaces for data&lt;/li&gt;
&lt;li&gt;SPA routing techniques&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;ramblings&quot;&gt;Ramblings&lt;/h2&gt;
&lt;p&gt;When I was working on this project it was a bag of mixed feelings. On one hand there were a lot of harnesses and patterns to follow to help write good functional code in a single page application. On the other it was a lot to take in at once and working with something so heavy meant I was trying to connect the dots as to how each piece fit together.
It was valuable to learn how a router worked and how Typescript could help organize JavaScript in a way that warned you against mixing types, but I was fighting the fact that the framework was changing as I was working with it. A lot of the tutorials were not for the version of react I was using as I was on the bleeding edge.&lt;/p&gt;
&lt;p&gt;Despite fighting with the framework itself, A good thing I learned while working on this project was that I learned how to dive into errors with greater fervor as that was the only way I managed to get this functional at the time.&lt;/p&gt;
&lt;p&gt;Next project: &lt;a href=&quot;/projects/angular-golf-scorecard/&quot;&gt;Angular Golf Scorecard&lt;/a&gt;&lt;/p&gt;
</description>
      </item>
      <item>
          <title>Old TechPaws Blog Site</title>
          <pubDate>Sun, 26 Jan 2025 00:00:00 +0000</pubDate>
          <author>Unknown</author>
          <link>/projects/old-techpaws-blog/</link>
          <guid>/projects/old-techpaws-blog/</guid>
          <description xml:base="/projects/old-techpaws-blog/">&lt;h1 id=&quot;old-techpaws-blog-site&quot;&gt;Old TechPaws Blog Site&lt;/h1&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://git.b1rdh0use.com/cr0w/old-blog.git&quot;&gt;Repository&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This project was a landing page and blog page for a generic tech company. I ended up using photos of a hardware monitor gauge built with the same technology as a car odometer. I&#39;m not cool enough to have built that but I did take the picture.&lt;/p&gt;
&lt;h2 id=&quot;stack&quot;&gt;Stack&lt;/h2&gt;
&lt;p&gt;Landing and blog page using static HTML. SCSS is used for styling and external CDN requests are used for fonts and FontAwesome icons. Each page is separated out into its own SCSS and HTML files and I used a funny little ispum generator set to Microsoft purist mode for the text.&lt;/p&gt;
&lt;h3 id=&quot;technology&quot;&gt;Technology&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Static HTML site&lt;/li&gt;
&lt;li&gt;SCSS for styling (compiled to CSS)&lt;/li&gt;
&lt;li&gt;FontAwesome icons&lt;/li&gt;
&lt;li&gt;Google Fonts (Roboto)&lt;/li&gt;
&lt;li&gt;Simple file structure&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;key-features&quot;&gt;Key Features&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Non semantic HTML structure using divs and classes&lt;/li&gt;
&lt;li&gt;More advanced usage of styling such as the slanted sidebar&lt;/li&gt;
&lt;li&gt;CDN usage&lt;/li&gt;
&lt;li&gt;Images&lt;/li&gt;
&lt;li&gt;Links between pages&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;learning-focus&quot;&gt;Learning Focus&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Learning about CDNs&lt;/li&gt;
&lt;li&gt;Using a compiler for the first time&lt;/li&gt;
&lt;li&gt;Practicing the habit of separating files&lt;/li&gt;
&lt;li&gt;Working with a partner&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;ramblings&quot;&gt;Ramblings&lt;/h2&gt;
&lt;p&gt;This project was a few different things. first it was a bit more complex due to having to compile SCSS in exchange for nicer variables, more importantly though it was a team project. We were using a shared repository and we had to work with each other and learn git operations. We also went over how to get fonts and icons from external sources and making sites look a bit nicer.
It also gave me permission to look for cool internet resources that can help me create a site. I spent project time on this site finding a lorem ipsum generator, it allowed me to make some funny ipsum text that feels like you&#39;re almost reading something coherent until you realize it&#39;s not. It&#39;s important to sometimes explore the web and find facinating resources to keep yourself interested and maybe learn to explore a new technology or just explore something another person made.&lt;/p&gt;
&lt;p&gt;Next project: &lt;a href=&quot;/projects/html-burgers/&quot;&gt;HTML &quot;Burgers&quot; Restaurant Site&lt;/a&gt;&lt;/p&gt;
</description>
      </item>
      <item>
          <title>JavaScript Golf Project</title>
          <pubDate>Thu, 23 Jan 2025 00:00:00 +0000</pubDate>
          <author>Unknown</author>
          <link>/projects/js-golf-project/</link>
          <guid>/projects/js-golf-project/</guid>
          <description xml:base="/projects/js-golf-project/">&lt;h1 id=&quot;javascript-golf-project&quot;&gt;JavaScript Golf Project&lt;/h1&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://git.b1rdh0use.com/cr0w/js-golfProject.git&quot;&gt;Repository&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This project was a golf scorecard using an external api to get information about a specific course and calculate the score based on par, yardage, and handicap.&lt;/p&gt;
&lt;h2 id=&quot;stack&quot;&gt;Stack&lt;/h2&gt;
&lt;p&gt;Golf scoring implementation using vanilla JavaScript and XMLHttpRequest, tracking multiple players and course data.&lt;/p&gt;
&lt;h3 id=&quot;technology&quot;&gt;Technology&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Vanilla JavaScript (ES5/ES6)&lt;/li&gt;
&lt;li&gt;XMLHttpRequest (pre-fetch era)&lt;/li&gt;
&lt;li&gt;Custom CSS (SCSS sources included)&lt;/li&gt;
&lt;li&gt;jQuery for DOM manipulation&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;key-features&quot;&gt;Key Features&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Switch statement&lt;/li&gt;
&lt;li&gt;Self Invoked functions&lt;/li&gt;
&lt;li&gt;Multi player tracking&lt;/li&gt;
&lt;li&gt;Score calculation&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;learning-focus&quot;&gt;Learning Focus&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Using an external api&lt;/li&gt;
&lt;li&gt;Manipulating data with JavaScript&lt;/li&gt;
&lt;li&gt;Manually creating HTTP requests without a library&lt;/li&gt;
&lt;li&gt;Modifying the DOM from JavaScript&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;ramblings&quot;&gt;Ramblings&lt;/h2&gt;
&lt;p&gt;Looking back at this particular project I am honestly horrified at the JavaScript patterns and structure past me wrote. I can already think of ways to make the JavaScript smaller and more efficient. For an example I&#39;ve got like eight hardcoded arrays filled with zeros up at the top to control the data for each player. Arrays can be two dimensional past me! I also didn&#39;t really understand the concept of a map yet. Eight hardcoded arrays can become a single line with both of these concepts.&lt;/p&gt;
&lt;pre&gt;&lt;code data-lang=&quot;js&quot;&gt;let players = Array(8).fill().map(() =&amp;gt; Array(18 /* or num holes */).fill(0));
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Once that is done the switch statement is no longer really needed and can instead be represented as such&lt;/p&gt;
&lt;pre&gt;&lt;code data-lang=&quot;js&quot;&gt;players[player-1][hole-1] = scoreNumber
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;There&#39;s also some other iteration and potential helper functions that can be written but I&#39;m not about to entirely refactor a project that no longer even has an api to connect to.&lt;/p&gt;
&lt;p&gt;Next project: &lt;a href=&quot;/projects/js-webworkers/&quot;&gt;HTML5 Web Workers Demo&lt;/a&gt;&lt;/p&gt;
</description>
      </item>
      <item>
          <title>HTML Burgers Restaurant Site</title>
          <pubDate>Tue, 21 Jan 2025 00:00:00 +0000</pubDate>
          <author>Unknown</author>
          <link>/projects/html-burgers/</link>
          <guid>/projects/html-burgers/</guid>
          <description xml:base="/projects/html-burgers/">&lt;h1 id=&quot;html-burgers-restaurant-site&quot;&gt;HTML &quot;Burgers&quot; Restaurant Site&lt;/h1&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://git.b1rdh0use.com/cr0w/html-burgers.git&quot;&gt;Repository&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This project was an assignment to create a basic website for a restaurant. The content of the site was provided such as the menu and all the marketing blurbs. All the design was my job. I decided that it would be cool to color the elements to be a burger in and of itself.&lt;/p&gt;
&lt;h2 id=&quot;stack&quot;&gt;Stack&lt;/h2&gt;
&lt;p&gt;Static multi-page restaurant website demonstrating HTML structure, CSS styling, and basic JavaScript interactivity.&lt;/p&gt;
&lt;h3 id=&quot;technology&quot;&gt;Technology&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Pure HTML5/JavaScript&lt;/li&gt;
&lt;li&gt;Bootstrap for page layout and buttons&lt;/li&gt;
&lt;li&gt;Custom images included&lt;/li&gt;
&lt;li&gt;Google maps API&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;key-features&quot;&gt;Key Features&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Iframe usage for vibdeo player&lt;/li&gt;
&lt;li&gt;Google maps API for displaying locations&lt;/li&gt;
&lt;li&gt;Site photos taken personally by myself&lt;/li&gt;
&lt;li&gt;Interactive HTML form&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;learning-focus&quot;&gt;Learning Focus&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Creating sites for clients using their materials&lt;/li&gt;
&lt;li&gt;Learning about HTML5 Features such as Iframes and vibdeo players&lt;/li&gt;
&lt;li&gt;Exploring CSS frameworks&lt;/li&gt;
&lt;li&gt;Dipping a toe in JavaScript by implementing a form&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;ramblings&quot;&gt;Ramblings&lt;/h2&gt;
&lt;p&gt;This project ended up being pretty fun, The assignment was to create a website for this fake Rockey burgers company. It needed a Menu and locations which let me play with the google maps Iframe. I took the hero picture myself of the burgers that the cafeteria of the college made. They were culinary students so the burger looked absolutely delicious. I did get B-roll of the chef cooking the burger for the video portion but I didn&#39;t have the time to edit it before the project was due.&lt;/p&gt;
&lt;p&gt;Next project: &lt;a href=&quot;/projects/js-golf-project/&quot;&gt;JavaScript Golf Project&lt;/a&gt;&lt;/p&gt;
</description>
      </item>
      <item>
          <title>HTML Lab</title>
          <pubDate>Mon, 20 Jan 2025 00:00:00 +0000</pubDate>
          <author>Unknown</author>
          <link>/projects/html-lab/</link>
          <guid>/projects/html-lab/</guid>
          <description xml:base="/projects/html-lab/">&lt;h1 id=&quot;html-lab&quot;&gt;HTML Lab&lt;/h1&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://git.b1rdh0use.com/cr0w/lab-3.git&quot;&gt;Repository&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This was a project very simple in scope but it&#39;s the start of my professional journey, and it&#39;s the start of this retrospective walk I&#39;m taking through my old code.&lt;/p&gt;
&lt;h2 id=&quot;stack&quot;&gt;Stack&lt;/h2&gt;
&lt;p&gt;Didn&#39;t even separate the css into it&#39;s own file. This is a raw single page of HTML.&lt;/p&gt;
&lt;h3 id=&quot;technology&quot;&gt;Technology&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;HTML4 and inline CSS&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;key-features&quot;&gt;Key Features&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Semantic HTML structure using container elements&lt;/li&gt;
&lt;li&gt;Inline CSS styling&lt;/li&gt;
&lt;li&gt;Lorem ipsum content to demonstrate hierarchy&lt;/li&gt;
&lt;li&gt;Clean document structure without many nested div elements&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;learning-focus&quot;&gt;Learning Focus&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Understand HTML elements vs. generic containers&lt;/li&gt;
&lt;li&gt;Learning document structure&lt;/li&gt;
&lt;li&gt;Practicing separation of concerns&lt;/li&gt;
&lt;li&gt;Establishing habits around readable and maintainable HTML markup&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;ramblings&quot;&gt;Ramblings&lt;/h2&gt;
&lt;p&gt;Because there&#39;s not a whole lot to talk about with the code itself I&#39;ll take this opportunity to talk about the emotional wall needed to hurdle for me to even dein to look at these old projects.
As a chronic perfectionist it&#39;s pretty hard to go back to the things i&#39;m not entirely proud of by myself. Ironically that&#39;s exactly how to fight off impostor syndrome. As I look through my old sus code it helps me understand how far i&#39;ve come. This page is literally a bunch of lorem ipsum text and HTML tags. I could write this in a moment now but it was important in my learning process as this project is what I go back to mentally when I think about how base HTML should look. Not a div soup, but using semantic tags as well as proper hierarchy.&lt;/p&gt;
&lt;p&gt;Next project: &lt;a href=&quot;/projects/old-techpaws-blog/&quot;&gt;Old TechPaws Blog Site&lt;/a&gt;&lt;/p&gt;
</description>
      </item>
    </channel>
</rss>
