Designing a Low-Code CRUD framework

Nowadays programmers write source code for inserting, editing and deleting records of a relational table. The majority of commercial relational databases include a specific management tool that offers such possibilities and most database programmers take this ability as granted. When it comes to real life applications, programmers use Object Oriented (OO) paradigm to build user friendly windows/screens/forms for database operations. The current work shows a different approach using a Low-code CRUD (Create, Read, Update, Delete) framework. Views and guidelines of how to design a Low-code CRUD framework will be detailed. “Low-code” motivation is due to the fact that the new framework will provide the ability to use less code in order to build fast and efficient complex applications. It will be up to the reader to envision a specific framework.

Rancangan Catu Daya Cadangan SRAM Pada Z80 Trainer

Z80 Trainer banyak digunakan dalam praktikum maupun alat bantu peraga terkait pembelajaran mikroprosesor. Dalam penggunaannya, Z80 Trainer menggunakan keypad untuk menulis kode sumber secara manual dan selanjutnya disimpan dalam memori secara volatile. Masalah yang sering terjadi adalah putusnya pasokan daya ke Z80 Trainer sehingga program yang telah ditulis tidak tersimpan dan harus ditulis kembali. Penelitian ini ditujukan untuk merancang dan mengontrol catu daya cadangan untuk SRAM di Z80 Trainer menggunakan baterai, yang mampu mendeteksi terputusnya suplai daya dari tegangan listrik PLN untuk memastikan bahwa data dan program yang telah ditulis dan tersimpan di memori tidak terhapus. Metode yang digunakan dalam penelitian ini adalah metode eksperimen dan perancangan alat yang dilaksanakan dilaboratorium. Penelitian ini telah menghasilkan alat yang dapat mengontrol catu daya cadangan berasal dari baterai melalui rangkaian switching control unit untuk SRAM di Z80 Trainer. Hasil pengujian unjuk kerja mendapati bahwa alat yang telah dibuat dapat mengontrol atau mengatur catu daya di SRAM disaat catu daya utama PLN terputus selama kurang lebih 26 hari dengan memakai baterai Li-Ion tipe 18650 berkapasitas 3000 mAh. Pengujian lama waktu penggunaan alat d kondisi normal menggunakan catu daya cadangan mendapatkan hasil sekitar ±20 jam.Z80 Trainer is widely used in practicum and teaching aids related to microprocessor learning. In use, the Z80 Trainer uses a keypad to write source code manually and then stored in volatile memory. The problem that often occurs is that the power supply to the Z80 Trainer is cut off so that the written program is not saved and has to be rewritten. This research is designed to build and control a backup power supply for SRAM on the Z80 Trainer using a battery, which can meet the power supply cut off from the PLN mains voltage to ensure that data and programs that have been written and stored in memory are not deleted. The method used in this research is the experimental method and the design of the tools carried out in the laboratory. This research has produced a tool that can control the backup power supply coming from the battery via a circuit of the switching control unit for the SRAM on the Z80 Trainer. The test results prove that the tool that has been made can control or build power in SRAM when the main power supply is cut off for less than 26 days using a Li-Ion battery type 18650 with a capacity of 3000 mAh. Testing the length of time to use the tool under normal conditions using a backup power supply to get the result of about ± 20 hours.

Towards computational reproducibility: researcher perspectives on the use and sharing of software

Research software, which includes both source code and executables used as part of the research process, presents a significant challenge for efforts aimed at ensuring reproducibility. In order to inform such efforts, we conducted a survey to better understand the characteristics of research software as well as how it is created, used, and shared by researchers. Based on the responses of 215 participants, representing a range of research disciplines, we found that researchers create, use, and share software in a wide variety of forms for a wide variety of purposes, including data collection, data analysis, data visualization, data cleaning and organization, and automation. More participants indicated that they use open source software than commercial software. While a relatively small number of programming languages (e.g., Python, R, JavaScript, C++, MATLAB) are used by a large number, there is a long tail of languages used by relatively few. Between-group comparisons revealed that significantly more participants from computer science write source code and create executables than participants from other disciplines. Differences between researchers from computer science and other disciplines related to the knowledge of best practices of software creation and sharing were not statistically significant. While many participants indicated that they draw a distinction between the sharing and preservation of software, related practices and perceptions were often not aligned with those of the broader scholarly communications community.

Towards computational reproducibility: researcher perspectives on the use and sharing of software

Research software, which includes both the source code and executables used as part of the research process, presents a significant challenge for efforts aimed at ensuring reproducibility. In order to inform such efforts, we conducted a survey to better understand the characteristics of research software as well as how it is created, used, and shared by researchers. Based on the responses of 215 participants, representing a range of research disciplines, we found that researchers create, use, and share software in a wide variety of forms for a wide variety of purposes, including data collection, data analysis, data visualization, data cleaning and organization, and automation. More participants indicated that they use open source software than commercial software. While a relatively small number of programming languages (e.g. Python, R, JavaScript, C++, Matlab) are used by a large number, there is a long tail of languages used by relatively few. Between group comparisons revealed that significantly more participants from computer science write source code and create executables than participants from other disciplines. Group comparisons related to knowledge of best practices related to software creation or sharing were not significant. While many participants indicated that they draw a distinction between the sharing and preservation of software, related practices and perceptions were often not aligned with those of the broader scholarly communications community.

Towards computational reproducibility: researcher perspectives on the use and sharing of software

Research software, which includes both the source code and executables used as part of the research process, presents a significant challenge for efforts aimed at ensuring reproducibility. In order to inform such efforts, we conducted a survey to better understand the characteristics of research software as well as how it is created, used, and shared by researchers. Based on the responses of 215 participants, representing a range of research disciplines, we found that researchers create, use, and share software in a wide variety of forms for a wide variety of purposes, including data collection, data analysis, data visualization, data cleaning and organization, and automation. More participants indicated that they use open source software than commercial software. While a relatively small number of programming languages (e.g. Python, R, JavaScript, C++, Matlab) are used by a large number, there is a long tail of languages used by relatively few. Between group comparisons revealed that significantly more participants from computer science write source code and create executables than participants from other disciplines. Group comparisons related to knowledge of best practices related to software creation or sharing were not significant. While many participants indicated that they draw a distinction between the sharing and preservation of software, related practices and perceptions were often not aligned with those of the broader scholarly communications community.

A INTERFACE GRÁFICA COMO LUGAR DE CONSTITUIÇÃO SUBJETIVA

Criadas a partir de uma concepção matemática e lógica de linguagem, as linguagens de programação constituem a ferramenta pela qual o universo informático é construído. Tidas como unívocas e perfeitas, com elas se escrevem os códigos fontes e se desenham as interfaces gráficas dos programas massivamente usados atualmente. As linguagens de programação, contudo, não deixam de ser linguagens que se abrem aos múltiplos sentidos e determinam posições sujeitos. Neste trabalho, tendo como base o referencial teórico da Análise de Discurso francesa, entendemos as interfaces gráficas como objetos construídos pelas linguagens de programação e, como tais, objetos de linguagem que funcionam como um lugar de constituição subjetiva e de deriva dos sentidos a partir da análise de uma interface tomada como corpus.Abstract:The programming languages have been developed taking into account a concept of logical and mathematical language which could read the reality and reproduce it in electronic systems. So, these languages constitute the tool by which the cyberspace is built. Taken as unequivocal and perfect, they are used to write source codes and to design the GUI of massively currently used programs. However, the programming languages are open to multiple meanings as well as other languages, and they even determine subject positions. In this paper, based on the theoretical framework of French Discourse Analysis, we understand graphical interfaces as objects constructed by the programming languages and, as such, objects of language that function as a place of subjective constitution and of drift of the senses. For that, we take a software interface as a corpus for our analysis.