C++

Yes, as a Science student, you can pursue a Bachelor of Commerce B.Com degree, provided you meet the eligibility criteria set by the college or university offering the course. Typically, a candidate should have passed their 10+2 examination in any stream with a minimum percentage of marks, usually ranging from 45% to 60% depending on the college or university. In India, there are mainly three streams in B.Com namely B.Com (General), B.Com (Honours), and B.Com (Professional). Each of these streams has a different set of subjects that are taught during the course. Here are the details:
1. B.Com (General): This is the most common stream in B.Com which covers various aspects of commerce, management, accounting, and finance. The subjects typically taught in this stream are:- Financial Accounting- Business Economics- Business Mathematics and Statistics- Corporate Accounting- Cost Accounting- Business Law- Marketing Management- Human Resource Management- Income Tax Law and Practice- Auditing and Assurance
2. B.Com (Honours): This stream focuses on a particular subject or discipline in commerce, and students are expected to study that subject in-depth. The subjects typically taught in this stream are:- Corporate Accounting- Financial Management- Cost and Management Accounting- Business Economics- Marketing Management- Income Tax Law and Practice- Auditing and Assurance- Entrepreneurship and Small Business Management- Business Communication- Organizational Behaviour
3. B.Com (Professional): This stream is designed to provide students with specialised knowledge and skills in accounting, taxation, and finance. The subjects typically taught in this stream are:- Financial Accounting- Business Economics- Cost Accounting- Income Tax Law and Practice- Auditing and Assurance- Corporate Accounting- Banking and Insurance- Financial Management- Management Accounting- Investment Management
You can choose any of these streams based on your interests and career goals. It's recommended that you do some research on each of these streams and the subjects taught in them to make an informed decision.

Mathematical reasoning is at the heart of programming. Learning to think fluently about data structures, algorithms, functions, effects, abstraction, and generalization is essential for every programmer. A issue has to be grasped, struggled with, solved, and then solved better. You need to critically consider your options, settle on a strategy that seems to have the most promise, and then figure out whether or not you can really implement it. What we have here is mathematics. Can someone who is poor at arithmetic improve their skills via practice?
To begin, there is no such thing. Mathematics covers a wide range of topics, and most people excel at some of them more than others. If you consider yourself ""poor at math, "" it's likely because you're having trouble with the math courses you're taking. This may be because they are actually tough for you, or maybe they aren't being taught in a manner that connects with you, or it may indicate that you have a profound gap in your mathematical development from when you were nine years old. This occurs often. There's no way for me, or anybody, to estimate your exact bad at math circumstance. The issue may or may not have a solution. It would be as harsh to urge you to give up and to encourage you not to worry, just trust in yourself and study. All I can tell you is that software engineering issue solving is not separate from math problem solving. Focus on the latter if you want to improve the former. It's typically something you learnt a long time ago but still don't fully grasp, so it's a good idea to obtain an outside opinion on what's causing your problem.

Computer programmers create software. Systems are constructed by software engineers. As far as I can tell, that's the main difference. It's one thing to create a software that really does anything. It's another thing entirely to design a software that works and can interact with a wide variety of other programs. And it's an entirely different thing to write a programme that can work with many other programs, run many instances of these programs simultaneously so you can handle massive transaction volumes, and then figure out how to keep the whole thing running when one or more of the programs is failing, especially since a failure in one programme usually results in the effects of the failure cascading through. Scalability, error detection and correction, fault tolerance, analysis of failure, monitoring, tuning, alerting, privacy protection, and the management of scarce resources are all part of software engineering. Most programmers won't encounter issues like that. And that's how people become software engineers in the first place: because they have to.