Posts Tagged ‘programmers’

I’m wondering how programmers develop new web programming languages because I want to learn how everything begins from the start. Let’s say I’m planning to write a new language for the Web. How do I do this? Is there anyone who knows about the way web programming languages first appear ? I’m asking these questions because I’m particularly interested in the World Wide Web.

I am busy studying for programming and now i have the choice of either choosing C#,C++,VB.NET or java as a programming Language.Which one of these is the best to do and which one will get you a good job,im planning to go to America or Canada after my studies.What are my chances of getting a programmers job there and which language is bery popular in these countries.Thanks

This is a quick feedback survey to find out what programmers would like changed/innovated to make programming faster and easier. What specific software development tools would you like that don’t currently exist, and specifically what features?

In a large organization, programmers develop a library of classes as they work on various projects. Discuss, in such an environment, how inheritance can be useful in reusing code and therefore saving time.

Almost any programmer can tell you that the bugs that are discovered in their software can be numerous. At times it is difficult to keep track of them all. A company can reduce the possibility of an issue getting lost among all of the other issues if they incorporate bug tracker software into their business. Bug tracker and issue management software can lead to higher productivity and lower turnaround time for issues that may come about.

Bug Tracker software provides a means of organization to many different companies. Programmers have the ability to log any issues and problems that arise using the software. Each change or adjustment that is made is logged and stored in one place so any one of the team members can access the information and see when the bugs were reported and when and what changes were put in place.

If there are a team of programmers working on different parts of a particular implementation but they all need to coordinate in a timeline then the bug tracker software is the answer. Each person should monitor their progress and frequently log updates or close their portion out when it is complete. This will keep them all aware of the pace that has been set and if they are behind or ahead of schedule.

They will be functioning as more of team as they work together to get the end results that are necessary. After this software is put in place, things will begin to work much more smoothly as people will be working at the same speed to develop and implement new products or ideas.

Another benefit of the issue management software is that if a bug is discovered by one group and they make a change to correct it which causes problems in another area, tracking down the change that affected the other area will be much simpler. By just reviewing the changes that went into effect that day they will be able to narrow down the contributing factor to the second issue. This problem can be resolved fairly quickly and the programmers can move on to the next hurdle that is in their schedule for the day.

By evaluating the issue management and bug tracking software, the management staff can also notice trends and identify possible areas of concern for the company. If they realize that they tend to always have problems with a certain line of product as soon as it is released into production they can make the necessary changes at that time and eliminate the need for problems in that area in the future.

If the problem tends to be with a particular employee and their performance at the job, the Management staff may be able to identify this as well. Each of these discoveries can be made in a reasonable amount of time as the reports are generated and the files are reviewed. If there is a problem in any reported area, the management staff will have the tools that are necessary to get ahead of the problem and find a solution as quickly as possible.

Author: Johnathan D. Smith
Article Source: EzineArticles.com
Provided by: Canada duty tariff

I am looking to find a PHP programmer to help program a website. I advertised in Craig’s list and other places and have a large number of resumes. I am not a computer programmer, and have very little knowledge regarding programming.

What sorts of questions should I ask to help me determine if the people we are interviewing are indeed good PHP programmers?

Thanks!

I read an article recently about “writer’s block”; the problem writers have on occasion when they just can’t seem to figure out where to start on their current project or what to say next. In the article, the author commented in passing that the problem of “writer’s block” seemed to be unique to the writing profession; that people in other lines of work such as architects or programmers or musicians didn’t suffer from that malady.

That got me to thinking. Having been a programmer for many years now, I can guarantee that I’ve experienced the equivalent of “writer’s block” on numerous occasions. In my case, the “blockage” usually centers around how best to design a new piece of software or how to proceed when I run into problems with the way I’ve built some part of the application.

Getting started is almost always traumatic to some degree, unless you’re designing a software package that’s very similar to something you’ve done before. Even after gathering as much information as possible about the program(s) to be written, it’s still difficult to decide on the best way to design the system until you’ve created at least the beginnings of a working model of the software.

And even if you get started in good shape, then comes the inevitable list of items you overlooked or didn’t fully understand, combined with the changes and additions requested by the end user. If that list gets too large or too complicated, it’s easy to lose your way. When you reach a point where you can’t see clearly how to proceed, you can even begin to feel like your whole approach may be wrong and you might be better off to scrap everything you’ve done and start over. You’re just not sure what to do next — bingo, “programmer’s block”.

So, what can you do to avoid or at least reduce the chance of running afoul of “programmer’s block”? Let’s take a look at the tips given to writers to overcome this obstacle:

1. “Make at least a rough outline before you start; that way you’ll always have at least a guideline to fall back on”:

   Most software projects have an “outline”, whether it’s called “system specifications” or “the project plan” or something else. I have worked with specifications that were an almost exact blueprint for creating the software — however in my experience that’s the exception, not the rule. If a detailed specification even exists, it’s usually no more than an educated guess as to how to design the system. It doesn’t get into the nuts and bolts of building the software and that’s where “programmer’s block” normally occurs. The main value in a set of system specifications is simply to remind you of what has to go into the system and what needs to come out. How you accomplish that is always subject to change.

2. “Loosen up; forget the deadline and the assignment”:

   This one’s not usually an option. In fact, one of the biggest problems for most programmers is the pressure to meet pre-set deadlines regardless of changes, rewrites or other problems. If you’ve been working non-stop for hours though, it can help to take a quick break — get up, walk around, try to focus on something else for a few minutes.

3. “Switch to an easier project temporarily”:

   Working on some other program that doesn’t give you a headache is a good idea. It relieves some of the stress and gives your confidence a boost. The problem is the same as for tip #2 — you may not have the luxury of taking time off to go work on something else. Deadlines keep coming up regardless of how stressed you might be.

   One trick that can help is to take a look at other programs that perform functions similar to what has you stumped. Sometimes just rummaging through other software and glancing at the way it works can give you an idea of how to attack the problem you’re hung up on. Even if the programming language is different or the software is written for a different platform, the basic approach used in designing the system may spark an idea.

4. “Talk the assignment over with a buddy, your dog, or an imaginary friend”:

   For software developers I would add another option — ask for advice on your favorite forum. How much good this will do you is debatable. As a rule no one else is familiar enough with what you’re working on to be able to provide much help (even if they have the time and inclination). If it’s just a matter of your code not working correctly though, forums can be a great place to get some assistance.

   In the end, the person best suited to help you is you — and sometimes just pacing back and forth and talking it over with yourself has been known to bring forth a solution to the problem of the moment. A word of caution however — you should probably do this in the privacy of your own office or, if you don’t have an office, find a vacant stairwell or an empty breakroom. People who spend a good deal of time talking to themselves tend to make those around them a little bit nervous.

5. “Change your writing environment if necessary”:

   If your environment is a problem, if there’s too much noise and confusion and you’re having trouble concentrating, lock yourself in the restroom, hide under your desk, or do whatever you need to do to get some quiet time. When you’re really focused, things seem to flow out of you in an organized stream like an assembly line. Constant interruptions can cause you to lose focus and suddenly your assembly line goes haywire. You lose track of where you were and where you were planning to go, and it can be a major struggle to get re-started and back on track. It can even lead you to make hurried decisions that take you to a dead-end and leave you wondering what to do next.

6. “Quiet your inner critic — the voice that tells you that nothing you write is good enough”:

   I’m willing to bet that most software developers have an “inner critic”. I know that I do, and it can bring me to complete halt if I let it. There are times (especially if I’m working in an area that’s new to me) when no matter what I come up with, that voice is talking to me, telling me that what I’m doing is amateurish and poorly constructed and is never going to work worth a hoot.

   The only real answer to that inner critic is to slog ahead, check your work, and do the best you can. Software development, like writing, doesn’t just come naturally. It’s hard work and the harder you work at it and the more of it you do, the better the result. No one’s perfect and there are going to be mistakes and things that could have been done better — catch as many problems as you can as early as you can and make lots of notes as to how the system works so changes and additional corrections can be made later.

There are a lot of other answers to avoiding “programmer’s block”; peer reviews, rapid application development techniques, books on best practices. However, if you do get stuck, maybe the best tip is simply to remember that you’ve been there before and survived — and you’ll survive this time too.

Author: Paul Love
Article Source: EzineArticles.com
Provided by: WordPress plugin expert

As a programmer, I am impressed by the quantity and quality of open source software products. A couple of the best ones I’ve personally used are: jEdit and FreeMind. I support the open source concept, but am concerned that it negatively impacts programmers’ income potential. Becoming an open source consultant would probably be the best way of making a living from writing open source code. How else can a programmer make a living from open source code?
Some additional questions… Can one legally repackage and resell open source? Are there standard types of open source licenses?