DEV Community

Cover image for Let's do this! - Learning In Public

Let's do this! - Learning In Public

zenmnky profile image Justin Hager ใƒป3 min read

Okay, let's do this. Let's learn in public, and learn how to learn in public. This is going to be messy. There will be mistakes and retakes. There will be embarrassment, humility, shared common humanity, and personal and technical growth.

๐Ÿ™ Big thank you to:

  • the great people and great conversations that happen at Virtual Coffee . I'm starting this after an hour long conversation about the fears and benefits of Learning In Public.
  • My Dad - for our regular conversations and for embodying grace, perseverance, and family values

// Note: not an exhaustive list (duh)

๐Ÿค”๐Ÿ’ญ What am I up to?

I'll start out briefly, just so I can lower the resistance to getting this out there and add a nice spin to the momentum that was created in this morning's conversation:

  • ๐Ÿ‘จโ€๐Ÿ’ป I'm currently in the scary position of finishing up a dev bootcamp (2 projects to wrap up by March 11th) and regularly praying for enlightenment of what's the next step I am to take.
  • โ›ช I'm excited to be part of the volunteer dev team for LifeChurch Open Network. I like the organization, the product/service, and I'm super stoked to be part of a professional software development team. I'm still in the 'onboarding' phase I'd say, but there really isn't any onboarding - so I'm taking notes and seeking to understand how everything works.

๐Ÿ‘‰ My notes on the Life Church project I've been assigned to:

LifeChurch Open Network

Admin Client

Part of the Church Online Platform
๐Ÿ“‹ Tech Notes

  • ๐Ÿงช Testing
    • End-to-end: Cypress
    • Integration: Mocha/Chai, Supertest (??)
    • Unit: Jest
  • ๐Ÿ’ป Frontend:

    • Framework: React.js
    • Language: TypeScript
    • Styling: Styled Components
    • State management: Redux & Apollo Client
  • ๐Ÿ“ก๐Ÿ’พ API/Backend:

    • API Structure: GraphQL
    • Backend Language: Ruby
  • ๐Ÿฑ DevOps:

    • Architecture: Containerized Microservices
      • Cloud: Azure
      • Containers: Docker, Kubernetes
    • Version Control: GitBucket

// oh, did I mention I love to take notes? Markdown + emojis && sketch notes with a ballpoint for the win!

๐Ÿ‘‰ My notes on the Thinkful program I'm finishing up:


Software Engineering Immersion Program

๐Ÿ“‹ Tech Notes

  • ๐Ÿงช Testing
    • End-to-end: Cypress
    • Integration: Mocha/Chai, Supertest
    • Unit: Jest
  • ๐Ÿ’ป Frontend:

    • Framework: React.js
    • Language: JS ES6
    • Styling: CSS3
    • State management: Context API & Stateful Class Components
  • ๐Ÿ“ก๐Ÿ’พ API/Backend:

    • API Structure: RESTful
    • ORM: Knex.js
    • DB: PostgresQL
  • ๐Ÿ“ˆ Application Development

    • Process:
      • Web App Design and a taste of Agile
      • Progressive enhancement
    • Considerations:
      • Mobile first, responsive, accessible
  • ๐Ÿฑ DevOps:

    • Architecture: Monolithic
    • Version Control: Git
    • Hosting: Vercel, Heroku

๐Ÿ‘‰ What I'm up to in Linux ๐Ÿง

  • Prepping for LFCA and LFSA exams
  • Currently working through Intro to Linux by the Linux Foundation
    • // which, by the way, is based here in Portland, OR. Who knew?! very cool.
    • VIM!!!
  • Preparing to do a learning project:
    • Setting up Nginx on a RasperryPi, setting it up to use Docker, and using Docker to setup Nextcloud, which I'll configure to use as my synchronization server for Joplin.
    • Am I familiar with any of this? Nope. I'm interested in all of this and want to learn more by figuring out how to do it ๐Ÿ˜

Talk to you later.

Persist Well โ›ฐ๏ธ๐ŸŒŸ


photo credit: Photo by CoWomen on Unsplash

Discussion (2)

Editor guide
nickytonline profile image
Nick Taylor (he/him) • Edited

Congrats on your first post and nice meeting you today Justin!

1st place in Mariokart

zenmnky profile image
Justin Hager Author

Thanks Nick!