Skip to main content

Experiment

'Applying technology', enterprises should take it as investment, instead of expense. This means 'taking risk'.

New IT ideas should be applied on small group first, in order to prove the validity and effectiveness.And then expanding its functionality toward full scale and taking user habits into consider. Finally, it is time to search for substitute products in IT market.

During the experiment period, enterprises could hire less experienced developers to implement expected functionality. Senior IT professionals help resolve technical boundaries. When the experiment is taken as successful and the enterprise decides to keep this model, there are two options to build it into formal and reliable structure. One is the senior developer takes over the responsibility of core structure improvement, and less skillful developers continue on customize the model to be more user friendly.

If the project is decided to be outsourced, the project manager have a practical model to negotiate with developing company, or to search for existing products. Current model is still in use until the new tool is ready. The senior developer is responsible for building bridging tools and exporting existing data to new IT product/system.

Experiment is not a waste. It proves the validity of new ideas, helps the enterprise to polish unfulfilled ideas to practical IT model, and, in fact, it prevents failed investment in unfamiliar IT products and saves money.

Labels:

Comments

Post a Comment

Popular posts from this blog

Bookmark service (MongoDB & Spring REST) -2/2

    I accidentally deleted my development VM. I got lucky having the habit of taking notes. This blog is useful. Development VM is doom to be lost. Rebuild it waste time, but having a clean slate is refreshing~. What concerns me more is my AWS free quota this month is reaching 85%. The second VM I launched but never being used might be the one to blame. (Of course, my mistake.) I terminated the wrong VM. Now I got Linux 2 built. Great, just threw away everything happened on AMI.  1st layer: Page Page class   Originally, I need to prepare getter/setter for all class properties for Spring. By using lombok, I only need to create constructors. lombok will deal with getter/setter and toString(). But there are chances to call getter/setter, but how? .......Naming convention.... Capitalize the 1st character with the prefix get/set.  Annotation @Data was used on this class.  Repository class Spring Docs: Repository https://docs.spring.io/spring-data/mongodb/docs/3....
1 comment
Read more

Comments for my Server/Client Web API samples

        Finally, I finished the comments for python/07 and 09 projects. I almost forgot to put the date on source code which is used to note how long it took me. Not precisely in hours….. I didn’t include source code in my previous post. If choosing code-section for this post…… maybe I want to mark out my comment….. (Really?!)          Once my work was developing websites for enterprises, including ERP, CRM or content sites. The sustainability of network and security are important issues. There are 2 methods for HTML Form submission: GET and POST. Submit via POST is secure, compared to GET which piles parameters on URL. RESTful API is mainly using GET.         Yup, even if you have a certification key, if you put the value on the URL, it is visible data. When writing socket-communication, client-server sockets are a pair; both follow the agreement on commands and structures; and there are countless ports for usa...
Post a Comment
Read more

Guide to Preserving HuggingFace Models in Google Colab Environments

Conclusion:  Step 1:  find the model path: ls ~/.cache  Step 2:  Copy the entire folder to Google Drive:  Step 3:  Set model path to the subfolder under snapshot: My Story: I initially began exploring Generative AI (GAI) and Google Colab through Stable Diffusion. In the past, as I mainly wrote server services and console applications, I was less familiar with data science modes like R and Jupyter that can maintain a paused state. I didn't quite understand the heavy burden on Colab of creating a temporary Stable Diffusion WebUI with .ipynb, as suggested by popular guides. I just found it troublesome that connections often took a long time and then dropped, requiring a restart. Recently, while testing new versions of the Stable Diffusion model, and facing challenges due to Colab's policies making various versions of WebUI difficult to run successfully, I started researching how to write my own test programs in Colab. Eventually, I understood that Colab is ess...
Post a Comment
Read more