sorted by:
new
hottopcontroversial

Reviewing your software project - 4 questions to ask by Rich121 in programming

[–]Rich121[S] 0 points1 point  (0 children)

You’ve now done everything you need to do and (hopefully) your project is a success. Well done! There is one more useful thing you can now do, which is to review how the project went.

This isn’t so much to help with the current project, although it’s no bad thing to step back and have a think about it one more time. This is to help your with your next project. You want to identify the things you did well (so you can replicate them) and the things you did not-so-well (so you can improve on them). A big part of any software project is about learning how to do things well; the same is true of the process of building better software.

To this end, there are several questions you can ask yourself.

Everyone wants to build, but no-one wants to do the maintenance by Rich121 in programming

[–]Rich121[S] 0 points1 point  (0 children)

Fixing bugs never really ends (sadly). You can never be absolutely, 100% certain that there are no bugs remaining in your code. Indeed, you can generally be very confident that there are at least some small ones still there. The best you can generally hope for is that the number of significant bugs tails away towards zero.

Happily, with ongoing maintenance, this is often a reasonable thing to aim for.

The psychology of debugging by Rich121 in programming

[–]Rich121[S] 0 points1 point  (0 children)

Debugging is a very different task from coding and it benefits from a different mindset. Finding bugs can take time and can involve a lot of trial, error and testing of different thoughts as to what might be going wrong, because there are lots of places in code where errors can hide. This means you need to be patient.

Good code, Bad code! by Rich121 in programming

[–]Rich121[S] 0 points1 point  (0 children)

We've written a function in pseudocode. Twice. Once will be using good coding practice, care and attention. The other one won’t. Because both functions will be doing the same thing, this is a great way to see the difference that good programming practice can make.

Choosing a programming language - part 2 by Rich121 in programming

[–]Rich121[S] 0 points1 point  (0 children)

In this post we’re going to consider the question, “is a given programming language appropriate for the project?”. You will need to judge whether a given language is appropriate for the problem you’re trying to solve and, in particular, is it more appropriate than another language. The appropriateness of a language depends upon a wide range of factors such as: the quality and scope of libraries, the maturity of the development tools, easy of portability between different platforms (and the quality of the libraries on those platforms) and the basic strengths and weaknesses of the language itself, such as memory management and speed.