Sign In
Get Clay Free →

Suggestions

    Jesse Warden

    Lead Software Engineer

    Jesse Warden is a veteran Software Developer with over 20 years of experience in coding, specializing in front-end and back-end development with a keen interest in AWS deployment.

    Throughout his career, Jesse has explored various avenues in the tech industry, from freelancing to working with startups, running a consulting business, to collaborating with major enterprises like Accenture and Capital One. Currently, he is actively involved in coding at Timmons.

    Jesse's expertise primarily revolves around building UIs, starting from Director and Lingo for desktop and CD-ROMs, transitioning to Flash, ActionScript, Flex, and eventually adapting to JavaScript, Backbone, Angular, React, and Elm. He has also ventured into back-end development using Node.js and has a strong focus on Functional Programming and serverless architecture on AWS.

    Passionate about sharing his knowledge, Jesse frequently speaks at conferences and events worldwide and maintains a blog to document his learning experiences. He also creates educational programming content on his YouTube channel to help beginners and advanced learners in a fun and engaging manner.

    Beyond the tech realm, Jesse's interests span across Bodybuilding, Powerlifting, Parkour, Backpacking, and riding motorcycles.

    Education-wise, Jesse holds a Bachelor's Degree in Organizational Leadership and Management from Reinhardt University, and an Associate's Degree in Multimedia from The Art Institutes.

    Highlights

    Oct 22 · twitter

    It's my long lost brother... COME SELECTAH, WHO GWAN TEST!? #CurryGoatRiceAndPeas #dnb https://t.co/rfys9oJieB

    Sep 28 · twitter

    Working on a preso around "Where is Type-Driven Development?". If you look at all the thought leaders out there, save Mark Seemann of Dependency Injection fame who has a blog post around type-driven dev, and Scott Wlaschin, they espouse all the good things (CICD, TDD, DDD, various long-lasting architecture ideas, etc), but none of them cover types, and only types as a tool for design. I get the sense all think types are just part of the implementation details.

    To those of us from good type-systems (F#, Scala, Haskell, Elm, OCAML, etc) it's confusing and curious. Typically in those languages, the types can lead design earlier, and better in some cases in tests, AND negate the need for some tests. This isn't to say tests aren't needed (more citations on that later), but if you have a good type system, typically types can either lead the design before tests, OR be a fast follow in the Red to Green phase.

    Anyway, times are different now, type systems are great and numerous, and I find it odd it's not talked about more; that and the term seems to be most popular with the book of the same name around the Idris programming language. C#/Java does NOT dominate the industry anymore, and even if they did, their type systems are better too when a lot of these thought leaders we're getting known and these software dev processes were getting popularized.

    It's clear people need examples in languages they use vs. "Here's a great idea from academia, see if you can adopt it", and then "Here's how you can use that as a design tool". I feel like the DDD crew, given their tools of the time, has co-opted the narrative because when they started, bad type systems were what people used, and leveraging classes and structs with methods/functions enforcing "how they are used" used to be the edifice in how those beliefs were (are still) manifested. Devs like Scott Wlaschin have shown you can leverage the good ideas from DDD in type-driven development.

    Given how smart many of these thought leaders are, and how wide their audiences are, it's disappointing this isn't even acknowledged. I've watched a few of their hands-on tutorials where they actually write code, and it seems to, like I said, just flow as an "implementation detail". Heck with that noise, devs need to know they have something OTHER than TDD/BDD, Event Driven, Layered Architectures, OOP, FP, and Design Patterns as the only design tools that exist. Awareness is sometimes key to helping.

    Jesse Warden
    Add to my network

    Location

    Mechanicsville, Virginia, United States