Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
#20: Post edited
- ## General scope of this site
- Software Development Codidact is about writing software, where software is understood to include any means of specifying computer actions to be performed later. This refers to both general-purpose programming and scripting languages such as SQL and shell scripts.
- ## On-topic
- On-topic questions should be about one of the following:
- > - **Software design**, architecture, or modeling.
- > - **Software implementation**: specific programming or troubleshooting problems that include attempts to solve or debug the problem.
> - **Best practices**, as long as clear "best" criteria are provided. Examples: fastest execution, least memory use, widest tool support for a target, most beginner-friendly IDE for a certain language and operating system- > - **Software development tools**: how to install, configure, troubleshoot, and use tools specifically meant for software development (e.g. compilers, debuggers, IDEs).
- > - **software development process** and project cycles specific to the software engineering such as requirements, design, or testing.
- > - **Software life cycle management**: build configurations, version control, release, deployment, etc.
- > - **Software documentation**: how to write it or how to use tools for that purpose.
- > - **Database management**: database design, programming, or access through SQL.
- > - **Code reviews** that follow [the guidelines for code review](https://software.codidact.com/help/code-review-guide).
- > - **User Interfaces that involve some programming**: mark-up language syntax, how to set properties in RAD tools, how to use graphic libraries, algorithms related to drawing graphics, including to some extent the math and physics behind it.
- > - **Quality Assurance**: programming, scripting, software design & architecture, process, tools, testing, and more.
- ## Off-topic
- The following types of questions are off-topic:
- > - **Asking for implementations** of a certain feature or a whole homework assignment. You should include your (partially working) attempts in the post
- > - **Asking for detailed explanations of posted code**, unless the code is small, self-contained, and an attempt to understand it is also included.
- > - **Simple typos**: if the issue was caused by simple typographical errors, the question is very unlikely to be useful for future readers and may be closed.
- > - **General computer or software support** which is not connected to software development/engineering (e.g. ask for recommendations)
- > - **System, network or server administration** questions
- > - **Embedded systems programming** including microcontroller programming, hardware description languages, RTOS questions, PLC programming. Please use [Electrical Codidact](https://electrical.codidact.com/) instead.
- > - **Project management**.
- > - **Software licensing**.
- > - **UI or graphic aesthetics.** What looks best, color choices, graphic design, and similar are mostly subjective questions.
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
- ## General scope of this site
- Software Development Codidact is about writing software, where software is understood to include any means of specifying computer actions to be performed later. This refers to both general-purpose programming and scripting languages such as SQL and shell scripts.
- ## On-topic
- On-topic questions should be about one of the following:
- > - **Software design**, architecture, or modeling.
- > - **Software implementation**: specific programming or troubleshooting problems that include attempts to solve or debug the problem.
- > - **Best practices**, as long as clear "best" criteria are provided. Examples: fastest execution, least memory use, widest tool support for a target, IDE for a certain language and operating system
- > - **SEO** (search engine optimization), as long as they are programming-related (e.g. ensuring website compatibility with different devices and browsers, optimizing website speed and performance)
- > - **Software development tools**: how to install, configure, troubleshoot, and use tools specifically meant for software development (e.g. compilers, debuggers, IDEs).
- > - **software development process** and project cycles specific to the software engineering such as requirements, design, or testing.
- > - **Software life cycle management**: build configurations, version control, release, deployment, etc.
- > - **Software documentation**: how to write it or how to use tools for that purpose.
- > - **Database management**: database design, programming, or access through SQL.
- > - **Code reviews** that follow [the guidelines for code review](https://software.codidact.com/help/code-review-guide).
- > - **User Interfaces that involve some programming**: mark-up language syntax, how to set properties in RAD tools, how to use graphic libraries, algorithms related to drawing graphics, including to some extent the math and physics behind it.
- > - **Quality Assurance**: programming, scripting, software design & architecture, process, tools, testing, and more.
- ## Off-topic
- The following types of questions are off-topic:
- > - **Asking for implementations** of a certain feature or a whole homework assignment. You should include your (partially working) attempts in the post
- > - **Asking for detailed explanations of posted code**, unless the code is small, self-contained, and an attempt to understand it is also included.
- > - **Simple typos**: if the issue was caused by simple typographical errors, the question is very unlikely to be useful for future readers and may be closed.
- > - **General computer or software support** which is not connected to software development/engineering (e.g. ask for recommendations)
- > - **System, network or server administration** questions
- > - **Embedded systems programming** including microcontroller programming, hardware description languages, RTOS questions, PLC programming. Please use [Electrical Codidact](https://electrical.codidact.com/) instead.
- > - **Project management**.
- > - **Software licensing**.
- > - **UI or graphic aesthetics.** What looks best, color choices, graphic design, and similar are mostly subjective questions.
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
#16: Post edited
# General scope of this site- Software Development Codidact is about writing software, where software is understood to include any means of specifying computer actions to be performed later. This refers to both general-purpose programming and scripting languages such as SQL and shell scripts.
- ## On-topic
- On-topic questions should be about one of the following:
- > - **Software design**, architecture, or modeling.
- > - **Software implementation**: specific programming or troubleshooting problems that include attempts to solve or debug the problem.
- > - **Best practices**, as long as clear "best" criteria are provided. Examples: fastest execution, least memory use, widest tool support for a target, most beginner-friendly IDE for a certain language and operating system
- > - **Software development tools**: how to install, configure, troubleshoot, and use tools specifically meant for software development (e.g. compilers, debuggers, IDEs).
- > - **software development process** and project cycles specific to the software engineering such as requirements, design, or testing.
- > - **Software life cycle management**: build configurations, version control, release, deployment, etc.
- > - **Software documentation**: how to write it or how to use tools for that purpose.
- > - **Database management**: database design, programming, or access through SQL.
- > - **Code reviews** that follow [the guidelines for code review](https://software.codidact.com/help/code-review-guide).
- > - **User Interfaces that involve some programming**: mark-up language syntax, how to set properties in RAD tools, how to use graphic libraries, algorithms related to drawing graphics, including to some extent the math and physics behind it.
- > - **Quality Assurance**: programming, scripting, software design & architecture, process, tools, testing, and more.
- ## Off-topic
- The following types of questions are off-topic:
- > - **Asking for implementations** of a certain feature or a whole homework assignment. You should include your (partially working) attempts in the post
- > - **Asking for detailed explanations of posted code**, unless the code is small, self-contained, and an attempt to understand it is also included.
- > - **Simple typos**: if the issue was caused by simple typographical errors, the question is very unlikely to be useful for future readers and may be closed.
- > - **General computer or software support** which is not connected to software development/engineering (e.g. ask for recommendations)
- > - **System, network or server administration** questions
- > - **Embedded systems programming** including microcontroller programming, hardware description languages, RTOS questions, PLC programming. Please use [Electrical Codidact](https://electrical.codidact.com/) instead.
- > - **Project management**.
- > - **Software licensing**.
- > - **UI or graphic aesthetics.** What looks best, color choices, graphic design, and similar are mostly subjective questions.
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
- ## General scope of this site
- Software Development Codidact is about writing software, where software is understood to include any means of specifying computer actions to be performed later. This refers to both general-purpose programming and scripting languages such as SQL and shell scripts.
- ## On-topic
- On-topic questions should be about one of the following:
- > - **Software design**, architecture, or modeling.
- > - **Software implementation**: specific programming or troubleshooting problems that include attempts to solve or debug the problem.
- > - **Best practices**, as long as clear "best" criteria are provided. Examples: fastest execution, least memory use, widest tool support for a target, most beginner-friendly IDE for a certain language and operating system
- > - **Software development tools**: how to install, configure, troubleshoot, and use tools specifically meant for software development (e.g. compilers, debuggers, IDEs).
- > - **software development process** and project cycles specific to the software engineering such as requirements, design, or testing.
- > - **Software life cycle management**: build configurations, version control, release, deployment, etc.
- > - **Software documentation**: how to write it or how to use tools for that purpose.
- > - **Database management**: database design, programming, or access through SQL.
- > - **Code reviews** that follow [the guidelines for code review](https://software.codidact.com/help/code-review-guide).
- > - **User Interfaces that involve some programming**: mark-up language syntax, how to set properties in RAD tools, how to use graphic libraries, algorithms related to drawing graphics, including to some extent the math and physics behind it.
- > - **Quality Assurance**: programming, scripting, software design & architecture, process, tools, testing, and more.
- ## Off-topic
- The following types of questions are off-topic:
- > - **Asking for implementations** of a certain feature or a whole homework assignment. You should include your (partially working) attempts in the post
- > - **Asking for detailed explanations of posted code**, unless the code is small, self-contained, and an attempt to understand it is also included.
- > - **Simple typos**: if the issue was caused by simple typographical errors, the question is very unlikely to be useful for future readers and may be closed.
- > - **General computer or software support** which is not connected to software development/engineering (e.g. ask for recommendations)
- > - **System, network or server administration** questions
- > - **Embedded systems programming** including microcontroller programming, hardware description languages, RTOS questions, PLC programming. Please use [Electrical Codidact](https://electrical.codidact.com/) instead.
- > - **Project management**.
- > - **Software licensing**.
- > - **UI or graphic aesthetics.** What looks best, color choices, graphic design, and similar are mostly subjective questions.
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
#14: Post edited
Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.To better understand what is on-topic and what is offtopic, please read the following sections.### On-topicOn-topic questions are about writing software, where software is understood to include any means of specifying to computer actions to be performed later. (This includes general-purpose programming languages as well as, for example, SQL, shell scripts, and spreadsheets).- questions about software design, software architecture, or modeling- questions about specific programming problems that include attempts to solve or debug the problem (aka troubleshooting questions)- questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)- questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus- questions related to software life cycle management, including build configurations, version control, release, and deployment.- questions dealing with how to write software documentation or how to use tools for that purpose- questions about database design, programming, or access through SQL (SQL programming).- questions asking for code review that follows [the guideline for code-review](https://software.codidact.com/policy/code-review-guide).- questions about how to install, configure, troubleshoot and use **tools specifically meant for software development** (e.g. compilers, debuggers, IDEs)- UI/UX questions related to an interface that involves some programming: regarding to UI, including mark-up language syntax, how to set properties in RAD tools, how to use graphic libraries- algorithm questions for how to draw graphics, including to some extent the math and physics behind it### Off-topic- questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post- asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.- questions about computers or software that are not connected to software development/engineering (e.g. ask for recommendations)- questions about system, network, or server administration- questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use[Electrical Codidact](https://electrical.codidact.com/) instead.- asking about project management of software projects- asking about software licensing- questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future- UI-related questions dealing with the aesthetic part - what looks best, color choices, graphic design, and similar mostly subjective questions- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
- # General scope of this site
- Software Development Codidact is about writing software, where software is understood to include any means of specifying computer actions to be performed later. This refers to both general-purpose programming and scripting languages such as SQL and shell scripts.
- ## On-topic
- On-topic questions should be about one of the following:
- > - **Software design**, architecture, or modeling.
- > - **Software implementation**: specific programming or troubleshooting problems that include attempts to solve or debug the problem.
- > - **Best practices**, as long as clear "best" criteria are provided. Examples: fastest execution, least memory use, widest tool support for a target, most beginner-friendly IDE for a certain language and operating system
- > - **Software development tools**: how to install, configure, troubleshoot, and use tools specifically meant for software development (e.g. compilers, debuggers, IDEs).
- > - **software development process** and project cycles specific to the software engineering such as requirements, design, or testing.
- > - **Software life cycle management**: build configurations, version control, release, deployment, etc.
- > - **Software documentation**: how to write it or how to use tools for that purpose.
- > - **Database management**: database design, programming, or access through SQL.
- > - **Code reviews** that follow [the guidelines for code review](https://software.codidact.com/help/code-review-guide).
- > - **User Interfaces that involve some programming**: mark-up language syntax, how to set properties in RAD tools, how to use graphic libraries, algorithms related to drawing graphics, including to some extent the math and physics behind it.
- > - **Quality Assurance**: programming, scripting, software design & architecture, process, tools, testing, and more.
- ## Off-topic
- The following types of questions are off-topic:
- > - **Asking for implementations** of a certain feature or a whole homework assignment. You should include your (partially working) attempts in the post
- > - **Asking for detailed explanations of posted code**, unless the code is small, self-contained, and an attempt to understand it is also included.
- > - **Simple typos**: if the issue was caused by simple typographical errors, the question is very unlikely to be useful for future readers and may be closed.
- > - **General computer or software support** which is not connected to software development/engineering (e.g. ask for recommendations)
- > - **System, network or server administration** questions
- > - **Embedded systems programming** including microcontroller programming, hardware description languages, RTOS questions, PLC programming. Please use [Electrical Codidact](https://electrical.codidact.com/) instead.
- > - **Project management**.
- > - **Software licensing**.
- > - **UI or graphic aesthetics.** What looks best, color choices, graphic design, and similar are mostly subjective questions.
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
#13: Post edited
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- On-topic questions are about writing software, where software is understood to include any means of specifying to computer actions to be performed later. (This includes general-purpose programming languages as well as, for example, SQL, shell scripts, and spreadsheets).
- - questions about software design, software architecture, or modeling
- - questions about specific programming problems that include attempts to solve or debug the problem (aka troubleshooting questions)
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation or how to use tools for that purpose
- - questions about database design, programming, or access through SQL (SQL programming).
- - questions asking for code review that follows [the guideline for code-review](https://software.codidact.com/policy/code-review-guide).
- - questions about how to install, configure, troubleshoot and use **tools specifically meant for software development** (e.g. compilers, debuggers, IDEs)
- UI/UX questions related to an interface that involves some programming (e.g. web interfaces)- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering (e.g. ask for recommendations)
- - questions about system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- On-topic questions are about writing software, where software is understood to include any means of specifying to computer actions to be performed later. (This includes general-purpose programming languages as well as, for example, SQL, shell scripts, and spreadsheets).
- - questions about software design, software architecture, or modeling
- - questions about specific programming problems that include attempts to solve or debug the problem (aka troubleshooting questions)
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation or how to use tools for that purpose
- - questions about database design, programming, or access through SQL (SQL programming).
- - questions asking for code review that follows [the guideline for code-review](https://software.codidact.com/policy/code-review-guide).
- - questions about how to install, configure, troubleshoot and use **tools specifically meant for software development** (e.g. compilers, debuggers, IDEs)
- - UI/UX questions related to an interface that involves some programming: regarding to UI, including mark-up language syntax, how to set properties in RAD tools, how to use graphic libraries
- - algorithm questions for how to draw graphics, including to some extent the math and physics behind it
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering (e.g. ask for recommendations)
- - questions about system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- - UI-related questions dealing with the aesthetic part - what looks best, color choices, graphic design, and similar mostly subjective questions
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
#12: Post edited
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- On-topic questions are about writing software, where software is understood to include any means of specifying to computer actions to be performed later. (This includes general-purpose programming languages as well as, for example, SQL, shell scripts, and spreadsheets).
- - questions about software design, software architecture, or modeling
- - questions about specific programming problems that include attempts to solve or debug the problem (aka troubleshooting questions)
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation or how to use tools for that purpose
- - questions about database design, programming, or access through SQL (SQL programming).
- - questions asking for code review that follows [the guideline for code-review](https://software.codidact.com/policy/code-review-guide).
- questions about how to install, configure, trouble-shoot and use **tools specifically meant for software development** (e.g. compilers, debuggers, IDEs)- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering (e.g. ask for recommendations)
- - questions about system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- On-topic questions are about writing software, where software is understood to include any means of specifying to computer actions to be performed later. (This includes general-purpose programming languages as well as, for example, SQL, shell scripts, and spreadsheets).
- - questions about software design, software architecture, or modeling
- - questions about specific programming problems that include attempts to solve or debug the problem (aka troubleshooting questions)
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation or how to use tools for that purpose
- - questions about database design, programming, or access through SQL (SQL programming).
- - questions asking for code review that follows [the guideline for code-review](https://software.codidact.com/policy/code-review-guide).
- - questions about how to install, configure, troubleshoot and use **tools specifically meant for software development** (e.g. compilers, debuggers, IDEs)
- - UI/UX questions related to an interface that involves some programming (e.g. web interfaces)
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering (e.g. ask for recommendations)
- - questions about system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
#11: Post edited
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- On-topic questions are about writing software, where software is understood to include any means of specifying to computer actions to be performed later. (This includes general-purpose programming languages as well as, for example, SQL, shell scripts, and spreadsheets).
- - questions about software design, software architecture, or modeling
- - questions about specific programming problems that include attempts to solve or debug the problem (aka troubleshooting questions)
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation or how to use tools for that purpose
- - questions about database design, programming, or access through SQL (SQL programming).
- - questions asking for code review that follows [the guideline for code-review](https://software.codidact.com/policy/code-review-guide).
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering (e.g. ask for recommendations)
- - questions about system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- On-topic questions are about writing software, where software is understood to include any means of specifying to computer actions to be performed later. (This includes general-purpose programming languages as well as, for example, SQL, shell scripts, and spreadsheets).
- - questions about software design, software architecture, or modeling
- - questions about specific programming problems that include attempts to solve or debug the problem (aka troubleshooting questions)
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation or how to use tools for that purpose
- - questions about database design, programming, or access through SQL (SQL programming).
- - questions asking for code review that follows [the guideline for code-review](https://software.codidact.com/policy/code-review-guide).
- - questions about how to install, configure, trouble-shoot and use **tools specifically meant for software development** (e.g. compilers, debuggers, IDEs)
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering (e.g. ask for recommendations)
- - questions about system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
#10: Post edited
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- On-topic questions are about writing software, where software is understood to include any means of specifying to computer actions to be performed later. (This includes general-purpose programming languages as well as, for example, SQL, shell scripts, and spreadsheets).
- - questions about software design, software architecture, or modeling
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation or how to use tools for that purpose
- - questions about database design, programming, or access through SQL (SQL programming).
- - questions asking for code review that follows [the guideline for code-review](https://software.codidact.com/policy/code-review-guide).
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering (e.g. ask for recommendations)
- - questions about system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- On-topic questions are about writing software, where software is understood to include any means of specifying to computer actions to be performed later. (This includes general-purpose programming languages as well as, for example, SQL, shell scripts, and spreadsheets).
- - questions about software design, software architecture, or modeling
- - questions about specific programming problems that include attempts to solve or debug the problem (aka troubleshooting questions)
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation or how to use tools for that purpose
- - questions about database design, programming, or access through SQL (SQL programming).
- - questions asking for code review that follows [the guideline for code-review](https://software.codidact.com/policy/code-review-guide).
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering (e.g. ask for recommendations)
- - questions about system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
#9: Post edited
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- On-topic questions are about writing software, where software is understood to include any means of specifying to computer actions to be performed later. (This includes general-purpose programming languages as well as, for example, SQL, shell scripts, and spreadsheets).
- - questions about software design, software architecture, or modeling
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation or how to use tools for that purpose
- - questions about database design, programming, or access through SQL (SQL programming).
- - questions asking for code review that follows [the guideline for code-review](https://software.codidact.com/policy/code-review-guide).
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering (e.g. ask for recommendations)
- questions about the system, network, or server administration- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- On-topic questions are about writing software, where software is understood to include any means of specifying to computer actions to be performed later. (This includes general-purpose programming languages as well as, for example, SQL, shell scripts, and spreadsheets).
- - questions about software design, software architecture, or modeling
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation or how to use tools for that purpose
- - questions about database design, programming, or access through SQL (SQL programming).
- - questions asking for code review that follows [the guideline for code-review](https://software.codidact.com/policy/code-review-guide).
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering (e.g. ask for recommendations)
- - questions about system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
#8: Post edited
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- On-topic questions are about writing software, where software is understood to include any means of specifying to computer actions to be performed later. (This includes general-purpose programming languages as well as, for example, SQL, shell scripts, and spreadsheets).
- - questions about software design, software architecture, or modeling
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- questions dealing with how to write software documentation.- - questions about database design, programming, or access through SQL (SQL programming).
- - questions asking for code review that follows [the guideline for code-review](https://software.codidact.com/policy/code-review-guide).
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering (e.g. ask for recommendations)
- - questions about the system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- On-topic questions are about writing software, where software is understood to include any means of specifying to computer actions to be performed later. (This includes general-purpose programming languages as well as, for example, SQL, shell scripts, and spreadsheets).
- - questions about software design, software architecture, or modeling
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation or how to use tools for that purpose
- - questions about database design, programming, or access through SQL (SQL programming).
- - questions asking for code review that follows [the guideline for code-review](https://software.codidact.com/policy/code-review-guide).
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering (e.g. ask for recommendations)
- - questions about the system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
#7: Post edited
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- On-topic questions are about writing software, where software is understood to include any means of specifying to computer actions to be performed later. (This includes general-purpose programming languages as well as, for example, SQL, shell scripts, and spreadsheets).
- - questions about software design, software architecture, or modeling
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation.
- - questions about database design, programming, or access through SQL (SQL programming).
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering (e.g. ask for recommendations)
- - questions about the system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- On-topic questions are about writing software, where software is understood to include any means of specifying to computer actions to be performed later. (This includes general-purpose programming languages as well as, for example, SQL, shell scripts, and spreadsheets).
- - questions about software design, software architecture, or modeling
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation.
- - questions about database design, programming, or access through SQL (SQL programming).
- - questions asking for code review that follows [the guideline for code-review](https://software.codidact.com/policy/code-review-guide).
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering (e.g. ask for recommendations)
- - questions about the system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
#6: Post edited
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- On-topic questions are about writing software, where software is understood to include any means of specifying to computer actions to be performed later. (This includes general-purpose programming languages as well as, for example, SQL, shell scripts, and spreadsheets).
- - questions about software design, software architecture, or modeling
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation.
- - questions about database design, programming, or access through SQL (SQL programming).
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- questions about computers or software that are not connected to software development/engineering- - questions about the system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- questions about which tools, frameworks, or technologies to use, unless they are directly related to development (e.g. code, schema changes documentation tools)- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- On-topic questions are about writing software, where software is understood to include any means of specifying to computer actions to be performed later. (This includes general-purpose programming languages as well as, for example, SQL, shell scripts, and spreadsheets).
- - questions about software design, software architecture, or modeling
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation.
- - questions about database design, programming, or access through SQL (SQL programming).
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering (e.g. ask for recommendations)
- - questions about the system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
#5: Post edited
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- - questions about software design, software architecture, or modeling
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation.
- - questions about database design, programming, or access through SQL (SQL programming).
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering
- - questions about the system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - questions about which tools, frameworks, or technologies to use, unless they are directly related to development (e.g. code, schema changes documentation tools)
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- On-topic questions are about writing software, where software is understood to include any means of specifying to computer actions to be performed later. (This includes general-purpose programming languages as well as, for example, SQL, shell scripts, and spreadsheets).
- - questions about software design, software architecture, or modeling
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation.
- - questions about database design, programming, or access through SQL (SQL programming).
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering
- - questions about the system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - questions about which tools, frameworks, or technologies to use, unless they are directly related to development (e.g. code, schema changes documentation tools)
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
#4: Post edited
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- - questions about software design, software architecture, or modeling
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- questions dealing with how to write software documentation- questions about SQL programming- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering
- - questions about the system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - questions about which tools, frameworks, or technologies to use, unless they are directly related to development (e.g. code, schema changes documentation tools)
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- questions about database administration- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- - questions about software design, software architecture, or modeling
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation.
- - questions about database design, programming, or access through SQL (SQL programming).
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering
- - questions about the system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - questions about which tools, frameworks, or technologies to use, unless they are directly related to development (e.g. code, schema changes documentation tools)
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
#3: Post edited
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- - questions about software design, software architecture, or modeling
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- questions about best practices as long as enough detail is provided to answer using external references or expertise consensus- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation
- - questions about SQL programming
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering
- - questions about the system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - questions about which tools, frameworks, or technologies to use, unless they are directly related to development (e.g. code, schema changes documentation tools)
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- - questions about database administration
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- - questions about software design, software architecture, or modeling
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as clear "best" criteria are provided and they can be answered using references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation
- - questions about SQL programming
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering
- - questions about the system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - questions about which tools, frameworks, or technologies to use, unless they are directly related to development (e.g. code, schema changes documentation tools)
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- - questions about database administration
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
#2: Post edited
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- - questions about software design, software architecture, or modeling
- questions related to software design/review - what item goes where when using a certain technology stack- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as enough detail is provided to answer using external references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation
- - questions about SQL programming
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering
- - questions about the system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - questions about which tools, frameworks, or technologies to use, unless they are directly related to development (e.g. code, schema changes documentation tools)
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- - questions about database administration
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- - questions about software design, software architecture, or modeling
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as enough detail is provided to answer using external references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation
- - questions about SQL programming
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering
- - questions about the system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - questions about which tools, frameworks, or technologies to use, unless they are directly related to development (e.g. code, schema changes documentation tools)
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- - questions about database administration
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
#1: Post edited
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- - questions about software design, software architecture, or modeling
- - questions related to software design/review - what item goes where when using a certain technology stack
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as enough detail is provided to answer using external references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation
- - questions about SQL programming
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- asking to explain what a certain code does.- - questions about computers or software that are not connected to software development/engineering
- - questions about the system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - questions about which tools, frameworks, or technologies to use, unless they are directly related to development (e.g. code, schema changes documentation tools)
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- - questions about database administration
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.
- Software Development Codidact is for software developers, people who like writing code. We tend to consider that the [best questions](https://software.codidact.com/help/how-to-ask) include some source code, but some without might also fit.
- To better understand what is on-topic and what is offtopic, please read the following sections.
- ### On-topic
- - questions about software design, software architecture, or modeling
- - questions related to software design/review - what item goes where when using a certain technology stack
- - questions about the software development process and project cycles specific to software engineering (requirements, design, testing, etc)
- - questions about best practices as long as enough detail is provided to answer using external references or expertise consensus
- - questions related to software life cycle management, including build configurations, version control, release, and deployment.
- - questions dealing with how to write software documentation
- - questions about SQL programming
- ### Off-topic
- - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post
- - asking to explain what a certain code does, unless they are small and an attempt to understand them is also added.
- - questions about computers or software that are not connected to software development/engineering
- - questions about the system, network, or server administration
- - questions about embedded systems programming (microcontroller programming, hardware description languages, RTOS questions, PLC programming). Please use
- [Electrical Codidact](https://electrical.codidact.com/) instead.
- - questions about which tools, frameworks, or technologies to use, unless they are directly related to development (e.g. code, schema changes documentation tools)
- - asking about project management of software projects
- - asking about software licensing
- - questions containing errors caused by typographical errors, as it is very unlikely to be useful in the future
- - questions about database administration
- It is important that your question contains enough information that another person can use to help you. After writing the post, please take a couple of moments to review it.