Skip to main content

IT quality for enterprise

Usually non-IT enterprises are IT product users. It is not really possible for non-IT companies to develop all software on their own. It is also rarely possible that the developing companies hands over their source code to buyers. The restriction on both sides not necessarily decides IT companies control non-IT companies's business information.

The role a senior software developer plays in non-IT enterprises is to guarantee business information and enterprise workflow will not be affected by the changes of tools. The following examples express this concept in more practical ways.

  • If the tool changes its requirement from MSSQL to MySQL, the senior developer should make the switch happen. 
  • If the enterprise need to control the priority of user account, and the tool only provides library or receiver to the external, the senior developer need to implement the library and link it with existing account service. 
  • If the developing company is going to shutdown its service, and the enterprise already found another option, but both companies don't really work together well. The senior developer should analyze the old system, extract all existing information and parse it to new system. 
  • If there are existing products and the enterprise want to unify parts of their functionality, the senior developer should apply the control over selected products without any harm to them. 
  • With source code, the senior developer should able to add functionality the enterprise needs. 

This means the senior developer may or may not master the development of all the tools used by the enterprise, but he/she has the ability to analyze and develop cross platforms/systems. The level of IT profession might be equal or higher than that in IT companies. Regardless of ability, having the interest to work cross system is rare.

Having this kind of senior developer, the enterprise shall soon find themselves  are free from the restriction of tools. All work could be kept properly without repeating non-technical work. And they can choose the best IT strategy more freely.

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

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

docker: storage and services

Docker Volume Without going through Docker, accessing files within a Docker image is not easy. Therefore, Docker has a volume feature that allows users to specify the location on the host file system to serve as the access directory for Docker. In other words, a volume is the NFS of a Docker image. Example: Using a volume to store SQLite files. ref:  SQLite for NodeJS: https://www.sqlitetutorial.net/sqlite-nodejs/ Initialize the project. # Setup ExpressJS framework express --view=pug 240324_ejs_sqlite_docker npm init npm install express npm install sqlite3 Test: npm start Initialize docker  Since the directory already contains NodeJS, the Docker Daemon will assist in the setup. Create new docker image docker build -t atfuture7/sqlite01 . Create a folder for Docker, create a container, run it.  mkdir docker_vol docker run -p 3000:3000 -v ./docker_vol:/data --name exp_sqlite atfuture7/sqlite01 After confirming that the container can run co...
Post a Comment
Read more