Monday, January 17, 2011

Partial Improvements

I have found a technique of problem solving using minimal financial costs bearing in mind that labour, materials and time are constraints and variables.  I have called it "partial improvements", and has worked quite well for me with project management work and self-reliant practices.  The way you approach the site is that you can provide some scientific principles and observations to your 24/7 day of survival.  I haven't bothered referencing anything because this has come from my "own" experiences and experiments.


Sometime the task at hand can involve many tasks and the idea of juggling all the ideas, work and time in programming can be complex when HR may not have the resources to complete the task, or may have in the past had problems with testing and implementing new systems and applications.  In some other areas your training needs to include physical exercise and regular journalling especially dreams and ideas as they pop into your head within your initial draft.


Partial Improvement goes along the lines that within the humanoid framework a large task can be separated into smaller sub-task each becoming new projects in themselves.  Quite a great deal of time is needed to collaborate on the work and the communication that exists within the team environment if there is greater than one player on the team.  Also when you as a humanoid will approach a task or project is to partially all sum up the rates of change of all aspects of your consciousness including memory, health, education, experience, success rate and speed of competency, efficiency.


Thus would be some sort of equation for mental health and potential value, summing up physical and mental aspects together rather than excluding the relativity of the two sub components.


Of course version control can make us need to solve a bug, twice, because of version control or dual file access database locking practices are needed such as pessemistic and exclusive access.  This is easily seen with M Access Dbase solutions and a "stamp of time" occurs.  This stamp is basically a function call to get the time from the source, the source we only discover using help to lookup the function documentation description.  All the unix and linux guys will know this as man for shell functions or procedures.


Using partial improvement you never ever run out of things to do, however as a perfectionist you can get to the stage where your app is ready to be documented and you would like to move on rather non creatively and look at performance, speed, reliability, exception handling, garbage collection and other synonyms for the programming world.


Essentially what could happen by designing carefully designed inputs test your app for speed together with other things like error handling and essentially doing nothing until it comes back to you.


Carefully understood communication is essential in all cases , making the system seem like a pipe dream.  Understanding whether you are sitting in front of a computer that reflects your knowledge and understanding and potential value moves along to partial improvements leading to complete solution offers.  These offers are like tenders for a final version, each team competing with others to understand the clients, needs wants and attitude.


Essentially speaking robot is something that can keep you glued to your chair, take a break every 20 minutes and walk away from the computer and also focus your eyes on distant objects whilst seated.


Read and learn new languages and methods and mental processes but realise to talk computer is basically what it is and nothing you can do can change it.


Of course understanding magnetism with processing can essentially drive a publisher mad having checked and triple checked a solution and then find after some time a "change", the developer suspects no one as one does and therefore needs to correct the change to comply with the design and architecture limitations and functionality.  Really the answer is the 1 turned to a 0 in the binary string of boolean or two separate values, this can even involve great many pages of memory, the thought of electrons comes to mind.


Constantly reliability of signal processing and data packet transmissions will always be subject to constant review and querying, together with understand the role you play as tester or consultant on the task at hand.  For me this has meant, think smart not competitively, do not see yourself superior or inferior, just be a human being and breath, relax and feel the earth and do nothing extra, this reference to Tao Tai Chi breathing visualisations anxiety needs to be controlled or "managed" and the breath becomes your tool for addressing the scan you place on yourself.  This then moves you into the world of diseases and medicines and also the ultimate question of "truth", if such an idea exists and we have to power to improve something, is it an act with your own sanity as to whether you drop the bundle and say enough.  Whether you have succeeded or failed depends on the test itself together with what you ate for breakfast or had blasted at you via the television.





1 comment:

  1. I can refer to Discovery channels Dirty Jobs which says that "Teamwork is for Robots", and that bringing passion with you to each job is important. Sometimes working as a one team can avoid communication issues altogether and allow for some autonomy and reliance on defined simple small code snippets as opposed to all sorts of five headed monsters and version control.. Of course all the importance of server side implementation involved collaboration and language development with say .NET and php etc scripted results and storage and load stress testing and server services, for me it seems that you work with what you do have rather than what you don't have, of course complete administrative control can make your web server .NET or whatever capable and the security and site mapping automation is a nice "feature", whether you program C or C#, Java, Ruby etc or incorporate your ideas of imitation by example in treading water with your application development, means that language can of course have API links to DBMS systems for whatever your clients target system and virtual machine will operate generally subject to database auditing and logging, but more importantly the robustness and documentation to any language that may or may not be available. I agree partial improvements may in some cases be a one man team on a delegated component, control or class and hence requires a great deal of complexity in terms of the evolved language and its sustainability and need for code re-use.

    In the end what works, does work and really can it stand it's virtual service life and keep up with clustered systems that evolve as a result of opportunities, in the end this slowness can be rather emotional with a deadline, in some ways slowing down can make it more remember-able and less fast and forgetful.

    ReplyDelete