Software Values
I am a design person among other things. Design has played an important role in my life, so much so that it has become a part of my identity. This is my first blog. This blog is a means of understanding the landscape of technology, the individual, software and observations. That would be a general description, do stick around to see it develop.
Values
Values instill a goal of action to perform. The realist by the endless winters of death has fashioned new methods of action. The right way is the best way in any condition is the best foot forward.
What values do you consider important in developing your software? How to put into practice design-to-development principles in software development?
Tech stacks
Software frameworks differ based on the purposes of the software to define the tech stacks. What programming languages would be best suited for the software you want to develop? What are the best options for low complexity when you begin?
Is there a tech stack that would be ideal for the software? How do you make it accessible for yourself and how complex is the approach? The abstraction of values in the highest is transparent.
Minimalism
When you're down to nothing, and you are less than one the only real way to cut across is to bear down the bloated wasteful. The architecture is the overview of a new clear light.
Build what’s necessary and control complexity in the early stages of development to provide space for long-term planning. Backend architecture, prospecting to lower complexity is complexity reduction while maintaining the functionality of the previous.
Software deployment can yield unexpected errors in relation to database and the backend.What are the factors of usability, control and convenience from design to development that define the values of the software to maintain most of the architecture including the frontend, when the backend can be complex.
Scaling back on complexity through high refactoring can make the deployment of the software a better experience.
The value system of development and deployment for control over complexity can include lower learning curve, accessiblity, flexible or high modularity. Therefore minimalism for lowering complexity should be considered.
Easy to maintain, extend, and scale - Simplicity to complexity
As a software is designed through the fulfilment of business outcomes in order to meet the needs of the consumer, it begins from a initial design prototype application in simplicity before expanding from simplicity to complexity from interactions with data and user interactions from the commercial goal.
Design for Safety - Feedback, instructional, errors, accessible, fail safe
An instructional interface such as dashboard for the user should be designed for safety in dangerous terrains of use cases like space exploration.
The design should account for errors and control over the unpredictable. Instructional feedback clear as day for the user. The mappings between action and intent should account for all known functionalities including fail safes.
Feedback from the system must be clear, immediate, deliberate to provide maximum control and clarity to the user.
Autonomy - Avoid vendor lock-in
Companies appear as striking balloons before they pop into closure leaving behind products or frameworks. Abandoned proprietary tools can leave you with unpatched issues thus avoiding vendor lock-in must be considered to maintain autonomy.
Modular - Modularity, Flexible, Clean
Stability when one variable affects the other on the edge of a bright day requires modular, reactive, and a clean approach that should be flexible to upgrade.
Readable, flexible, and easy to audit - Control Over Convenience
Open source software remains one of the strongest choices in most modern development scenarios.Transparency and auditability reviews the actual code, spot potential backdoors, vulnerabilities critical for AI models, libraries, infrastructure tools, and handling data. Feedback reviews contribute to the development of security practices and adoption across industries.
Open source licenses by the definition allows commercial use, modification, distribution, and private use without discrimination against fields of endeavor. Consider open source but review the license for commercial-use and distribution clauses before shipping products.
Open source projects often receive fixes, updates, and contributions from organizations.
Interfaces responsive and accessible - Good usability is accessible
The interface is a relay between the user and the technology. The input layer serves as the point of data between the user and the specific feature of the output layer where decisions are made.
Interfaces must be responsive and accessible for good usability. Good usability is accessible and accessibility is good usability. Consumerism is good usability.
Security - Effective, Secure and Minimal
What programming language would be best for the backend?
If it has a high degree of complexity does it make up for efficiency and functionality? Is a long string of sequence more effective than a shorter sequence? E.g neural network, DNA
Can security be effective, secure and minimal? Are there other things you have considered for security that is minimal and effective like compactilization? Information is modular.
