New answers tagged

2

Answering the questions an order that makes sense to me: Are the identified processes sensible, or are they too abstract? The items on your process list are rather brief and looks to me more like scenario heading names than processes. As I read it, in 4+1 processes are essentially running programs. ... At the highest level, the process ...


2

A possible way to help portability could be to rely only on declarations and features provided by the C++11 standard, and by using cross-platform libraries and frameworks like POCO & Qt. But even this is not fail-proof. Remember the aphorism there is no such thing as a portable program, there are only programs which have been successfully ported (to ...


10

Creating portable code can be very challenging. First some obvious language related advices: use standard C++ and avoid carefully any undefined behavior rely primarily on standard library (and portable libraries such as boost) always include all expected headers. Do not assume that you don't need a header because it's included in another one (i.e.on ...


3

It depends on the "some compilation errors" you mention. Without knowing what they were, it's impossible to be specific. I've got cross-platform code for Windows / Linux / iOS / Android / Mac. Each new platform brought some extra errors and warnings when it was first added. You will quickly learn which constructs bring problems. Either avoid them, or ...


7

If you are asking for "development processes" and you primary development platform is Windows with Visual Studio then I would suggest to try building your project without "windows.h" included. You will get a lot of compilation errors that will point you to many places where you'll need to refactor your code. For example, 'DWORD' won't be #defined and you'll ...


11

There is nothing that can guarantee that the code is compatible with a platform other than building it, running it, and testing it there. Therefore, the approach of all sane people is to build, run and test their application on every platform that they project it will need to be built, run, and test on. Continuous Integration (CI) can ease this burden a ...


-1

To be honest, the most important thing of Git for myself when I see it: 1. Network Graph or Should I call the History(also commenting) 2. Branch and Pull Request 3. It's more powerful, really, I would say it's so feels like I have a secretary holding all my work, and I can told that sec to wrote down anything for me, the change, everything! 4. It's easy to ...


6

The cost of professional tools You severely under-estimate the availability of free tools. Software development is an industry with a wealth of completely free tools that professional developers use every day. Free things that I use regularly in my job as a developer: git (Source control, the major thing you're looking for here.) KDiff3 SourceTree ...


24

The goal of Repl>it is to write and share short snippets of code. For instance, you may use it to illustrate your point when discussing a particular aspect of your favorite programming language with other programmers, or you may use it to sketch some code in a few minutes. Repl>it is not intended to actually write and maintain codebase of any size, not even ...


5

You could use your disappointment and upset as a chance to learn something. Any good editor takes frequent snapshots of your study, including emacs and every IDE I've used. You should find an editor that does this and use it. Saving code is usually required to run it so if you are developing locally this should be less of an issue. Of course you can still ...



Top 50 recent answers are included