Code Quality Challenge - Week 5

Senior Full-Stack Developer with over 20 years of experience building web applications for startups, government, and higher education.
Search for a command to run...

Senior Full-Stack Developer with over 20 years of experience building web applications for startups, government, and higher education.
No comments yet. Be the first to comment.
Journal of my [Code quality challenge](https://justinramel.com/im-taking-the-code-quality-challenge)
Week 1 journal of the Code Quality Challenge. Day 1 - Clean up your README Free swag! Ben Orenstein is very kindly offering free stuff for all participants: For a little extra motivation, I am offering a free swag item from Tuple to all participants...
Writing this up so I have somewhere to quickly grab basic Jest setup. This information is copied from the Jest Documentation Site compressed into just the parts I'm interested in. Create folders mkdir -p <project>/src cd <project> Install and init n...

In this blog post, we'll explore the process of setting up and configuring a Postgres database using Docker and seeding it with test data. This approach can be used for a variety of apps and can be easily adapted for your own needs. We'll cover all t...

Continuing from last time, we will explore the concepts behind Create and Update functionality and provide a step-by-step guide on how to implement it in your SvelteKit application. Let's get started! Server & Client Code In SvelteKit, the server-sid...

Introduction In this post, I will explore how to create a REST API using Spring Boot and Kotlin. We will dive into the fundamentals of Spring Boot and Kotlin, explain how to set up the project, and guide you through the process of building the API st...

Introduction Welcome to the latest post in my series of Koan Battles using Kotlin and TypeScript. In this series, we'll complete a Koan in both languages and then discuss the differences between the two solutions. My goal is to help you gain a deeper...

I thought the challenge ended last week but it seems we're getting a couple of bonus days, lets get to it.
Today’s task is all about improving readability.
Investigate your larger methods, especially ones longer than 10 lines. Do you see any groups of functionality that could be extracted out into smaller, more clearly named, methods?
Always a useful refactoring. I spent 20 minutes splitting up a massive 65 line method into smaller clearly named methods.
You made it! Well done, you.
For this, our final task, please reflect upon your experience. Consider flipping back through the older threads to refresh your memory of the exercises.
Let's have a look back through my posts and find out which challenges I've been keeping up...
Keeping the README up to date is really valuable. Useful for the future me when trying to remember how to deploy the app. Invaluable for the rest of the team when I'm not around.
I was spending a lot of time digging through masses of branches when switching between feature branches. I hadn't realised how painful this was until I cleared them out.
This saves me lots of time every day, great win.
Spent some extra time on this challenge and have since deployed to production via the command line. I also updated the README with instructions on how to do it, see Day 1 😀
This one has been the most surprising, I've tried this before but not kept it up. The slow burn method has worked and I'm adding new snippets daily.
Thanks Ben Orenstein for a great challenge and the Pear programming T-shirt!

Any developer (and codebase) will benefit from this challenge.
What are you waiting for? Get signed up for the next challenge!