1
2

craft> fellowshiptech.pop "Nick"
craft> newrelic.push "Nick"

For the past several months I have felt the absence of peace in what I had been doing at Fellowship Technologies. Not that I wasn’t putting my heart into what I did, or that the people aspect was making me miserable or even that the work was a tyrannical laundry list. Quite the contrary, even though sometimes it was a challenge to move forward because of process or technical debt I loved the people I was blessed to work with and I pressed into the work that we needed to do to try and make a difference in the world.

A little history before I go on…

Rewind a little over 8 years ago. I went to interview for a new gig at Fellowship Church in Grapevine, TX for a web developer position because I felt that I would make more of a difference in the world then throwing web bits at Gamestop.com (another awesome gig that I was blessed to have). I had the interview and I didn’t feel 100% about it, though that could’ve been because they were doing some things in classic ASP and talking about moving to PHP.

Later that week I got a call from the guy that I would be replacing and he said, “I liked what I heard in the interview - what do you think about going to do this start up thing with me and some other guys - we’ll be writing software for churches…”

I’m sorry, could you say that again? Did you say software for churches? I didn’t know there was a need for that. Apparently there was, in a big way.

I joined up, and they threw me and another dev in a closet at the church and… 8 years, 5 conferences, 4 different office buildings, more devs, a billion lines of code, 48 applications, a gazillion (sp?) rows of data, many really awesome people, a whole lot of long nights and foosball games, and one acquisition and IPO - here I stand a changed dev; a changed person.

So where is the peace?

I’m not going to go into some long diatribe about the hardships I faced because frankly there really were none. Sure there were things I dissagreed with or got frustrated by but Active is a great corporate body trying to solve some really hard problems. So then, why am I leaving?

My first motivation is something I have been fighting for months now - God has been telling me to pick my mat up and move. Bottom line, as a Christian, I could not avoid the pull. I mean, after all why would I move? Great benefits, I was comfortable / confident in what I did, great support system in Texas, loved the people I worked with - why would I not have peace?

Second, my wife and I had grown so much in our marriage with God we could face what a complete family reboot meant - so our hearts were in the right spot for change. We agreed that no matter what, if we disagreed on anything around change we would not do it.

Third, I read and understood the holstee manifesto. I remember talking to my wife telling her that I really felt like I was not good enough to do anything really “great.” To which she promptly replied, “You arn’t. Quit trying to rely on what you think you know and rely on the plan God has for you.” Boom! I love my wife.

What did I do about it?

After getting the pride smack-down by my beautiful wife. I decided to list out 7 companies that inspired me; that, as a dev, I looked up to. I then wrote a few thoughts down on why I would want to be a part of the amazing work each company was doing.

Flying is learning how to throw yourself at the ground and miss.

New Relic was, of course, at the top of the list. As a dev how could you not look up to and admire the shockwave they have sent through the worldwide developer ecosystem. They have fundamentally changed the way many developers and Ops guys work together - empowering developers worldwide to get better by understanding what is actually going on with, and how to fix their software - who wouldn’t want to be a part of making dev life’s better?!?

The engineers at new relic have done for monitoring what DHH and Matz did for software - they have revolutionized how we make great bits. New Relic genuinely cares about their people and the developers they serve and it is evident time and time again as we use the software and as I interact with the team. There are some of the most ingenious and brilliantly minded people in that group. It is literally a polyglot’s paradise where they have guys who are experts in Ruby, PHP, Python, Java, and .NET and they all work together innovating on an amazing product - there is no company out there like it!

So I took a leap. I was swooned by the amazing team and the love they showed me right up front and the hard to miss excitement everyone had for what they do there.

Now what?

1
2

life> rm -r "/God/FloydFamily1.0"
life> mkdir "/God/FloydFamily2.0"

My family (5 rock solid kiddos and a beautiful and patient wife) and I are doing a complete reboot - moving et. al. Are we sad to be leaving our friends and family, yes definitely. Has it been easy, not entirely but we trust in how we are being led. I am humbled by how orchestrated this entire thing has been from it’s beginning until now - we are definitely looking forward to the adventure.

Find me on the Twitters if you ever want to chat about life change or geek out over tech.

Often times I hear developer “happiness” come up when turn over happens. It’s all part of the “game” right? As a creative, why would you stay somewhere that was not helping you become a better painter or a place where you would get really excited about what you do?

To be pragmatic, I feel like I need to claim reality as well - we as devs also need / have to do the grimy grind work because not every line of code creates an epic bloom of fireworks. Face it, we have to mix our paint if we want the really cool colors.

I’ve been thinking a lot on the signs of complacency or waining enthusiasm developers face on long running projects; what keeps us motivated and how do we recognize that the “passion” has left? Then I thought ”soup stone!”

It’s funny how a common cause motivates people. For instance if you’ve ever done the startup thing then you know that everyone has a lot to do and has many hats to wear. Generally there is never much whining about what they “want to do” rather there is a lot of moving on what they “need to do” - need becomes want because of the cause.

Let’s play a little metaphor game with the soup stone folk story:

Say that the stone is the company (because without people and product all a company really is, is an idea, a dream) and the ingredients added to the soup by others is the code that is written to motivate and move the company. What happens if your developers start pursuing other projects on the side and take their ingredients there. Why would they do that? What would motivate them to continue working on the mythical soup to make it a real soup?

Sharing is a massive problem for companies.

I’m not talking about OSS necessarily but something along the lines of the mentality where “as developer in company X I am not challenged nor am I motivated to be exceptional therefore I will go make products of my own that do excite me.” On one hand you want your developers to be challenged and grow, on the other hand wouldn’t you want your developers to be so excited about what your doing to not have to go and do the side gig thing to get the dev itch scratched?

Is it possible to ask a dev: “what can we do to get you more interested in what you’re doing here?” - who wouldn’t want to be energized and excited about their day job allowing you to make your night job “life.”

Detaching myself and deciding that I am a user rather than the developer is hard for me. I used to find it difficult to watch people use the software I created… always wondering if it was good enough, if they’d like it or if I created an app where people become pixel hunters waiting for alt text to appear rather than users trying to get something done.

I really don’t feel that way anymore, the fact is it will never be good enough or perfect it will just be what it always has been - my best effort. If it doesn’t work I’ll start over or change it; if it does make someone’s life better then I’ll do something else.

One of the most amazing things about creating software is that if you did it once, you can do it again and most likely you’ll do it better. One of the best ways to learn how to get better is to be quiet, watch and experience your software with your users and listen to everything they say, even if you disagree with them - especially if you disagree with them.

This book is primarily focuses on Continuous Delivery and not Continuous Deployment per se, it etches into an architectural area (around pages 347-349) that I feel every software ecosystem should have.

Feature Dark

dark side rule #1: Releasing small, even unfinished bits into production is ok and will actually save you from head aches.

Delivering features into customers hands should be exciting not terrifying - how many of you have placed bets on the success or failure of a gargantuan release? Why do we have humongous deployments that are scary? Being big and scary didn’t really work out for the dinosaurs did it and it won’t work for your software either. Create a parallel page, work on the model first - do something other than stop to wonder how you’re going to eat the elephant (i.e. big things need to be eaten one bite at a time).

dark side rule #2: Putting software into production does not always mean that you are putting it into the hands of your users. Your software should have toggles that turn features (partial or otherwise) on for either some or all users

I believe that developers should be able to release code right to production, bottom line. If you disagree then you either need to get new developers or you need to start trusting the ones you have. I also believe that every commit after going through quality gates should go right to production once it hits master.

Write your code so that if the doomsday scenario of someone elbowing the keyboard won’t put your latest UX redesign in front of your customers. Histrionics aside make your software “releasable.” Don’t expect a magic bullet here either, this will take team maturity and some patterns for everyone to stick to (like the ones @chadmeyer and I created - pushing features dark). Best idea here is to come up with an easy to understand / use patten and make sure that the business is tooled to flip those switches.

dark side rule #3: Let your business worry about releasing the software to the customers and let your developers worry about writing and deploying said software

See - cd vs. cd. Look @ your keyboard, go ahead I’ll wait……

If the symbols <,>,{,},# are worn then you are a developer. Do what you’re good at - write and deploy code.

If the # key or the letters a,t,t,n,. are worn then you know who you are. Go put the software developed into the hands and minds of the customers

dark side rule #4: Your features might not always fit into or be able to be feature dark

You just won’t. There will be organizational challenges, changes, events and technical roadblocks that will take time to get past. The goal here is to incrementally get there. Be pragmatic.

dark side rule #5: Ruled by fear your competitors are… deploying software all the time you will be…

See amazon, flickr, so on.

Note: The dark side rules are my own creations and are only based on my experience with what works and does not work while I have been in dev shops trying to achieve CD, so take them with a grain of salt to season your own rules.

Let’s say you just bought this massive steak that you’re going prep before the game. So you know you’re gonna create an awesome rub then toss it on the grill at a solid 600° and just go to town on the beautiful cow bouquet.

You get to the counter and it is covered in the remanence of last night’s game fest. Baring any cultures that the CDC might want to take for posterity do you really stop and think… “Hmmmmm, should I clean the counter before I do the rub throw-down on this $50 steak?” No you don’t… so why do we do it with the code we write?

You’re in some pretty rough code and you add a beautiful bit of code to it, do you leave the other bits around it trashed; lipstick on a pig. Word to the wise, be a boy scout, leave it in a better condition than you found it.

Teaching tools:
hackety-hack.com/
codeschool.com/courses/rails-for-zombies
codeschool.com/courses/try-ruby
rubylearning.org/
railscasts.com/
teachmetocode.com/
rubyrogues.com/
ruby.railstutorial.org/
guides.rubyonrails.org/
rubyflow.com/
refactormycode.com/
pry.github.com/

Screen / pod casts:
peepcode.com/screencasts/ruby-on-rails
rubyshow.com/
www.destroyallsoftware.com

irc:
#rubyonrails (irc.freenode.net)
#ruby (irc.freenode.net)

Books
Why’s (Poignant) Guide to Ruby
The Pickaxe
Beginning Rails 3
Beginning Ruby
Humble little ruby book
Exceptional Ruby

I have to admit, Hollywood makes slamming out bits look cool and easy - not nerd cool like node.js or mongodb but more like socially acceptable “teen” cool like eating Pringles, drinking mountain dew or jolt and getting away with “something.” Right now I am snacking on Pringles and drinking mountain dew - the propaganda worked!

Though my boys haven’t seen those movies they are familiar with the “hacker” architype of a guy mashing keys having code fly across the screen to save the world from total meltdown! So, as I expected we hit a productivity wall with the “code” part of this project.

Needless to say here is my 6 year old’s first lines of code:

    public Earth(){    
        super(750, 750, 1); 
        addObject(new Turtle(), 0,350);
        Greenfoot.playSound("mnhaon.mp3");
    }

and the 4 year old’s in the Turtle class:

public void act(){
    moveLeft();
}

It took us roughly 30 minutes of them typing (20 minutes) and going through the greenfoot API docs by themselves (10 minutes) to get that done. At this point and time they saw a turtle run left across a white screen and they were done, shutdoor. I expected this so I did have a back up plan….

Making media for the game: They spent the remainder of or time making trucks, turtles, backgrounds and recording sounds for the game. I wrote the remaining code and added some snips from Michael Kölling’s blog.

What we learned:

• Making games together can be fun and we can actually get something enjoyable done in a short period of time.
• Greenfoot is a great platform for new developers and there are others out there such as: Alice, Kudo, scratch and others, so there is really no excuse to not teach your kids if they are interested.
• My boys were too young (6 and 5 years old) to code. Kind of obvious but I really wanted to see where they were at as far as logic thinkers - I was impressed with there ability to articulate what they wanted to do all I had to do was write the code

The bits:

• Framework: Greenfoot (Java)
• Hardware: imac
• Time: roughly a week (1hr per day)
• Process: scrum
• Output: source | game in gallery | stand alone game

If you have time please let my boys know what you think about their project, I know they’ed love to see your comments and thoughts, they worked really hard and I am super proud of them for doing all that they did and trying as hard as they did. Related posts: kid gamification - planning, kid gamification - day 1, kid gamification - day 2

Today we focused on:

• getting our project all planned out using sudo scrum (didn’t want to get wrapped up in teaching them the process in depth; just that there is a process and it can help)
• a repo going on github
• creating a greenfoot scenario
• theme music - because every great game has cool theme music, and we were doing a lot of admin stuff for the project and I wanted the kids to have fun mixing music.

Project planning:

Using scrum, we generated cards and hijacked the grocery list whiteboard and began planning. I asked the kids questions like what do you want the game to do?, how do you think it should work?, how will you play the game? what do you want things to sound like? and so on. Their answers, to my surprise, were somewhat practical for a 5 and 6 year old. I assumed that they would say things like, “I want to control the turtle with my mind,” or “the turtle can fly and breathe fire to destroy the trucks.” The answered with we can use the “arrow keys” or “w:a:s:d” to move the turtle (apparently we need to lay off the games, their familiarity with default game controls and their ability to name them was frightening). Here are the resulting cards from their answers:

• Make game sound effects(truck sounds, turtle sounds, turtle getting hit sounds)
• Make code project
• Make story about why the turtle is doing what he is doing
• Make the turtle and truck graphics
• Make place to put our code so we dont loose it
• Make music
• Make turtle move
• Make trucks move
• Make world for trucks and turtle

Getting a repo going:

I let them type the commands in terminal, they said it felt like they were super spies trying to save the world (I never really thought of it that way…)

We…

• generated ssh key - just follow the instructions here
• setup a github account - just follow the instructions here
• created a local repo - - just follow the instructions here
• pushed the code

Creating a greenfoot scenario:

If you are parent of really young kiddos with limited attention spans like me I would recommend going through the greenfoot tutorial before you begin your senario with your kids. The tutorial will get greenfoot setup and get you aquatinted with the greenfoot API

Creating the theme music:

This was pretty fun. The kids mixed samples using Aviary audio editor. You can listen to the sample mix here.

Once we did the mixdown on the samples we made into an mp3 using the same tool and added it to our github repo.

That was it for today. Tomorrow we should have some working code g2g. We will spend the next 3 days working on code, testing and content. Finishing the game at the end of the week.

Related posts: kid gamification - planning, kid gamification - day 1, kid gamification - day 3, the finale

I told them to begin drawing pictures and just talking out loud about what they were thinking they wanted from a game. As they talked I wrote down key words that they said that had to do with: game name, characters (antagonist, protagonist), environment, and story line.

One idea was… Game name: Lego Minecraft Characters: protagonist - Lego guy, antagonist - environment Environment: Total mutable world Cool idea but it has really already been done.

Another idea was… Game name: MnHAON (no idea where he got the game name) Characters: protagonist - trucks, antagonist - turtle Environment: A road with moving cars, etc.. much like a frogger clone

We ended the hour with a couple of really good ideas where we picked the one titled “MnHAON” and decided to move on it.

We also decided on using greenfoot (i.e. java) for the project based on the simple API and java being a pretty simple language to pick up quickly.

Tomorrow we are planning on:

• Create our scrum board and cards
• Creating a github repo for the project
• Creating the “theme” music using aviary
• Creating a greenfoot project and push it to github

Related posts: kid gamification - planning, kid gamification - day 2, kid gamification - day 3, the finale

I know what your thinking: 4 boys and dad, mom is cuddling with the new baby girl - video games, junk food and movies, whoo hoo!! Well, almost…

My wonderful wife hooked me up with a lesson plan and the directive: “If you just get one or two things done that will be great.” Looking over the curriculum I saw math, reading, handwriting(who needs that?), science (cool we can blow stuff up), history (really that’s where that subject should stay), and so on. I mean my wife has this thing put together so well I felt like I might actually be able to pull off teaching my kids something other than the Konami code (a.k.a the Contra code) or how to beat Zelda (which we did).

Something felt like it was missing. So for two weeks we decided to ditch history and replace it with developing a game from 0 bits to shared. I will be teaching my 6 and 5 year olds with the following in mind:

The constraints:

1. The source must be shared via github and in a compiled playable format with in two weeks.
2. The focus will be on creating, experiencing and sharing code not the framework or deep syntax itself (so we will be using greenfoot, gosu or something like them).
3. The two students will write all of the code using XP and scrum with an occasional booster script from me
4. The two students provide all of the content: music, graphics, story and code
5. We will have fun

I am really looking forward to taking on this challenge and will be chronicling it daily, so keep up with us and follow what we are doing. I know the boys and I hope that it will inspire other parents and kids to try it out and see how far a little creativity will take them.

subscribe to follow our progress

Related posts: kid gamification - day 1, kid gamification - day 2, kid gamification - day 3, the finale

Most of us have lists. I call mine the “grrr” list (pronounced grrr). This is a list of things that constantly irritate you about the software you write but for some reason you just cannot stop to address it.

My personal software grrr list has things on it such as: rip out old data model and replace it with the new shiny one I just built, change doc-type on all of my sites - so that I can-haz HTML 5 or move all of my domain names to one provider.

The things on your grrr list are important because they cause you grief and no one likes a constant stream of grief (re: Frasier). Do yourself a favor and create a grrr list - and in moments where you could watch re-runs of Frasier instead do something on that list.

You’ll feel accomplished and less frustrated with the software you write. Then you can go outside and do something you’ve been putting off, like mowing the grass.

That seems to be much like some software deployments I been evolved with over the years. The software goes out into production and no one pays attention until the alarm goes off.

As devs pushing bits into the hands of our beloved customers, why don’t we take some time to listen to the tick of the clock. You can do this by checking the logs after a deployment, monitor cpu / memory usage or my personal favorite get a tool like newrelic and see what the impact of what you just pushed really is.

the take away: just because it was deployed to ”production” does not mean it’s done or you’re done - take time to look at what your software is doing after a release it WILL pay off.

So with all of the legacy out there who’s dealing with the underbelly of our software stacks, you know “the lowdown” where no one dares to go.

Seems to me we need to be a little like Captain Kirk. He wasn’t scared to go places where no one had been. A little unknown nerd history on the juggernaut legacy of Star Trek - Gene Roddenberry, the creator, wanted to build something that was an adventure while simultaneously conveying a moral point and political agenda. Kirk was one such character who could carry out that agenda.

Let’s pretend Captain Kirk was a night time hacker - what would that look like next to how the show played out:

The Plan

Captain: Crew set out to do something routine

Coder: Kirk decides, “Hey let’s do a twitter mashup in one of my existing apps. I want to be able to tell all of the ladies how cool I am in my yellow an black stretchy outfit.”

The Distraction

Captain: Somewhere along the way they get a call: “Planet O’ ladies are in trouble, only Kirk can save them, please hurry.”

Coder: “Crap,” says Kirk, “I have to create OAuth hooks, and it looks like all of the models in this app use .net SOAP web services and there are no flippin tests!!!” “efffffffffffffff!, The boss is gonna kill me!” Kirk exclaims.

The Moral Dilemma

Captain: The Captain must decide, should I follow orders and go or should I do the “right” thing and save the ladies, errr um, the planet.

Coder: Scratching his head he thinks: “do I give up on the app, this legacy code is gonna kill me. Or do I rewrite it so that it actually looks and works like software.”

The Decision (this is where a lot of us go off the reservation)

Captain: “Think of the lady planet, they need me! I choose yes! I choose refractor, regardless of the dangers i’ll face.”

Coder: “Think of the ladies, they need my fashion tips! I choose refractor, regardless of the dangers i’ll face.”

The Victory

Captain: He arrives, struggles with the bad guy aptly named SOAP (what, it’s my story) , looses his shirt (so that they can have a show that both the man and woman will watch), saves the planet, gets forgiven for getting off task, and there is much celebration.

Coder: He begins writing tests, refactor, test, refactor, kills the bad guy named SOAP, implements his twitter client, gets forgiven for a little scope bleed, builds a killer app, and all of the ladies rejoice because now they see that most of his fashion is based on a breakaway design.

As dangerous as it may seem we need to deal with the lowdown and be like Kirk.

the point: Go hunting occasionally - code smells are not hard to find and there will always be something to refactor.

When thinking about the business side of software I tend to think about the lions without teeth; the things that are claimed as the highest importance from the loudest people.

So as developers how do we distill the true signal in all of the noise? How do we separate the lions with teeth who we should be paying attention to from the ones without the teeth that we should be able to ignore? Have a point. In a scrum shop, this is generally set by the product owner, but we as devs are responsible for helping our groups stick to it when the pressure rises.

Impossible you say? You’re thinking, “there is no way we could all stand behind one point, the business would implode.” Really? So does that mean personal budgets don’t work, or that companies like 37signals really don’t function?

When lions bite they will do everything not to let go, because they are hungry. They know that letting go = empty belly or in the business mind => my group’s priority = my passion; those are the real lions.

What about the others? That’s where histrionics enters into the equation; where deception takes over and reality steps out. Their business mind => my priority = my passion. Stay clear of them, don’t have anything to do with them - they tend to distort, disillusion, and distract from the “goal.”

run with this: get a point for what you’re doing, write it down where it’s in your face, get behind it, do it, stay away from anyone who want’s to usurp it.

Emotions are for socially accepted people, a notion that many developers seem to struggle with - being socially acceptable, that is. So in any given dev team how do you deal with introverts and the socially challenged, when you as a leader should be, well leading (whatever that actually means to the people you’re leading).

You start by connecting on an emotional level. Try by asking what do they love about their job and what do they hate. If they give you service level answers at first start off by “actually” being real with them and tell them about your love/hate relationship with your job.

The take away: You’ll probably lean something you didn’t know; something you’ll actually be able to do something about.

Have you ever watched a war movie where the troops roll in and they start lobbing grenades, firing rockets, shooting first then asking questions and at the end of it all you see a “relief effort” swoop in and rebuild? No. After the dust has settled all you see is a bunch of broken stuff.

I feel like that matches the pattern of some of our dev-mentality. We go in with the intent of saving the village and all we do is cause a considerable amount of collateral damage then bail assuming there will be some sort of relief effort (QA perhaps).

Why do we sometime fight with hand grenades instead of knives; more like the tank and less like the ninja? It might be the glory of the battle or the sweet taste of victory (at least as far as the fight goes ); who really knows?

All software needs some degree of refactoring and sometimes huge reworks are a sound way to rid yourself of a looming / annoying problem area - but try to start by using a knife not a grenade / iteration not search and replace.

The idea… solving problems should be iterative not mass-blasting with collateral results.

We deal with “scary” legacy code all the time. The fact is if it was produced by you or someone else that doesn’t matter; it’s that it’s there.

More often than not we generally try to stay away from the code claiming that it is toxic or that by touching we would cause unforeseen consequences - claiming “you can’t just change a road.” When, in reality, it’s just code; bits cast on the grid.

Knowing that there are dangerous intersections, why don’t we as devs do something about it, change it, rework it. We have a choice: we can continue to avoid those bits or choose to make them better.

Take this up as a challenge: count in a given day, week or month how many times you or someone else groans about a section of code, functionality, etc… that has been complained about before. Not that you’ll be surprised by the result but you may realized how complacent you and other devs have become about dangerous code you’re allowing your users to use.

Drop FUD as a tool and pick up something useful in it’s place (such as unit / integration tests or parallel deprecation).

What if you could take a game like minecraft and build something like “appcraft” where you could visibly see where the weak points in your architecture are and what hardware / software relationships make up your app.

I’m not talking about some over blown UML but an almost touchable model of your software that you could actually walk through. Why would it be so odd to actually make a game of it as well others could attack your virtual stack and see if they could break it.

What would be wrong with “gaming the system” and doing software modeling inside of minecraft?

{end-of-line}

A caterpillar is made of of a series of segments and devices each with the sole purpose of processing food. I got tuned into that sole focus as he moved across my arm. A few moves then up to have a look around for food, a few moves then up looking for food again and so on…

(This is where I am not going to draw a parallel to a caterpillars focus and some software or language idiom. )

Here is what I saw…

When the caterpillar approached something natural, such as my arm, a leaf, some grass - it move like silk, without interruption. When it approached something unnatural, such as my watch, it struggled with navigation and movement.

Much like the software we write and design we loose traction when something ”unnatural” enters our systems. Being cautious of aberrant things being introduced into our ecosystem is a fundamental desire of an architect. Without this awareness our systems begin to slow and stop functioning.

Consider the caterpillar - if you run into something that slows you or your system remove / re-factor.

{end-of-line}

It comes down to ownership. Who owns the thing that you’re communicating about, are they informed and is that ownership respected. Often times people become impatient, want to “help,” want to get credit for or just want to do it their way. Which, in turn, massively distills the effectiveness of communication. If I am the solutions architect, for instance, and there is a fundamental change to “architecture” then I had better be involved and own up to the outcome.

I’m not talking about the RACI mess, to me that’s a lot of work and works just to say I’ve got it. Most things can be absolutely inferred as to who owns them. I’m not talking about the ambiguous lines like an organizational decision such as making core hours for the teams; more like the decision to change systems or software patterns.

Consider how these things pan out in life…

I own the budget in my household because i am better at numbers and cash; no “formal” decision was ever made to make me the budget czar. If you “own” something, make sure you do just that. Otherwise there will be a lot more mud in your waters that you need to inherit.

{end of line}