Writing organized, readable code. If you want to write code then readability should be your number 1 priority at all times. This is an ongoing process that never ends, partly because people have differing styles. We can't even agree on where to put braces or whether to use spaces or tabs! Still, it's critical that you write code that at the very least you can read — six months or more after you wrote it!
The single biggest and most frequent mistake we see beginners make on this site is trying to "just get it to work" instead of worrying about readability. Give me readable code that has a bug over sloppy code that works any day of the week! I know I'll get that readable code working easily, but when I have to make a change to the sloppy code (and it always happens) I'm going to regret ever using it.
How often do you use an engineering model apart from trial and error / code patterns to develop your applications? For instance hypothetically, you are developing a web application with a database back-end and know that your web application will be accessed by thousands of clients at the same time (hypothetically the web application becomes live at a certain time). Do you sandbox these things and strength test server load? Apart from the regular safety nets in place for code control and quality, how are these things tested?
Patterns can help with readability. See above.
Test everything. Assume you have bugs until you prove you don't.
How often do you see mathematics used throughout software engineering that isn't in gaming, but rather for code optimization? When designing algorithms that are applied in real world applications, do you find a firm grasp of Number Theory helps to optimize algorithms, and when openly discussing mathematics are you often greeted with blank faces?
Math is in everything.
Let's say you're at a interview for a job and the interviewer asks you to make examples of bad and good software and explain. What would you say? (Would interpret it as a trick question, or give the answer?)
Good software is well organized and readable. Bad software isn't. Never try to prove how smart you are by writing complicated code. It shows the opposite.
Did you pick up coding style from the people you worked with or some other way?
Yes. Style is both personal and general. Think of programming as an art form, like music or writing books. You're bound to have your own personal style, but that style should and will be influenced by the larger group.
Again the situation when you're on a interview. If the interviewer asks you what was wrong in your previous job post? (Would you risk of revealing some firm secrets by answering that or would you avoid that question somehow?)
It could have paid more. They can always pay more.
How much of your current knowledge did you gain at your work post?
Hard to say. Unlike many, I think that most jobs don't challenge you as much as college. On the other hand, the job is focussed on one area where college focussed on many. In any case, you should always be learning. Even outside of your job.
Most of you have been in the industry for some time now; some for a longer period than others.
My question is: do you still find yourself motivated to go home after work and learn some technology related things outside of work, or is it more of a 9-5 job now for you and just do it for a paycheck.
Heh, I spend too much time on this site, so that should tell you something.
How do you guys make it so that the job remains exciting.
When you aren't learning you get bored. If you get bored, find another job. Maybe an additional job, or maybe just a new one. Either way, you'll find something to keep you going.
In your corner of the industry, what differentiates an experienced programmer/hobbies from a professional?
The quality (readability) of their code. Whether you want to be a web developer or a mathematical modeler at some point you're going to have to edit code you wrote months ago or longer. That's where hobbiests run into trouble.
Since you started programing, what has been your favorite project, personal or work related.
Any project where I feel I learned something useful is my favorite at the time. I never want to find myself writing the basically same project I wrote a while back.
Are you guys participating/used to participate at open source projects? Why did you do it/are doing it? - sense of achievement, getting better at programming, boredom?
A few minutes answering question on DIC during the day is about as far as I can go. Open source projects would need too much time.
What is your opinion in regards to the authenticity of the Tiobe index? Is it a reliable source to use to determine which language is the most used/popular?
Don't think about languages. Think about writing quality code.
Do you find that you are happy with your line of work? If you could change to some other (realistic) line of work, would you?
Yes, I'm happy with it. That doesn't mean I wouldn't consider something better if it came along.
How do you guys use your programming languages for your company?
I write code for mathematical models of disease progression and transmission.

New Topic/Question
This topic is locked




MultiQuote







|