I have obviously not written in a fair amount of time. The only explanation I’ve got, is this page… https://github.com/mlantz. I have been crazy busy with work, but I assure you, it will be worth the wait. I’ve got some very interesting things to talk about this year. Patience though, for now, is key. Thanks.
Observe, Evaluate, Iterate
A journal by Matt Lantz
Alone and ghostly lit,
I sip my liquid black.
An Eerily blue hue,
is all I have left.
I have been hard at work for the past few weeks and totally fallen off the earth of blog writing, for that I apologize. It’s been a whirlwind of change in my life, thoughts of moving to a new city in the next year or so and building a business. I have been contemplating numerous ideas for small projects and what I wish to focus on in my career and hobbies moving forward. I’ve been seeking out new people to work with and exploring new technologies the same as always. But where do I go from here? That seems to be the question that keeps repeating in my mind. I keep contemplating what can I bring forward and how do I better the world around me?
Contrary to the popular phrases ‘future proof’ etc it is my opinion that all code must die. Now what do I mean when I say all code must die? All code is out of date the minute it is written, because of that all code ideas though good at the moment are unable to predict the future and thusly cannot stay relevant for very long. Businesses change and grow with time, and code that may have fit the part in 2004 does not service the company in 2014. You cannot expect a hack job on a WordPress site to maintain its value. Code itself degrades in value from day one of writing, therefore what you had written in 2004 is likely dead by 2008. Lets look at some more details on why.
I’m forced to keep this entry short, since I haven’t been getting enough sleep lately. I’d like to pose a theory, and since I’ve never done any schooling on the concept of infinite I have very little to base this idea’s originality on. But, I thought lets try this out.
There is a moment in the Lord of the Rings films and books where Bilbo claims there is nothing wrong with having a simple life. This is of course after we see a barrage of imagery of graceful animals walking about, people gardening, and doing woodworking etc. There is a serious misconception of what it means to maintain a simple life. I often see people discuss the idea of living in the country being simple. The notion that because you’re getting away from the complexities of the city your own personal life will be more simplistic. It has been my experience that a life is as complex as you want it to be regardless of what your environment is.
I may sound like a cynic but as I see it movies have been on a steady decline in substance for a while. It seems like we have lost the movies focused solely on great writing, with a few big name actors in them. We get them occasionally like we did with ‘The Big Short” and a few others, but it seems to be that whole entertainment industry has moved to large scale films with bland predictable story lines recycling old comic book heroes with popular actors and actresses playing their roles offering minute layers to characters that have been well established for a long time.
I was asked recently why I write open source software that could replace me. Personally I do not think I can be replaced by open source code. Even when I contemplate the future of open source coupled with artificial intelligence I personally think that as long as I’m always pushing myself to learn new things I can remain useful in evolving economy. However, why do I write code that does some of my work for me? To put it simply its because I don’t want to have to do those things again. As a developer, and for that matter, as a person who wants to grow, I’m a fan of learning new things and letting go of stuff I no longer want to do. If I can build a CMS which handles all my basic content operations then I have the freedom to work on machine learning algorithms etc.
I’ve decided to go a little philosophical with this post. I want to talk about an idea, not too sure if I’m coining it or if thats been done, but here it is: short term evolution (STE). Now let’s get to what I mean by using this term. I want to explore at this in the field of business. I have worked with many companies in my career, and there have been a few which have stood out to me, as doing things in a weird way. As I see it they are too focused on short term evolutionary changes, rather than entertaining long term evolutionary changes. Now this starts to spell out what I mean by STE. Short term evolution is a process in which a group makes shallow short term changes to improve their business, believing that these changes will result in a long term change. This is contrary to long term evolutionary changes, which are small in nature but address deeper foundational issues of a business which will via percolating upstream result in long term changes.
Why build a framework versus a ‘seed app’?
I originally did start to write “Laravel” as a seed application for CodeIgniter; however, I found I couldn’t accomplish it without hacking the core components of CodeIgniter, so I just decided to start writing my own framework. At the time, I was fairly new to PHP from .NET and wasn’t really aware it was widely considered “taboo” to seriously write your own framework. 🙂