Curious what's the proper length for these. I've got a few days of material now and I haven't been cohesive enough to pull everything together with certain thoughts to get this out there on a regular basis.


Relationships, mannnnnn. Work relationships. Relationships relationships. Family relationships. Hell, the relationships of characters in the books you read.

There's some crazy sort of inner workings all around us when it comes to relationships and how often do we actually take the time to digest or try and really look at what we're seeing?

New chica, who dis? There's a new person in my life and it's hilarious the sorts of things that crop up at the beginning of meeting/pursuing someone. Too much? Too soon? Talk to them? Ignore them? Chase them? Wait for them to chase you? Shit's weird. It's all games but sometimes I think the games are necessary.

I used to think the whole full honesty and throwing it all at em at once was a good method but there's maybe an art to falling in love that takes some highs and lows to get right before you can make it there.

highs and lows

My mind still swirls around the concept of work and life combined together. I'm chillin at work and flipping back and forth trying to figure out a bugger of a problem getting Keycloak token exchange working for Google tokens and then back on my own bullshit trying to get my head straight about having equity in myself. Equity and equinimity are very similar words but I think they go hand in hand.

So there's this concept in computer science and just engineering in general since the early 2000s that's called "agile". TBH it's kind of a stupid system but most tech companies put in place 3 major systems for productivity:

  • OKRs
  • KPIs
  • agile/scrum/sprints

First we have objectives and key results. The major gist of this is that you you set out for an "objective" much like a goal and there are certain key results to accomplish that get you close to that objective. These small little results stack together to get to a goal. Miles on a run or minutes on a treadmill, etc.

Next comes the key performance indices. These are what I like to call scorecards. We all have metrics that we live by like pounds or height or words written or miles run this month. Key results can combine together in a certain category to get reach a certain number on your performance index but it's not necessary. These numbers are helpful to track change over time instead of major objectives and/or missions. You don't want your goal to be just monthly users or readers of this blog or whatever. You hope that your mission is bigger than that.

Build the voice; not the decibel level.

Last is more common to all tech things everywhere. Work in minute increments. Some people do 2 week cycles or maybe 1 week if you're extra hard core and maybe a month if you like solo work. The concept here is that you come up for breath every so often and only work in mini milestones. The work inside these "sprints" should all usually be headed towards an objective. Hell, getting the tasks done in a sprint can be part of your KPIs but just doing a task for the sake of doing a task is dumb obvi.

So you keep this going over and over and over and suddenly 2 years have gone by but you look back and realize that you've been so caught up in the work goals that you forgot about your personal goals. Equity is key here. Equity, equity, equity. Personal stake. For us developers/software engineers it's really easy to get a voice going that is a drop in the bucket as far as equity goes.

A Twitter account is equity but that equity is small in comparison to your own website. Do you own the architecture that gets you heard? If the world was gone tomorrow and with it the internet do you have your words somewhere? Do you have the drops in the bucket that you can truly call your property? Some might think this is a stupid way to think of things but hell if I ever want to lose what I've written or made or produced. That's the hard part with digital things in general.

Good book that puts a lot of these thoughts into perspective is How to Talk About Books You Haven't Read by Pierre Bayard. The idea is that you ain't ever going to read every book on the face of the planet but you can sure as shit try. There's a concept that past a certain number of books you find patterns and sequences that allow you to get the gist. Don't ever feel like you're not good enough to have an opinion in this regard. Wisdom has more power than knowledge but the only way to get that wisdom is to be passed down the knowledge or to distill enough knowledge in the general direction.

grandpa Cologero's journal

Holy shit! I totally forgot. I've been working with a company in Greenpoint that specializes in video production and digital assets to get a digitized copy of my great-great gandfather's journal translated.

Christian -> David -> Charles -> Joseph -> Calogero/Charles

So that's 4 generations holy shit and I have a pristine copy of his stuff. The journal is from 1911 supposedly and there are article clippings from the Schenectady newspaper he wrote in. I'm so excited to see what I'll find in this thing but so excited I found this company that makes such amazing photo copies from any paper stuff you want. I'm paying $615.07 for roughly 300 total pages. So excited to get this back. Hopefully a couple weeks and I'll get this.

Share the love!

Thank y'all kindly for the read!