Notes about my work, projects, training, and life.
Recovery gets stronger when your boundaries do.
You cannot protect a rebuilt life while giving everything and everyone unlimited access to you.
Some things need a firm no. Some situations need distance. Some relationships need limits.
Strong boundaries are not punishment.
They are protection for the standards you refuse to lose.
https://jimlunsford.com/recovery-standard-strong-boundaries/
I did not release a new version of Bonumark Stream on GitHub today like I said I was going to yesterday.
Kelly and I decided to take the day and recover from the concert instead.
And no, we do not drink.
We are just old. Lol.
Bonumark Stream will still be there tomorrow. Today was for doing absolutely nothing useful and being okay with it.
Bonumark Stream got better when I stopped treating every problem like it needed another feature.
This rebuild was about defining boundaries: Stream is publishing, Profiles are identity, Themes own presentation, Admin owns management, and Core owns platform behavior.
That clearer architecture came from testing real workflows, catching bad assumptions, rejecting the wrong direction, and rebuilding where necessary.
https://jimlunsford.com/builder-receipt-reworking-bonumark-stream/
Kelly and I had a great time at the Five Finger Death Punch concert tonight.
We have seen them before, and they never disappoint. They always put on one hell of a show.
Good music, loud as hell, and a good night out together.
Exactly what we needed.
Bonumark Stream’s Profile system needed more than a few extra fields.
I rebuilt it from a clean baseline around one rule: the Profile represents identity, while the existing Stream remains the publishing surface.
That distinction shaped everything that followed.
Desktop and mobile testing drove several revisions across Featured work, photos, profile metadata, portability, and the overall layout. Along the way, testing also exposed an unrelated empty-Stream layout bug that needed corrected.
The result is a much stronger Profile system without turning Bonumark Stream into another social network.
The Stream is still where the publishing happens.
The Profile now gives the person behind it a place to actually exist.
I will be releasing a new version on GitHub tomorrow with these changes.
Today’s run sucked. I never found a comfortable rhythm, the heat made everything feel heavier, and a 9:16 pace felt harder than it should have.
I still finished 3.02 miles in 28 minutes.
That is the part people misunderstand about discipline. It is not about feeling strong every day. It is about keeping the standard alive when you don’t.
Some days the run feels easy. Some days you fight for every mile.
Either way, the work gets done.
Discipline doesn’t take a day off.
Yesterday was basically a blur after two nights of working night shift at the jail.
I never sleep much between those shifts, so I spent most of the day walking around like a zombie and doing just enough to stay functional.
Thankfully, I finally got more than enough sleep last night, which is good timing because tonight is going to be a hell of a lot more fun.
Kelly and I are going to see Five Finger Death Punch in concert.
Night shift recovery complete.
Now it is time for loud music and a much better kind of exhaustion.
Comfort will always ask you to stop early.
Discipline asks for one more step, one more rep, one more hard choice when quitting would be easier.
You do not build confidence by avoiding discomfort. You build it by proving you can move through it.
Welcome the hard thing.
https://jimlunsford.com/discipline-dispatch-welcome-discipline/
For the first time since I started using AI to help me build Bonumark Stream, I had to abandon hours of work because the development direction went bad.
The problem was not one broken screen. Too many architectural assumptions got introduced, then each correction tried to fix the previous mistake with another layer.
A simple Profile feature started bleeding into routing, theme behavior, metadata, exports, and presentation state. Some of those decisions conflicted with what Bonumark Stream already is.
So I stopped.
That matters.
Building with AI does not remove the need for judgment. It makes judgment more important. You still have to understand the product, recognize when the architecture is drifting, test the work, and be willing to throw away hours instead of protecting bad decisions because you already invested time in them.
The lesson was simple: preserve the existing architecture, define the boundaries first, and never let one wrong assumption turn into five more.
