Finding Problems

Based on some ideas I heard on a podcast, I’ve started writing down things that annoy me.  I’ve got two plans on this.  One, I want to know whether I’m focusing on issues that are important or issues that are completely out of my control.  But second, and most important, was that it provides a list of potential opportunities that can be fixed.

So to do this, you simply need to write down three annoyances a day.  You do this every day for 30 days.  After those 30 days, then you have a list of problems that you have the potential to solve.  What I’ve found is that I’ve trained myself to not complain.  And I’ve been trying to start this project for several days. 

But I drive around, and I work, and I run into things that annoy me.  And they piss me off for about 3 seconds.  And then I’m off again, without any remembrance of what made me mad.  So I’ve had to take special effort to both remember what pissed me off.  And I also have to take special notice to write down those things that piss me off.

 

Funny thing is… once you’ve trained yourself to not be so critical of the world, it’s hard to go back to be critical.  But those observations are just what you need to find opportunity.

Breakfast thoughts

As a person who is chronically scrawny, I find the weight gain segment of the market heavily under served.  Though the solutions to both weight loss and weight gain are simple, it seems like ten thousand books have been written on weight loss, and only 1 or 2 on weight gain.  I guess people see it as a non-problem.

I've been reading The Black Swan by Nassim Nicholas Taleb.  It's quite an interesting jaunt into the world of the highly improbable.  I've made it through chapter 5, and I'm beginning to agree with most of what he has written.  I'm guessing it's very easy to underestimate the importance of things the can scale.

The thought I had while sitting in church was fairly simple.  Maybe it's the one I should be paying attention to.

Are you working on a solution that scales?  If it doesn't, stop.  

Scaling is the only hope of financial explosion. 

Which, that fits correctly with everything else I've read.  It ties in nicely with Robert Kyosaki, and countless others.  The problem is a simple one: the employer only gets paid for the work they do.  If you want to get paid more, you have to put in more time.

The entrepreneur creates one thing that can be sold to many people.  The thing is created once, and then you sell it for as many as you can possibly make money on.  Because of scaling, your idea went from one to millions in a short period.  Your financial situation was thrown for a loop.  Why?  Because you realized a profit on your idea that scaled.

Anyways... the day is calling.

Time to go think of things that scale.

 

A New Beginning

It’s a new year and a new beginning.  What could I say about it? 

I’m not sure.  Because my current blogging status is based off whim, I really haven’t had anything to say.  Or at least I don’t think I have.  The problem with operating by whim is you don’t spend a lot of time thinking about what you are going to say.  It’s time spent waiting for inspiration to show up.

Which is exactly opposite of what I normally teach. 

So maybe the answer is I should start talking about the complications and problems associated with trying to get something started.  But then, most of those are mental.  And the answer is “quit procrastinating” and do something.

It’s really that simple.

Whenever you get the idea, start then.  Don’t wait until the beginning of the week.  Start right then. 

Hopefully, you’ll get a small victory before the grind sets in and it becomes a lot like work. 

And if it doesn’t, happy grinding. 

The normal answer

I've been working like a crazy man the last couple of weeks.  Putting in hours the normal individual wouldn't consider sane.  But it's done.  Or at least at a temporary standstill. I started writing an article about the time spent.  It wasn't worth a shit.  I haven't moved on.

I started writing, and it seemed like a good thing.  Then I realized I sounded like a whiny little bum.

Too much "oh poor me".

And another part of me started speaking up.

"What would haji do?"  Do they care that you haven't slept in 36 hours?  Are you still sane?

When your friends die, what's your excuse?  Did you do your best, or did you roll over like a little bum?

What could you have done?  Why are you living a life of regret?  Grab the wheel and force the ship in the direction you want it to go.  Damn the torpedoes.

Quit making excuses.  Grab the wheel.  Put your back in to it.

And if it isn't moving, start kicking it.  Kick until it moves.  Make it move.

"Does haji care you had a bad day?"

"Does haji care you haven't slept?"

Move the damn wheel.

Make it move.

Haji will kill you and not think twice.  He will drop a bomb on your day and completely fuck your world.

Adapt.  Improvise.  Overcome.

Don't let that asshole keep you from your goals.

Don't be an excuse.   Be an answer.





Dedicated to 3/4 and 3/5.  The assholes that saved my ass in a firefight.  Because when I was weak, they were strong.

Ooh rah.

Useful Cisco Commands

Here's a collection of Cisco commands I still haven't been taught by Cisco.  But I learned through various other methods.

terminal monitor
and
term no mon
Terminal monitor is the answer to all remote diagnostic issues.  So when you ssh or telnet into a client, you then get the output you would if you were on site.  The only problem is that output occasionally drives you mad as you try to figure out the solution to a problem.  How in the world do you turn it off?  That's where term no mon comes into play.  It turns off console connections for after they have been turned on with terminal monitor.  Terminal monitor is taught in class.  Term no mon is not.

term len 0
Another terminal command.  The terminal length command tells how many lines of output to display when you hit a key.  But term len 0 has a special use.  Let's say you want to do a quick examination of the entire running config of a site.  How do I do that?

Using Putty, turn on logging.  I'd actually recommend setting logging to default so it logs every piece of output forever. Might be useful when you have other issues.  Next, remote access the system via telnet or ssh.  Next.  term len 0.  You now just set the terminal length to 0, so it will display the entire output without having to press a single key.  Guess what?  No more parsing crud out of text files.  You now have a complete running config stored in the Putty log file that only needs minor parsing.  No more removing typing, input characters, or what not.  Just open the file and remove the login/logout sections.

Next, exit.  Do not save.  No not write.  That way, the next time you log in everything will be just as you found it before.  No weirdness or strangeness.  Otherwise you might have to use term len 10 or something to that effect to put it all back together again.

monitor session 1 source interface interface_name/number
monitor session 1 destination interface interface_name/number
The only pair of commands in my list.  I've only used these commands on switches.  They might work on routers as well.  Not sure.  But here's the great thing about these commands: along with Wireshark, you can kick back and examine all the traffic going through a device in order to try and troubleshoot communication issues.  It's kind of like a programmable hub, but better.  And, you can monitor as few or as many ports as you want.  I'm sure there's limitations to the commands, but like I said, these are things I've learned that classes have never taught me.

So, there you go.  A short collection of Cisco commands that seem to make life easier.  Or get rid of terminal monitor after you start it up.  Hope it helps.

It's always easy

I was going to write something on a subject I conjecture about, but really know nothing about. So I decided to scrap that and go with something else.  Perhaps this.  This might get scrapped before I finish writing it.  If not, lucky you!

I'm struck by how everything is always described as being "easy" as long as you use the correct method.  Which seems really strange because you need to know the correct method in order to use the correct method, and learning the correct method is generally trial and error.

Anyways.  I really see two variations in this theme.  One sells books, and the other is the truth.  The first is that everything is always easy.  Which is strange, because I can't describe anything I do as easy.  Sure, I make it look easy.  But I've got 5 years of hard experience in my job.  I've also done an okay job at learning how to learn.  I also understand that the primary way to learn is something I call blunt force trauma.  The goal with blunt force trauma is simple.  Beat a subject into your brain until it sticks.  Keep doing it over and over and over again. I've heard of plenty of shortcuts, but none of them work as well as blunt force trauma.  That's how I've passed my Cisco classes.

Because really, learning is work.  And work by and large is hard.  But it is fulfilling.  But it's hard.  It's a lot easier to kick back and use some passive method of studying.  I could watch videos all day long and not gain anything out of them.  Nor could I tell you what I read.  It just doesn't stick.  Because it requires no interaction and no concentration on my part.  Perhaps if I'd trained my brain differently, then I would instantly start learning the instant I sat in front of a TV.  But in reality I've spent years telling my brain to sit down and shut up when I'm in front of a TV.  And usually, my brain rebels.  So I watch about 30 minutes of TV a week.  There's far too many other things that I find interesting and would like to engage my brain in besides passive non-interaction.

At the moment, I happen to be reading Peak Learning by Ronald Gross.  He has a tendency to use the "it's so easy" method quite a bit.  But I've also covered 1/6 of the book, and he has yet to begin discussing learning how to learn.  And that's the purpose of the book, right?  So the question becomes when does the author try to get into the material so I can start learning how to learn?  In general, I'll probably gain 2-3 good insights out of the book.

I also happen to be reading Computer Vision by Dana H Ballard and Christopher Brown.  In comparison, I haven't heard anything described as "easy".  In comparison, it's better described as dense and/or heavily packed.  There is little room for fluff in this book.  Unfortunately, there's not really an easy way to go through that book.

Last Projects for Cisco 3

So I just finished my last two packet tracers for my Cisco 3 class.  Presented, for all your wonderful glory, is a picture of my EIGRP capstone project.  

Which I have to admit is about as complicated as some things I've designed for work, and are actually in operation.  The fun thing about this one is I ended up setting up DHCP on every single one of those networks in there, so the end user connections are all DHCP assigned.  The EIGRP portion wasn't that difficult.  Mostly, it was just labor. 

The interesting thing was in creating the ISP connection.  Really, it's just a router with an assigned public IP.  From there, I added a default route back towards the network I designed.  It might have been more interesting to design the thing as a multiaccess network, but who cares.  The system wanted a multiple location EIGRP network.  So I used serial connections.  And funny thing is, I've never had to set up a serial connection in real life.  All Ethernet based.  One was PPPOE, and that was a bit annoying to set up.  

So now, all I have to do is study for the final and start working on the next book.  In the process of taking over four stores.  Isn't work fun?