As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Having a program that has several distinct parts is usual.By part I mean a graphical part that has its own windows and functionalities.(About non graphical part, I think creating a library is the preferable solution)
How do you prefer to separate them ?
Is it better to make each of them a static library and use them in the main program?
Or the better solution is to create an executable file of each one and load them in the main program?
Or even better solution?
I suggest that you read Code Complete or something simlar. This book and others go into the best practices or even how to know which of the best practices you should look into when you create a product.
The problem is one of scope. You need to know your specifications and the parts that join together, as well as which design practices you are going to use before you can answer this question.
I am also inclined to think that there is no right or wrong answer (depending on HOW wrong you are) and that no-one else can answer that question for you, especially since you are likely to be one of the main players in maintaining the code.
Hope that gives you some food for thought :-)
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
This is more a philosophical question but its one I've been pondering for some time now.
I don't know anything about computer security or how computers are broken into. I thought hackers used disassembling software on executable software to create malware and other things.
My question is would making some software open source make it vulnerable to hackers or do I have reverse engineering confused with hacking?
Making something open source does not inherently make it more vulnerable. Trying to hide what you are doing is known as Security Through Obscurity, and it doesn't work very well.
Making something open source makes things easier for casual hackers, since they can see how your app works more easily. On the other hand, making it open source also lets anyone who is interested look through your code and report security vulnerabilities. They're two sides of the same coin.
For the most advanced threats, they'll get through regardless of whether your code is open source or not. On the other hand, honest volunteers are much less likely to bother trying to find and fix bugs in a closed source product.
So basically, it depends. In general, you're better off open sourcing things if you think people are actually going to be interested in the project.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I have a navigation providing interface, where in given the starting and destination points, and somehow the map of the street maybe, then the path is chosen based on the map, i.e. if a way is found then move in the direction, or if some blockage is found, or if the path will not lead to the desired destination then check for some other path maybe.
Now what programming language will be the best for it? I have worked with C only till now. Will it be all right for me to code in C only?
Is there anything else I need to take care before I take up this project? (Apart from the implementation issues).
Thanks.
Look, the best thing to do is to just start coding and find out. If you are not experienced, it's better to use the language you're familiar with rather than learn a new one. At the end of the day, you can achieve most tasks with most languages.
It's not so much what you use but how you use it.
In terms of the path-finding implementation, you might want to start by looking at A-star or Dijkstra's algorithm.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
As a programming novice, I often run into trouble when trying to install packages, use virtualenv, and basically do anything even mildly complex using the command line.
What are some good references out there to help me UNDERSTAND things like my path, environment, shell scripts, etc?
Basically, I'm tired of copying and pasting. I want to really understand what's going on.
Thanks!
I used Linux in a Nutshell by O'Reilly. It helps you get past the initial beginners stage. Obviously there are a ton more links and tutorials, lists of keystrokes online, easily found with a Google search, but this will help you get going, and nice to read when you are on the bus or at lunch or whatever, to give you some ideas you might not just happen on in normal everyday life.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I have dealt and used JavaScript and am quite comfortable with it. However I was wondering if I should learn another one. Is there another language out there that used more widely or has more use in the business industry? And could you also recommend a good book for it?
Should you learn a new programming language?
Yes, you surely should.
Which one then?
I don't know. Why don't you pick one related to your expertise? Or something wildly different from what you know.
Which book is the best one?
Go to the library or a book shop. Flip some books through. Most likely, one of those books is good enough. But nothing beats learning to look up API reference on the net.
EDIT: Question from the comments:
What's the most popular and widely used?
You can use the TIOBE Community Index to look up popular programming languages. However, you shouldn't use that as a deciding factor as things may differ locally to you. I've never done C professionally (which is apparently the most "popular" language according to TIOBE), so it all depends on what you want to do.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Any recommendations for katas covering generics and delegates in C#?
Most of the member on my team can code generics and delegates, but always require a quick look at the documentation or an example to jump start our brains on them. So I thought that for our daily kata we would cover these aspects for a couple of weeks until we can read and write them by instinct.
This would make it easier for us to use these tools in our coding retreats for design patterns.
Thanks in advance for any recommendations...
You may think this terribly vain of me to suggest, but how about doing the same sort of exercise as I've been engaging in for the last month or so? Namely reimplementing LINQ to Objects. My posts aren't in kata form, but you might find them useful to suggest an ordering, and they could give you hints if you get stuck.
LINQ to Objects is all about delegates and is based on generic sequences (with plenty of generic methods involved) so between the tests and the implementation you'll get a lot of practice in - and get to know LINQ better at the same time!
If you're only doing it for a specific exercise you could always ignore some of the trickier operators (like OrderBy etc).