DEV Community

Jeremy Gibson
Jeremy Gibson

Posted on • Edited on

1

Refactoring RATOM: Day 1

Where to start?

Whelp, as it often is... the best laid plans.

I thought I would spend the day spinning up the system, so I could refresh myself as to the site structure from a UI/UX perspective, but instead I got caught up in getting testing and CI to work.

The moral of this story...

Tech Debt Is Everywhere

Jade-truffle the cookiecutter template that I used to bring up the skeleton of the application, has been pretty well maintained, and I took some pains when designing it, to create the most up to date site possible. No versions of anything are pinned in the pip-tools .in files, and the requirements are resolved at the time the cookiecutter is run.

Even so, other places that I hadn't thought to look had rotted away:

  • pre-commit.config.yml was out of date with many of its revs.
  • flake8 started failing because of changes in a major version
  • An initiative to add accessibility testing into jade-truffle had some quirks that I missed on the initial PR.

I had to fix all of those to go from angry red x's on my repo to happy green ticks.

On to tomorrow.

Previous Post

Next Post

AWS GenAI LIVE image

How is generative AI increasing efficiency?

Join AWS GenAI LIVE! to find out how gen AI is reshaping productivity, streamlining processes, and driving innovation.

Learn more

Top comments (0)

nextjs tutorial video

Youtube Tutorial Series 📺

So you built a Next.js app, but you need a clear view of the entire operation flow to be able to identify performance bottlenecks before you launch. But how do you get started? Get the essentials on tracing for Next.js from @nikolovlazar in this video series 👀

Watch the Youtube series

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay