Skip to main content

keeping ideas original

In the last few years, I've noticed that ideas or conjectures that I made in the past as a naive and imaginative college student have come to have substance behind them in the empirical results of various research reports in the areas that have been published since those times. I won't go over the actual items because they really aren't relevant, what is relevant and likely is that I wasn't alone in making these mental prognostications. I think that as we speak, brilliant solutions to incredibly vexing human problems are being engineered and forgotten in the minds of precocious young thinkers and in the minds of refined thinkers as well. The key difference between the two groups lies in my view in the perception of two groups that allows one to vastly out perform the other in the skill of "innovation" is self motivation or belief.

As a young college student I literally felt that there was no problem that I alone, could not solve. This belief was reinforced by the experiences I had in studying illustration, my early forays into programming as a pre teen in the early 80's and in college , the focus I placed on studying particular subjects that I found interesting. As a youth the landscape of life is barren, there is only our boundless optimism and fascination with the breadth of open questions begging to be solved. Most of us (at least here in the United States) are free of the burdens of self support thanks to the aid of our parents. Some of us even so blessed to have had the academic performance and focus to secure this support through our own energies. Free to engage the problems , youthful engineers can plunge themselves headlong into the difficulties and through dilligent exploration of the possibilities perhaps chance across novel and innovative solutions to previously open problems.

In contrast, as we move beyond the early years, we tend to saddle ourselves with the responsibilities of life. We fall in and out of love, we have children, we redirect our energies to these endeavors and necessarily are left with less ability to attack the open problems that still beckon us. This realization then fetters the mind with doubts, doubts of our ability to perform to the same level as we did in the past, doubts of our ability to keep up with the younger generation, doubts can serve as the anchor that keeps our ship from steaming forward to new explorations and discovery. The fountain of ideas that we once were is brought to a trickle and a feedback loop of self doubts in some cases , completely stops the flow. In my life I've done my best to rebel against this erosion of ideas with time by ensuring I am free of the diversions (some would say blessings but that is a matter of perspective) that would reduce my ability to solve problems with innovative and novel ideas. Rather than steep myself in family (a task I do want to engage in eventually) I steeped myself in study (of both illustration and engineering) , rather than laden myself with material burdens (home, car...etc.)

I've been quite successful living an extremely ascetic life, one that I have chosen so that I could direct my energies inward toward the problems that I deemed most important to solve. In so doing, I've realized that a second benefit to this focus is the fact that I have been in some ways oblivious to the ideas of others, now in some areas this may be a huge detriment, as being completely unaware of the progress being made in a particular area of study can lead to the world of advances passing you by, but just the right amount of sampling of the work of others , allows the ideas to catalyze rather than pollute the innovation engine in our own minds. If we focus on every detail of what others are doing I believe we tend to pick up those ideas and may then neglect novel patterns of thought that might have led us to original creations. So, to have an eye on progress periodically allows us to shuffle the deck so to speak on the choices we will make in our designs without being stuck into a rut of following the prevailing "dogma" of ideas.

In history we see that many of the most innovative achievements were performed by lone gunmen characters who seemed at first , secluded away oblivious of the workings of the world. Einstein serves as the archetypal example of such a character, but Einstein wasn't a lone gunman, he sought and maintained correspondences with many influential individuals in his work, he was able to bounce his ideas off those people and use the feedback to continue his innovations without being polluted by a mass of dogma that might have derailed his train into the unknown and extraordinary concepts of relativity, brownian motion, photo electric effect among other great realizations. Einstein kept his ideas original by NOT mingling too much in the world of scientific dogmas that said, time must be absolute, that space must have an "ether". He delved into the work and let it reveal the truths to him and objectively accepted the results. Software engineering is in many respects the same type of endeavor, it is possible to get lost in a sea of dogma, as we embrace this or that programming methodology, as we are introduced to this or that "pattern", these templates allow us to solve certain types of problems but as we all know, all problems are unique and just as a tailors suit patterns are not amenable to designing all sizes of to is it that the constantly evolving dogma of software engineering technique (one which has a definite industry behind it in the form of lectures, books and videos by the way) are not applicable to all problems. We must be facile enough with our ideas that we can engineer novel solutions on the fly without being restricted by the patterns of dogma. In doing this we ensure that we can busy ourselves with solutions that not only solve the problem, but solve it in a tailor made fashion that ensures extreme and complete long term efficiency. The theme of taking time to properly design solutions and avoiding the pollution of foreign dogma is one I've come across a great deal in my life, so far it has been very beneficial and has kept me from falling into a rut of self doubt, at least that is my perception. ;)

jist: be so busy with your own innovations that you have little time to read about the dogma of others. Time will reveal the value of the path you have taken.


Popular posts from this blog

Highly targeted Cpg vaccine immunotherapy for a range of cancer


This will surely go down as a seminal advance in cancer therapy. It reads like magic:

So this new approach looks for the specific proteins that are associated with a given tumors resistance to attack by the body's T cells, it then adjusts those T cells to be hyper sensitive to the specific oncogenic proteins targeted. These cells become essentially The Terminator​ T cells in the specific tumor AND have the multiplied effect of traveling along the immune pathway of spreading that the cancer many have metastasized. This is huge squared because it means you can essentially use targeting one tumor to identify and eliminate distal tumors that you many not even realize exist.

This allows the therapy for treating cancer to, for the first time; end the "wack a mole" problem that has frustrated traditional shot gun methods of treatment involving radiation and chemotherapy ...which by their nature unfortunately damage parts of the body that are not cancer laden but …

Engineers versus Programmers

I have found as more non formally trained people enter the coding space, the quality of code that results varies in an interesting way.

The formalities of learning to code in a structured course at University involve often strong focus on "correctness" and efficiency in the form of big O representations for the algorithms created.

Much less focus tends to be placed on what I'll call practical programming, which is the type of code that engineers (note I didn't use "programmers" on purpose) must learn to write.

Programmers are what Universities create, students that can take a defined development environment and within in write an algorithm for computing some sequence or traversing a tree or encoding and decoding a string. Efficiency and invariant rules are guiding development missions. Execution time for creating the solution is often a week or more depending on the professor and their style of teaching code and giving out problems. This type of coding is devo…

AgilEntity Architecture: Action Oriented Workflow

Permissions, fine grained versus management headache
The usual method for determining which users can perform a given function on a given object in a managed system, employs providing those Users with specific access rights via the use of permissions. Often these permissions are also able to be granted to collections called Groups, to which Users are added. The combination of Permissions and Groups provides the ability to provide as atomic a dissemination of rights across the User space as possible. However, this granularity comes at the price of reduced efficiency for managing the created permissions and more importantly the Groups that collect Users designated to perform sets of actions. Essentially the Groups serve as access control lists in many systems, which for the variable and often changing environment of business applications means a need to constantly update the ACL’s (groups) in order to add or remove individuals based on their ability to perform certain actions. Also, the…