|
It is all about determination because there are thousands of obstacles while programming any system, If one have steellike determination programming of system is easy task for him/her. so what i think is important aspect of programming is determination and thorough knowledge of system domain.
What you think is what you get
|
|
|
|
|
|
You bunch of geeks, money is the most important aspect of programming 
|
|
|
|
|
Yes this is an importar part...
With the motivation of money the good programmers become great ones
..and an excelent programmer bad paid becomes a big enemy !!!
Cheers
------------
My Articles[^]
|
|
|
|
|
|
As a professional developer the most important aspect of my work is being paid for it .. thats what being professional means.
Obviously money is not the most important aspect of good software design or solution architecture or many of the technical aspects of programming but understanding that money is the root of a lot of software development efforts helps your understanding of your clients needs.
.. and no I dont expect to become mega rich via programming but there are much worse ways of making a living
|
|
|
|
|
Sir/Madam
i want to know about the comport programming.i am working on a project of library management in that i add the bar codereader so i want to know about the bardcode reading and writing and also about the comport programing.
the programming language is c# and databasing in ado.net
so kindly responce as earlier possible.
|
|
|
|
|
|
and does what you intended, in terms of not only functionality, but maintainability, compliance, best practices, cost, and so forth.
Marc
Pensieve
-- modified at 17:42 Wednesday 1st March, 2006
|
|
|
|
|
Marc Clifton wrote: That it works and does what you intended, in terms of not only functionality, but maintainability, compliance, best practices, cost, and so forth.
I think "best practices" is uncessary, if you have everything else in there, then it must be the best practice.
My articles and software tools
|
|
|
|
|
Nope, it's not a "best practice" unless lots of other people are using it, too. At that point, it must be the best, since there's no way you're gonna get everyone to admit that they were wrong...
----
Bots don't know when people die.
--Paul Watson, RIP
|
|
|
|
|
Shog9 wrote: Nope, it's not a "best practice" unless lots of other people are using it, too. At that point, it must be the best
Ok, let me sum up some of the best practices I know:
1 Don't waste your time step into the code line by line.
2 Use whatever technology that is popular.
3 Who cares about what the users want, deliver a whole system/framework anyway.
4 ...
My articles and software tools
|
|
|
|
|
|
Of course the options are all important aspects of good programming... as are maintainability, elegance, good design, etc...
But ultimately, isn't the single most important thing that - it works? Does the code do what it was intended to do? Does it satisfy the need it was intended to satisfy? Even if it isn't the most elegant - or for that matter, the most maintainable (shuddering even as I write that, as anyone who has had to maintain someone else's poorly designed code probably would) - ultimately, it has to do the job it was intended to do.
|
|
|
|
|
It's fine to say that the code does what it was intended to do but generally I find that not enough effort is put into making it easy to use, read and understand for the next guy who's job it is to expand on it or retro fit it to another application and that no consideration was given to the future of the code so when the next guy does have to modify or re-use it they end up having to re-write it anyway which in the long run ends up costing more time and more money than if a little more effort had been put into the job in the first place. So I think that this idea of just getting the job done should be avoided at all costs.
|
|
|
|
|
Gavin wrote: So I think that this idea of just getting the job done should be avoided at all costs.
Hi Gavin. You may have misunderstood me. I'm not advocating "get the job done" as the only consideration - far from it. I much prefer elegant, maintainable code, based on solid design principles... as I mentioned, all the options in this survey are important to good software development.
The point I was getting at was - if one were to eliminate everything but one thing and consider it the most important - how could it be anything but it works? Software developers are hired to write software that works. I think most employers would prefer unelegant software that works to elegant software that doesn't work.
|
|
|
|
|
...and delivering what the client expects and beyond.
I believe, within a couple of years, computers will start writing codes themselves when provided with business logic alone. So, the success will depend upon how quickly we can understand the operations of client.
Exposure to different cultures and countries, exposure to business, client handling capabilities, requirement study, analytical power, ability to find quick solutions for client etc. will take the place of ability to study new computer languages and technologies, remember different syntaxes, taking certifications in various languages/technologies, writing codes based on a VSD diagram etc. etc.
|
|
|
|
|
Madhu Kampurath wrote: Exposure to different cultures and countries, exposure to business, client handling capabilities, requirement study, analytical power, ability to find quick solutions for client etc.
These are all important now!
But what is also important, and likely to continue being important, is the ability to prioritize and implement requirements, choose and use the best tools for the job, and to design and implement solutions that are clear to, and easily maintainable for, others.
At the end of the day, it doesn't matter if you're coding up biz logic in C++ or a specially-written inference language. Either you're clear on your intentions (and all will be well with you and your successors) or you're winging it (and you will suffer for your sins).
|
|
|
|
|
Madhu,
I think this is addressed by the point "Value for money to your employer / customers".
A significant improvement in this perspective means meeting and exceeding client expectations.
Is'nt it?
Vasudevan Deepak Kumar
Personal Web: http://www.lavanyadeepak.tk/
I Blog At:
|
|
|
|
|
I checked this with a bit of uneasiness. There is a kind of expression that delights in making the most of opportunities, and another that relishes abusing them... and i cringe at much of what results from the latter. I've seen code that has left me amazed, filled with awe at the author's method of producing results in the face of limitations that had left me sure no elegant solution could be found. But i've also seen too much code that relies on tricks and self-serving cleverness, when the simple and obvious solution would have sufficed.
As for the rest... Innovation is nice to see, correctness is almost always key, attention to detail can make the difference between a useful once-off routine and one that can be used and re-used for years... Value is always a consideration, but exists on a different level for me; I can no more take value into account while programming than i can effectively edit a letter while writing. And i cringe every time i hear the phrase "Best Practices". Nothing wrong with the concept itself, but it's been used so often as a crutch or an excuse... ugh.
Heh, and looks like the controls usually in place to reduce abuse on the "Other" entry were disabled for some reason. 
|
|
|
|
|
Coding is like graphic design. You can either make great beautiful murals, or mass produced simple, concise street signs. It's graphics none-the-less.
Some people aren't concerned with challenging themselves to learn a new algorithm, API, or other programming technique; just want to get the job done. The problem is just-get-it-done code could be really ugly and unmaintainable.
I say it takes a skilled craftsman to hone the techniques over the years to take it to the next level.
---
Shawn Poulson
spoulson@explodingcoder.com
|
|
|
|
|
I agree, and would also like to mention the "most important aspect" of programming depends largely on the scope and environment of your software project.
In my line of work (writing software for a major corporation), following best practices is the most important rule of thumb (in my opinion). It's pretty much a given that other developers will be enhancing and/or fixing the code you write, so it's very important that standards are defined and followed. Otherwise, the cost of maintaining and enhancing applications spirals out of control until it becomes impossible and you're forced to scrap your application for a third-party app. That could mean that your position is no longer needed within the company and is eliminated.
However, if you are writing code solo or in a small group, I could see how following best practices would not be nearly as important. Focus could be on innovation or experimental methods of coding depending on the level of risk.
|
|
|
|
|
I agree, as well. Sometimes you have to put away the geek cap and adopt to whatever shop you're working in. If they want a Perl/CGI solution, don't give them ASP.NET because you think it's best. Sometimes you have to stop being bullheaded about what is best in your opinion and go with what was approved. Taking this wisdom with you will open your mind to great new technologies out there that you would never have considered otherwise. That is a mark of a good coder.
---
Shawn Poulson
spoulson@explodingcoder.com
|
|
|
|
|
Few programmers are software developers. Programmers know how to solve problems. That is, get from point A to point B in code. However, coding should only take 25% of the time. Software developers make sure that the code is actually what the user wants. Achieving a user's goals should be 75% of all efforts. In fact, for the software developer, coding is almost a non-existent issue.
There is a C++ book that covers this and many related topics in an effort to convert programmers into software develoeprs. The book is called "Safe C++ Design Principles"[^].
|
|
|
|
|
River One wrote: In fact, for the software developer, coding is almost a non-existent issue.
Yeah but the problem is that since 100% of all bugs are code related, the code tends to become a big issue if it's not properly developed and tested before it's delivered to the user.
Alvaro
To announce that there must be no criticism of the president, or that we are to stand by the president right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
