Documenting my What and Why.
November 15, 2019

This post is a bit of a brain dump, a way for me to articulate my frustrations and hopefully, the start of a solution. I've been coding for a while now (over 13 years!), and I'm tired of reinventing the wheel. Specifically, I'm tired of writing the same code over and over again.

What I am trying to do?

I'm trying to automate repetitive coding tasks, particularly within frameworks and libraries. This isn't about fancy AI/ML stuff, but rather about creating standardized, reusable components for common functionalities. Think less "Skynet" and more "smart snippets."

Why I am trying to do it?

Simply put: I'm tired of rewriting code I've already written. It's a time sink, and frankly, it's boring. For over a decade, I've been writing and rewriting the same basic code blocks, and it's starting to wear me down.

A Case in Point: The Login System

I wrote my first login system back in 2006. Guess what? I'm still writing login systems in 2019.

This time, it really hit me –

  • Why haven't I automated this already?

  • Why am I still manually building something I've built countless times before?

This realization has spurred me to finally address this issue. I want to create a standardized, extensible base for common functionalities like login systems, allowing me to quickly and easily implement them without starting from scratch each time. This is about solving my own problem first, scratching my own itch.

Basically:

  • What: Automating repetitive coding tasks within frameworks and libraries.

  • Why: To avoid rewriting the same code repeatedly, saving time and effort.

Looking Ahead

I'm not entirely sure how this will shape up, but I'm determined to find a solution. Perhaps it will involve creating reusable code libraries, or developing standardized templates. The goal is to streamline my workflow and eliminate redundant coding tasks.

Side note: CakePHP 4.x being in beta is exciting, but not directly related to this particular quest for automation.

2025