Stackoverflow

If you want to know your path to becoming a developer and know the prerequisites and things you need to learn, visit the following site. https://roadmap.sh @stackoverflow

What is the ElectronJS? A framework to build desktop application using single codebase via nodejs with web technologies such as vue.js and reactjs. Because of using web technology, app can harnesses modern web ui as a desktop app for Linux, windows and Mac OSes. @stackoverflow

What's is the GraphQL? GraphQL is a query language for your API, and a server-side runtime for executing queries using a type system you define for your data. GraphQL isn't tied to any specific database or storage engine and is instead backed by your existing code and data. @stackoverflow

The distinction between a software engineer and a programmer lies in their approach to application development. While a programmer is focused on building functional applications in the present, a software engineer prioritizes creating clean, maintainable code that can withstand the test of time. This approach not only minimizes financial and engineering work time in the long term, but also allows for easy integration of new changes without requiring a complete code rewrite. In essence, a software engineer's application is designed with scalability in mind, ensuring its longevity and adaptability to evolving business needs. Ali Iman @stackoverflow

With a sufficient number of users of an API, it does not matter what you promise in the contract; all observable behaviors of your system will be depended on by somebody. Hyrum's Law @stackoverflow

One of the pitfalls that programmers may encounter is the inclination to develop an idea in isolation and keep it under wraps until completion. This approach can be perilous for several reasons. Firstly, without soliciting feedback from trusted and experienced individuals, there is a risk of creating a product that is perceived as exceptional by the developer but may not resonate with the intended target audience. Secondly, there is the possibility of competitors who may have already developed a similar idea, leveraging the insights and advice of others to refine their product and address its shortcomings early on that your product cannot compete it because modifying the foundational structure of product may prove to be a time-consuming and futile endeavor. @stackoverflow

One of the biggest mistakes that beginners make is not to ask for help when they’re stuck. You might be tempted to struggle through it alone or feel fearful that your questions are “too simple.” “I just need to try harder before I ask anyone for help,” you think. Don’t fall into this trap! Your coworkers are often the best source of information: leverage this valuable resource. @stackoverflow

Knowledge is in some ways the most important (though intangible) capital of a software engineering organization, and sharing of that knowledge is crucial for making an organization resilient and redundant in the face of change. A culture that promotes open and honest knowledge sharing distributes that knowledge efficiently across the organization and allows that organization to scale over time. In most cases, investments into easier knowledge sharing reap manyfold dividends over the life of a company. @stackoverflow

No team can function well without a leader. There are two type of leadership role; A “Manager” is a leader of people, whereas while a “Tech Lead” leads technology efforts. Although the responsibilities of these two roles are quite different, they require quite similar skills. In nascent teams, both roles will sometimes be filled by the same person. On larger teams, an experienced people manager will step in to take on the management role, whereas a senior engineer with extensive experience will step into the tech lead role. The manager is responsible for the performance, productivity and happiness of every person on their team including the tech lead. The Tech Lead will often report to the manager and is responsible for the technical aspects of the product, including technology decisions, choices, architecture, priorities, velocity, and general project management. #leadership @stackoverflow