Brendan Bondurant

    Tag: coding

    • New website coming

      —

      by

      brendanbondurant
      in

      After receiving feedback from a recruiter, I updated my LinkedIn and personal website, transitioning it from a musician site to a blog/portfolio. I’m learning C#/.NET & Blazor through this project and improving my Figma skills. I aim to launch the new site next Friday, featuring Bootstrap and JavaScript elements.

    • Procs, lambdas, and performance

      —

      by

      brendanbondurant
      in

      The author explores the performance of blocks, procs, and lambdas in Ruby through benchmarking. Initial tests showed blocks to be slower due to method call overhead. After refining the approach, benchmarks indicated that while blocks improved, procs and lambdas remained consistently faster, highlighting the importance of method usage in performance.

    • 99 bottles – go and ruby

      —

      by

      brendanbondurant
      in ,

      For whatever reason, I thought of a practice problem that we did at Turing today of writing something that will print the song “99 Bottles of Beer”. I think it was a reference someone made to redoing flashcards? I don’t know, it’s not important. Anyway, I went looking for it on my computer because I…

    • Selenium in Rails

      —

      by

      brendanbondurant
      in

      In this content, the author shares their experience integrating automated testing using Selenium in a Rails application. They describe setting up a new Rails project, configuring necessary gems, and creating a contact form with JavaScript functionality. Two tests are illustrated: one checks successful message submission, and the other validates email format.

    • C# Testing set up

      —

      by

      brendanbondurant
      in

      I have spent a ton of time doing testing for the last several weeks, so I get to teach my friends in a C# study group some basic testing in C# tomorrow. It’s been a minute since I’ve done this (February, maybe?). So I wanted to get the process down somewhere in case I go…

    • Two Sum – Python

      —

      by

      brendanbondurant
      in

      I’ve been reviewing technical interview practice over the last few weeks, and thought it might be a good idea to consolidate my notes and think about how I would teach it. This always worked very well for music, and seems to work for writing code too. I’m going to go over the Two Sum problem…

    • Dynamic vs Static

      —

      by

      brendanbondurant
      in ,

      The author contrasts C# and Ruby, highlighting C# as a static, compiled language and Ruby as dynamic and interpreted. C# requires variable types to be declared at compile time, catching errors early, while Ruby allows runtime type changes, leading to potential runtime errors. Each language suits different needs: Ruby for speed in small tasks, C#…

    • Method/Function in Ruby and C#

      —

      by

      brendanbondurant
      in

      The author compares method implementation between Ruby and C#. They demonstrate creating a simple addition method and checking for odd numbers in both languages. Ruby’s syntax is more concise with built-in methods, while C# requires explicit logic for operations. The author appreciates C#’s detailed visibility in code structure.

    • C# and Ruby

      —

      by

      brendanbondurant
      in , ,

      I’m thinking that the next few posts are going to focus on the similarities between C# and Ruby, as I work through my notes from being onboarded into a project using C# and .NET. One of the main differences is that C# is a ‘statically typed’ language. It requires explicit declarations, and everything is checked…

    • What’s next?

      —

      by

      brendanbondurant
      in

      The author contemplates the future of their content accumulated over 15 years, deciding to maintain a musician website while creating a new platform. With the start of mod3 at Turing approaching, they plan to share blog posts reflecting their learning experiences, primarily serving as instructions for their future self.