top of page
Search

Untitled

  • Writer: Mark Kendall
    Mark Kendall
  • Jan 9
  • 2 min read

I Asked AI to Fix My Life



(It Sent Me a Diagram)


So I did what any seasoned engineer with a few decades of scar tissue would do at the start of a new year.


I asked AI to help me with my New Year’s resolutions.


Not because I lack opinions.

Not because I need motivation.

But because sometimes you just want an external system to tell you what you already know… without emotion.


And sure enough, AI delivered.


Not a vision board.

Not a manifesto.

A diagram.


Which, frankly, should have been my first clue that this was going to be accurate.





The Results Were Annoyingly Reasonable



No “wake up at 4am and grind.”

No cold plunges.

No journaling while standing on one foot.


Instead, I got the equivalent of a clean architectural diagram for life:


  • Wake up earlier (not early, just earlier)

  • Move your body occasionally

  • Talk to other humans

  • Do meaningful work without thrashing

  • Leave room for inspiration instead of scheduling it



In other words:

basic things that work, consistently ignored because they’re not exciting.


Which explains why they work.





Turns Out Life Has Technical Debt



This is where it got uncomfortable.


Because the diagram didn’t say:


“Become a new person.”


It said:


“Stop fighting the system you’re already running.”


Life, like software, accumulates technical debt:


  • late nights

  • skipped workouts

  • inboxes pretending to be task managers

  • relationships handled “later”

  • inspiration deferred until the mythical free weekend



Eventually, the system still runs… but every change costs more than it should.


Sound familiar?





Same Rules as Architecture (Annoying, I Know)



The longer I stared at the diagram, the more it looked like something I’ve preached for years in systems design:


  • Small habits beat heroic efforts

  • Feedback loops matter

  • Humans are part of the system (whether you model them or not)

  • Stability enables speed

  • Over-optimization is just procrastination in a nicer shirt



Apparently, the same principles apply when the runtime is you.


Rude, but fair.





No Reinvention Required



The most insulting part?


There was nothing new in this diagram.


I’ve known all of this.

You’ve known all of this.

Your dog probably knows all of this.


The problem was never knowledge.


The problem was execution.


Or more accurately:

defaults.





So That’s the Plan



No dramatic transformation.

No announcement that “this year is different.”

No pretending discipline is a personality trait.


Just better defaults.

Less noise.

Fewer self-inflicted outages.


And if it works?


Great.


If not?


Well… we’ll iterate.


Refactoring in progress.





 
 
 

Recent Posts

See All
Intent-driven Engineering Framwork IDEF

TeamBrain: Turning Engineering Knowledge into a Developer Intelligence System Modern software teams don’t struggle with writing code. They struggle with remembering why the code exists. Architecture d

 
 
 

Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
Post: Blog2_Post

Subscribe Form

Thanks for submitting!

©2020 by LearnTeachMaster DevOps. Proudly created with Wix.com

bottom of page