Graph-based resumes and the AJC Bridge

I once wasted six months trying to pivot my career by pretending I had a standard tech background, only to get rejected by every recruiter who saw my non-linear path as a red flag. They wanted a straight line; I had a web of different life experiences. I learned the hard way that if you present a chaotic history as a chronological list, you look like a flight risk rather than a versatile engineer.

The "Unboxable in Tech" series shows a better way to handle this. The author had a resume that looked like a disaster—restaurant work, postal service, school aide—until he stopped fighting the CV format and started using graph theory. He mapped his roles as nodes and edges. This turned a "messy" history into a logical network where his developer identity acted as the underlying thread connecting everything. For anyone on a non-traditional path, the goal shouldn't be to hide the gaps, but to visualize the connections.

This same logic applies to how we handle our dev stacks. In my mobile work, I see teams constantly burning hours on massive migrations because they think "modern" means ditching everything old. There is this huge bias in the web community against WordPress, with everyone pushing Hugo or Astro as the only "correct" way to build.

The author avoids this friction by using his "AJC Bridge" instead of a total migration. He realized the issue wasn't the CMS itself, but the hosting model. Rather than forcing a move to a new writing interface, he built a plugin that hooks into the WordPress publish action and pushes content directly to a static site. It’s a bridge, not a replacement. He even landed in the top 7% of a GitHub Copilot CLI challenge with it.

In a team environment, we shouldn't be tearing down functional workflows just to chase the latest trend. If you can build a connection between the tools your team knows and the infrastructure you actually need, you save more time than a complete stack rewrite ever would.

https://github.com/unboxable-in-tech/ajc-bridge