Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I'm writing this after doing searches and not finding much useful answers. I know the basic of programming, like context (loops, conditionals), basic ideas (classes, instances, inheritance.) and I'd like to improve on my OOP. The thing is when I look at open source projects, they seem very overwhelming because there is so much going on. How can I improve and learn the concepts of OOP without jumping into a huge project. I'd like to go in steps because I always learn best when things are broken down and not thrown at me all at once. Are there any resources you can share? Or any advice in general would be really appreciated. I want to take the next step, but just don't know where to begin. How did you guys go about improving your skills, how did you take the next step? Right now I'm focused on C++ and Ruby.
OOP is an idea and doesn't depend on your programming language.
You can learn various design patterns to improve your OOP.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 days ago.
Improve this question
I need practical advice on how to build a compiler. Any advice is welcome, metaphors, tools, a learning order, things to study, etc.
At the moment I have been studying regular expressions and automata theory, deterministic and non-deterministic finite automata, but I don't understand the concepts very well, I plan to keep studying and share my progress with the community on this occasion.
I would appreciate any input or comments on your experiences in similar cases, as I said, anything is welcome, thank you very much!
The instructions I have received are as follows:
[Implement a compiler for a specific language considering the language stages.
Define, design and program the lexical and syntactic analyser stages of a translator or compiler to preamble the construction of a compiler].
As you can see the assignment is actually very abstract and it benefits me to do it my way, so I want to make the most of this experience.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I learned C++ basics such as syntax, data structures, and OOP. What should I learn next to be able to find small jobs as a college student and where?
Join open-source project. Checkout code, analyze it, learn, and once you will be more confident with your skills you can prepare your own features/fixes. Results of your pull requests will be your skills "score". The main advantage of it is seeing large-scale code, without going through job interview.
You can offer your skills as a freelancer. But remember that without practical knowledge your design decisions may be wrong. So don't take big contracts, because you may struggle with your own bugs.
Try to apply for an internship or a full/part-time job as a Junior Developer. The advantage is the same as (1) and you will get some money. But some jobs maybe not what you would expect to be, in open-source project you may choose your favorite.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I'm currently self-studying C++ and I'm about to finish my OOP course, till now, I've finished the OOP concepts but the course also includes an introduction to the STL, but I feel like it's too early to have a look on the STL at this stage(before studying Data Structures).
Is it a good idea to skip the last part of the OOP course and start studying Data Structures right now? or should I complete the course anyway?
In my opinion, if you already can understand OOP principles you should use STL and do not care how it really works under the hood, but after that, you should learn basic data structures and all will come clear for you.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
Relatively new to C++ but I am very interested in the algorithmic aspect of programming.
Is there a general framework for deciding if an algorithm is efficient? i.e. the quickest possible?
I am trying to write pseudocode on paper before implementing but there are probably many different ways to solve any given problem.
Would be very keen to learn best practice for constructing / analysing algorithms.
Thanks, and Happy New Year!
Yes you can start with the Wikipedia article explaining the Big O notation, which in a nutshell is a way of describing the "efficiency" (upper bound of complexity) of different type of algorithms. Or you can look at an earlier answer where this is explained in simple english
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I want to start learning DirectX and I do have an extremely strong grasp of C++
Anyways I have searched online and I saw that people recommend that I start with dx9 then move my way up to the other DXs
Now my question is
If I learn dx9 and fully grasp it then move on to Dx10 and then to Dx11 Will that cause me to get mixed up while I'm programming when I learn the newer DirectX because of the similar code
or will it help me understand the language and be better at using it?
Honestly, there's not an awful lot of point in learning DX10. If you don't need hardware compatibility, go straight to DX11. If you do, then stick with DX9. The hard part about graphics programming has little to do with the API- most of it is in programmable shaders and techniques that are not strongly tied to the API you're using.