We are looking for talented developers to create an operating system from scratch that will surpass Linux and Windows! If you have experience and a desire to participate in an ambitious project, join our team!

PAYMENT FOR WORK:

Due to the lack of a large budget, payment will come in a different form. Project participants will receive lifetime free access to the T-Gen neural network, which predicts asset prices. The neural network itself costs more than $8999 per month. Additionally, participants can request to receive a percentage of the total profits from the project if they wish.

REQUIREMENTS FOR ALL:

Age: 18 and older
Experience with programming languages C and Assembly (NASM)
Ability to work in a team
Willingness to complete the project within 5 months (by 31.12.2024)
Deep understanding of operating systems and their implementation

WORKING SCHEDULE:

You will work from home. You will work all day; you should show great interest in this work and may even work at night. Take breaks when necessary; if you take a break, you must inform us. On average, you will need to write 500 lines of code each day. But don’t forget to rest; you are highly motivated, but without rest, you may suffer later, and you don’t want to let the team down.

TEAM:

You will form a large team, and you will communicate with them on the Discord server created for our team. I hope you understand how important teamwork skills are. Your team will consist of:

System Developers: 150
QA Engineers: 75
Interface Developers: 50
Driver Developers: 75
Optimization Specialists: 50
Security Specialists: 50
System Architects: 50
And one Director.
Places are limited, but new people may join throughout the project. We only accept professionals in their field.

MORE ABOUT PAYMENT FOR YOUR WORK:

As mentioned before, we will not pay you monthly for your work. If the project is completed on time, you will receive lifetime free access to the T-Gen* neural network. This neural network predicts the closing price of an asset. This means that if you ask it about any stock, it will perform extensive calculations and accurately predict where the price will go. To profit from this, you must open a trade with the selected asset at the right interval and in the correct direction. In my experience, it has never been wrong. By the way, this neural network is developed by entirely different developers; we have no relation to them. Please review their policy before using their product.

Additionally, if you wish, after the successful release of the project, you can request a percentage of the profits. The percentage will also depend on how well you performed.

*At the moment, the company can be contacted by mail t2gen@outlook.com (The site stopped working after an attempted hacker attack).

WHAT AWAITS YOU AT WORK:

Prepare to work from home in your cozy space, communicate with the team via Discord, and solve any problems you encounter. We will try to ensure that everyone behaves appropriately. Your colleagues, like you, should be kind to all. Everyone will keep documentation of all code work right in the code. You will be required to submit a weekly report on your completed work. We will encourage the team. Don’t constantly think about the reward; upon timely completion of the project, you will definitely receive it. You will also receive plenty of guidance on solving various problems. Be ready to work with GNU C Compiler, NASM assembly language, Make, and version control Git. Be prepared to communicate with your team, share files, and even relax together in the evenings. Just imagine how our system will be featured on television; perhaps someone will see on TV something they contributed to for the first time. The future is ours.

WHAT KNOWLEDGE IS REQUIRED:

For System Developers:

• Proficiency in the GNU C programming language.
• Expertise in NASM assembly language.
• Expertise in automation with Make.
• Ability to maintain documentation of all code work within the code itself.
• Experience with version control Git.
• Deep understanding of operating systems and their implementation.
• Teamwork skills.
• Knowledge of the English language.
• Familiarity with Discord.

For QA Engineers:

• Experience with manual testing.
• Knowledge of C for writing tests.
• Ability to use Make for build automation.
• Deep understanding of operating systems and how they work.
• Experience in developing automated tests in C.
• Familiarity with testing tools.
• Knowledge of GDB for debugging tests.
• Knowledge of the English language.
• Teamwork skills.
• Familiarity with Discord.

For Interface Developers:

• Experience in designing user interfaces for operating systems.
• Knowledge of UX/UI design principles and their application in interface development.
• Proficiency with design and prototyping tools (Figma, Adobe XD, Sketch).
• Understanding user interactions with operating systems.
• Ability to create intuitive and user-friendly interfaces.
• Teamwork skills and ability for constructive criticism.
• Knowledge of the English language.
• Familiarity with Discord. Join our team and contribute to creating a truly unique operating system interface!

For Driver Developers:

• Experience in developing drivers for various operating systems.
• In-depth knowledge of operating system architecture and hardware interaction.
• Proficiency in C and NASM assembly language.
• Experience with device interaction protocols.
• Familiarity with tools for driver debugging.
• Teamwork skills and readiness to collaborate with other developers.
• Knowledge of the English language.
• Familiarity with Discord.

For Optimization Specialists:

• Experience in profiling application and system performance.
• Ability to optimize code for speed and resource efficiency.
• Knowledge of modern optimization methods (e.g., algorithms, data structures).
• Experience with C and NASM assembly language.
• Teamwork skills and willingness to share knowledge.
• Knowledge of the English language.
• Familiarity with Discord.

For Security Specialists:

• Experience in the field of cybersecurity.
• Knowledge of designing secure systems and applications.
• Ability to audit code for vulnerabilities.
• Familiarity with modern security tools.
• Understanding of current threats to software and operating systems.
• Teamwork skills and willingness to share experience.
• Knowledge of the English language.
• Familiarity with Discord.

For System Architects:

• Experience in designing complex software systems.
• Deep understanding of architectural styles and design patterns.
• Ability to manage projects and collaborate with various teams.
• Knowledge of programming languages (C, assembly) and operating system principles.
• Experience with version control (Git).
• Knowledge of the English language.
• Familiarity with Discord. ________________________________________________ HOW TO APPLY FOR PARTICIPATION:

Write to sayonaraproject.os@gmail.com, answering the questions related to your specialty as well as general questions for everyone:

General Questions about Experience and Skills:

1. What is your experience with programming languages C and Assembly (NASM)?
2. Can you provide examples of projects where you worked on operating systems?
3. How would you rate your programming skills on a scale from 1 to 10?
4. Do you have experience working in a team on large projects? How did you resolve conflicts within the team?
5. How do you plan to prioritize your work to complete the project on time?
6. How do you handle working under tight deadlines?
7. Have you had previous experience working with distributed teams? How did you establish communication?
8. What task planning method do you prefer to use during development?
9. How do you generate your ideas for new features?
10. How do you keep your knowledge up to date?

Questions for System Developers:

1. How do you automate the build process using Make?
2. What are your approaches to maintaining documentation for code?
3. What can you say about the principles of developing multithreaded applications?
4. How do you test the functionality of your code?
5. How do you approach debugging code? What tools do you use?
6. What is your experience with system calls in Linux?
7. Do you have experience optimizing kernel modules?
8. How do you handle compatibility issues across different hardware platforms?
9. What technologies do you use for state management in multithreaded environments?
10. How well do you know working with Linux system utilities?

Questions for QA Engineers:

1. How do you approach manual testing? Can you provide examples of tests you wrote in C?
2. What are your preferences for tools for test automation and debugging?
3. How do you determine critical testing paths in a project?
4. What do you consider best practices in integration testing?
5. How do you approach reporting test results? What metrics do you use?
6. How do you track bugs and manage their lifecycle?
7. Do you have experience working with automated tests? If so, what approaches did you use?
8. What is your experience with performance monitoring tools?
9. How do you confirm that a software product meets the requirements?
10. How do you organize the testing process when new functionalities arise in the later stages of development?

Questions for Interface Developers:

1. What UX/UI design principles do you consider most important when developing interfaces?
2. Tell us about your experience designing interfaces for operating systems.
3. How do you test interfaces for usability and intuitiveness?
4. What methods do you use for prototyping and designing interfaces?
5. How do you work with user feedback when creating interfaces?
6. What tools do you prefer for interface design and why?
7. How do you address accessibility in interfaces for different categories of users?
8. What is your approach to mobile responsiveness in interfaces?
9. How do you integrate visual elements with functionality?
10. How do you handle criticism of your design, and what improvements do you usually implement?

Questions for Driver Developers:

1. What is your experience in driver development and hardware interaction?
2. How do you debug drivers? What tools do you use?
3. How do you work with interaction protocols between devices?
4. How do you test drivers for stability and performance?
5. What design patterns do you apply in driver development?
6. How do you manage driver versions?
7. How do you resolve compatibility issues with various devices?
8. What is your understanding of the driver certification process?
9. How do you keep your documentation up to date?
10. How do you ensure a high level of security in driver development?

Questions for Optimization Specialists:

1. What optimization methods do you apply to improve performance?
2. Tell us about your experience with application and system performance profiling.
3. How do you identify bottlenecks in code performance?
4. What tools do you use for code analysis and optimization?
5. How do you approach algorithm optimization?
6. How do you work with multithreading for performance enhancement?
7. How does your experience with C and NASM help you in optimization?
8. How do you factor performance into the system design stage?
9. Tell us about your experience with caching and its optimization.
10. What is your approach to documenting your optimization solutions?

Questions for Security Specialists:

1. What are your methods for auditing code for vulnerabilities?
2. What modern security tools do you use in your work?
3. How do you handle security incidents?
4. What data encryption methods do you prefer to use?
5. How do you work on preventing network-level attacks?
6. How do you assess security risks in projects at early stages of development?
7. How do you ensure security when working with open-source code?
8. What are your recommendations for creating secure systems and applications?
9. How do you educate your team on security issues in the code?
10. How do you stay updated with new vulnerabilities and threats?

Questions for System Architects:

1. How do you approach designing complex software systems?
2. What is your opinion on architectural styles and design patterns in the context of operating systems?
3. How do you manage projects and interact with different teams?
4. What methods do you use to evaluate architecture for performance?
5. How do you deal with technical debt in your projects?
6. How do you use system modeling tools in your work?
7. How do you address various system requirements such as scalability and fault tolerance?
8. How do you align architectural decisions with other team members?
9. How do you select technologies for your project?
10. What are your plans for maintaining architecture in the future?

Questions about Teamwork:

1. How do you set up communication with the team on Discord for effective work?
2. How do you train and support less experienced team members?
3. How do you document collaborative work and your team's achievements?
4. What are your practices for maintaining team morale?
5. How do you approach conflict resolution within the team?
6. How will your team handle timely updates and improvements to code?
7. How often do you hold meetings and discussions within the team?
8. How do you assess the success of collaboration within the team?
9. How do you give and receive feedback among colleagues?
10. How do you motivate your team to achieve common goals?

Questions about Motivation and Expectations:

1. Why do you want to work on creating a new operating system?
2. How do you see your role in the team and the project?
3. What are your expectations for participating in a project like ours?
4. How do you plan to use your experience after the project is completed?
5. How do you set your career goals for the next 5 years?
6. How do you deal with failures in projects?
7. What do you enjoy most about your current profession?
8. What aspects of your work bring you the most satisfaction?
9. How do you plan to develop your skills and career in development?
10. How do you motivate yourself to achieve high performance at work? ________________________________________________ CODING STANDARDS

In your code, you must adhere to the following standards:

Function Line Count:
Functions should contain no more than 40 lines of code. This improves readability and maintainability, making the code more understandable for other developers.

Structure and Formatting:
Code should be clearly formatted and structured. This includes the use of indentation, spacing, and consistency in the naming of variables, functions, and classes.

Naming:
Variables and functions should be named in a way that their purpose and functionality are obvious. Clear and informative names should be used.

Code Documentation:
Each module and function should be documented. This includes descriptions of input parameters, output data, and overall functionality.

Error Handling:
Code should include error handling mechanisms to enhance the application's robustness and reliability.

Testing:
The programming code should be accompanied by unit tests to ensure functionality and detect errors at an early stage of development.

Avoiding Code Duplication:
The programming code should minimize duplication. If the same logic is applied in multiple places, it should be extracted into a separate function or module.

Version Control:
The use of version control systems is mandatory to track changes in the code and enable quick rollback in case of errors.

Adhering to these standards will be highly beneficial.

WHAT IS REVOLUTIONARY:

You will develop a system that supports .exe and .apk formats.
You will create your own bootloader, similar to GRUB.
You will write a hybrid kernel.

Operating System Development Plan

I. Preparation Stage (1 month)

• Team Assembly and Role Distribution

  • Define team membership.
  • Appoint leaders for each subgroup: system developers, QA, interfaces, drivers, optimization, security, architecture.

• Requirement and Specification Definition

  • Gather functional and non-functional requirements.
  • Create a technical specification (TS) for the OS.

• Research and Analysis of Existing Solutions

  • Analyze key components used in Linux and Windows.
  • Identify unique features for the new solution.

• Architecture Planning

  • Create architectural diagrams.
  • Define interactions between components.

• Creation of Repository and General Documentation

  • Set up Git for version control.
  • Create the main project documentation.

II. Kernel Development (2 months)

• Design and Development of Hybrid Kernel

  • Create a kernel prototype.
  • Implement essential system calls and process management.

• Bootloader Development

  • Explore bootloader options (similar to GRUB).
  • Implement basic OS loading functionality.

• Memory Management Module Creation

  • Develop mechanisms for managing virtual and physical memory.

• Kernel Testing

  • Conduct unit testing of the kernel.
  • Fix identified errors.

III. Development of System Components (1 month)

• Creation of System Drivers

  • Implement drivers for key devices.
  • Test interaction with hardware.

• Development of System Utilities

  • Create basic utilities for system management (e.g., file system, process management).

• GUI Interface Development

  • Create a basic user interface.
  • Implement core functions for interaction with the OS.

IV. Optimization and Testing (1 month)

• Performance Optimization

  • Conduct performance profiling.
  • Optimize code at the driver and system call levels.

• Functional Testing

  • Perform integration testing of all components.
  • Test performance and stability.

• Error Correction

  • Address all identified errors and defects.

V. Preparation for Release (1 month)

• Final Testing

  • Conduct system testing with the QA team.
  • Ensure compliance with all requirements.

• Documentation

  • Create a complete user manual.
  • Prepare technical documentation.

• Release Preparation

  • Create release versions of the system.
  • Set up the system for user feedback collection.

VI. Release and Post-Release Support

• System Release

  • Official launch of the OS and announcement of the release.

• Feedback and Support

  • Gather user feedback and report errors.
  • Prepare updates based on collected data. ________________________________________________ If you are writing to us via email, you agree to the following terms:

Cooperation Agreement
Date: 12.09.2024

Place of Drafting: Washington, USA

Terms of Cooperation
By participating in the project, you agree to the following terms:

Subject of the Agreement
The participants agree to cooperate in developing a new operating system from scratch that surpasses existing solutions such as Linux and Windows.

Participants' Responsibilities

• Provide necessary resources and support for the project.
• Establish and maintain communication through the Discord server.
• Participate in the development of the operating system by performing tasks per requirements.
• Provide a weekly report on completed work.
• Actively engage in teamwork and discussions.

Rewards and Compensation
In lieu of monetary compensation, participants will receive:

• Free access to the T-Gen neural network.
• The possibility of receiving a percentage of the project's profits at discretion.

Duration
This agreement comes into effect upon the participants' consent and remains valid until the project's completion (until 31.12.2024).

Confidentiality
Participants agree to keep all confidential information obtained during the collaboration secret.

Dispute Resolution
All disputes arising from this agreement will be resolved through negotiations. If an agreement is not reached, the dispute will be referred for arbitration.

Final Provisions
Changes to this agreement are possible only in written form, notified to all participants. The agreement may be terminated by either party upon 3 days' prior notice.

How to Participate
If you agree to the above terms and wish to participate in the project, please send an email to sayonaraproject.os@gmail.com stating your intention to join the project.