Wax and Wane

Government spending and/or increased taxes are not bad in and of themselves. What matters in every situation where a politician proposes these things is not only what the change will do to the individual and the company but what it will do for the economy as a whole and whether expanding or contracting these things is the right move given the current state of the nation.

In general, you can have some situations where taxes are needed to fuel government spending and some where they are not. In times of deficit there are not enough funds to cover spending, so you have two options. You can either raise taxes or you can cut spending. Cutting spending is the obvious first choice but will only work to an extent before you start losing control of the basics that our government provides, such as police forces, legislative branches, etc. The only option that remains when cutting spending is not viable is to raise taxes. Conversely, if the nation is in a surplus then raising taxes and reducing government spending don’t really make a lot of sense.

Likewise, government spending can be both a blessing and a burden. In times of economic stagnation government spending, when applied judiciously, can help to stimulate growth within the economy. However, overspending by the government can have the counteractive effect of helping to ramp up inflation, which then has a trickle down effect on unemployment and the general welfare of the economy.

The point I am driving at here is simple: government spending and taxes are only bad in the situation that they are used inappropriately. If you hear that a given senator, mayor, or city official wants to raise taxes, don’t immediately shut them out. Listen to why they want to raise them then judge whether their reasoning is flawed or not. Many times this exercise will reveal that the individual isn’t making the choice that is in the best interest of the people. However, many other times this will prove to be the right choice. Some praise Reagan for operating the country very well in a deficit while others praise Clinton for doing the same with a surplus. The ultimate goal is a zero state where spending exactly equals taxes, however in the inevitable absence of this near mythical zero state, increases and decreases in both government spending and taxes will be warranted in certain situations.

The Art of Verbocity

Saying just the right amount is an art. It is hard to say just enough to convey your point while not getting overly verbose.

Take for example a simple directive: “Go”. While this directive lets us know what to do it lacks information. Where should I go? Why should I go? Does this mean me physically or something I am supposed to do?

Update the example to this: “Go down the street, take a right, go 3.4 mils, turn left, watch for traffic, cross the street. go into Sav-A-Lot Grocery, grab some cookies, and come back”. This is very exact but may be overly verbose. If I already know were the Sav-A-Lot is then this information is arbitrary and doesn’t really add much to the overall context. This example does, however, give more information as to the purpose of the directive is.

Perhaps a median ground is best: “Go get some cookies”. The directive is meaningful, succinct, and has enough information to keep the person targeted by the statement from being overly curious.

The same thing applies to code comments. You should write enough so that the situation is clearly explained without going into too much detail. If you find yourself not writing comments or writing one or two words, this is the equivalent of “Go”. If you find yourself describing what the code itself does, this is the equivalent of the overly verbose version of “Go…”. Since the code itself offers direction, the purpose of the comments should be to simply tell what the overall purpose of the code is and why it is doing the things it does. This is the equivalent of the “Go get some cookies” directive. It is enough information to provide some help but not too little or too much.

Working Smarter Versus Working Smarter

I previously wrote about Working Smart Versus Working Smarter. In it I spoke about how I needed to pull a bunch of fence posts out of the ground. Instead of taking the obvious option of getting a shovel and starting to dig (working hard) I chose to build something that will do the same amount of work with less effort (working smart). This contraption worked fine for a while, however I came to realize that even when working smart there are ways to work smarter.

This past weekend Mark Turansky and Dan Mace came over to help me pull an old four foot picket fence out and set the posts for a new six foot privacy fence. We started using my contraption and found that, while it was a little unwieldy to move, it was doing the job. We pulled a couple posts then someone pointed out that the 3/8″ stainless steel eye bolt was actually bending. For whatever reason the post, while it would wiggle quite a bit, was firmly rooted and was not going to come up with the aid of just my contraption.

untitled.jpg

So we took a step back to think about the situation and came up with the solution of wetting the ground to help loosen the soil. After hosing down the area for about a minute one of the guys pushed against the post, only to find that he could now almost pull it out by himself, with his bare hands. We cast the contraption aside and use this method to wrench the rest of the posts from the ground.

Working smart doesn’t preclude improvements. There is almost always a way to work smarter – finding it is the real challenge.