“Just Let Me Code!”


LOL!  I have certainly felt like this before.  Knowing what I “love” to do and what I “have” to do.  We always talk about avoiding the “M & M’s”.  Managers and meetings.  Time sinks that can easily corrupt a development plan.  Getting into coding was so easy.  You pick things up, learn, and just hammer away at the keyboard.  Once it becomes a profession, it changes.  Schedules, deadlines, technology you didn’t get to choose.  It becomes more of a dodge and weave scenario vs a creative process.

Why I am in Washington, and programming with SAP!

So now that I am finally settled in to my new location, and Comcast has finally connected me online, I can post an update.

Long story short, my business partner and I developed some software over the last few months over long nights and weekends.  Very quickly we drew the attention of several investment interests.  Over several weeks, meetings, and countless demos we were dazed and confused.  We couldn’t decide if we wanted to continue running the company and keep in our direction, to bend to investment teams whims and wishes, etc.  Like a shining light, we happen to discover a company based in Vancouver, Washington who was looking for additions to their team, specifically developers in the industry we JUST BUILT SOFTWARE FOR!  It was like the ying to our yang.  Several meetings later, and we were sold.  We needed to move ASAP in order to begin integrating our technology stack, ideas, and begin solidifying a framework to revolutionize our industry.  We fell in love with the team, the direction they were on, and were in company of some seriously talented people.  We knew this was it, exactly what we had envisioned one day.

The background of our team members is as diverse as it is talented.  Most of the development team, support, and infrastructure is done within SAP’s platform of services and tools.  We are diving head first and using our intense .NET knowledge to leverage SAP’s enterprise level data and SDK.  It is a little different, leaving the web (temporarily), but all in all I believe our talents will do nothing but benefit the team and we will be able to bring strong development background to a team and industry that need solid development.

Why am I in Washington writing SAP?  For an industry.  For my team and family.  For my future, and the push for premium enterprise grade programs.

“Our project has been 90% complete for a year now…”

“Our project has been 90% complete for a year now…”

We have a running joke in my office about people/project who are “90% complete”.  I can’t tell you how many times we’ve talked to a client who says “Yeah, I hired this guy like a year ago.  He said it would take 4 months to make my web app, but here we are still not 100%.  We’re like 90% done, we just need that little push to get us to 100%”.  We take a quick look at their application (say e-commerce) and find out you can’t manage products, check out a cart, sign up for a user account.  Very far from 90% indeed.

Or clients with a WordPress theme jam packed with Lorem Ipsum, and stock photos.  Not to mention on their live URL, causing SEO issues.

90%?  Suurrrreeee…

What people don’t realize is that software is never 100%.  You’ll never make it to 100%.  No software that I know of was released at version 1 and has never changed.  It’s constantly being updated.  Tweaked, fixed, broken, you name it.  What owners of websites/web applications need to realize is that your project is an ongoing deal that will need constant attention, updates, etc.  Things change.  Business relationships, sources of data, needs of the business.  As business changes, so will your site/application.

I used to think I could sell someone a site/application, shake hands at the end of the project and we both walk away happy.  After 10+ years of development I’ve learned a few things.  One of those things is that you become personally invested in a project for the life of the project.   I have some software applications 3-5+ years old, still chugging along.  Written with horribly designed, non object-orientated code, but running.

I now know every website/web application I touch has the potential to stick with me for years.  The client could potentially use it for years.  It makes you think twice when you write code.  You want the system to make sense to the “next guy”.  Sometimes that “next guy” is future you.  I’m sure future programmer me, would fire current me because I’ll learn more, change my ways, adapt to ever changing technologies.

I also learned that there is no 100%.  You can be stable for some time, days, weeks, months, years, but there will be some need for attention in the future.  We know consider all of our projects 90% complete, and we plan to work perceptually on it.  Knowing that nothing can ever be 100% done in web.

Tired Of “Hiding”

I realized something recently.  Throughout my “internet lifetime” I have used a ton of unique usernames.  They usually are related to the person I am at the time I make them, but that person changes.  I think back to all the times I answered questions on forums, or expressed my opinions.  All those people I helped, all that information I left I the internet, lost.

I think it’s time we own up to who we are.  Why do we choose to remain anonymous on the internet?  Honestly, what benefit does it provide?  I’d rather leave my legacy and have people know who the person behind the moniker is.  I’ve begun changing all of my accounts to use my real name.  Reddit, XBOX Live, WordPress, my domain name.  Everything.  This way, good or bad, the world can always know my stance on issues, or know who helped them.