 |
|
|
Are you enjoying the job assigned to you or you forced by someone to being in this field?
|
|
|
|
|
|
|
I was born to design and code! 
|
|
|
|
|
|
|
|
|
|
Yes I very much enjoy writing code. The best part is starting a new project of my own. I am right now doing just that. 3 weeks ago I started a project that will be used to run radiologists reading studies of multiple modalities. I had done single or dual mode studies in the past several times but this time the program will have to be much more flexible in its design. Instead of all the code in 1 application the image viewing workstation in several modalities will be the same viewer that doctors normally use to read cases. This takes some work away from me from having to emulate the visualization of clinical machine but then adds extra work since I have to be able to have these clinical systems bring up the case I want and also since none of these have a reading mode all scoring (marking suspicious regions, cancer ratings ..) has to be done on my displays so I still have to display the 2D or 3D images but only at a most basic level. At this point my project has 11K lines of new C++/Qt code that I have written in the last 3 weeks. I suspect it to be a 50K to 75K project when it scheduled to go live in March of 2010.
John
|
|
|
|
|
|
|
Mr Drescher..Quite Intresting..How long you are being in this firm
|
|
|
|
|
|
|
Since May 19, 1997. We are a small research imaging/cancer research team at the University of Pittsburgh. Right now I am the lead programmer of a team 2 programmers and I am right now looking to add a third.
John
|
|
|
|
|
|
|
Message Automatically Removed
|
|
|
|
|
|
|
I am sorry, but I have enclosed myself in a try-catch block so I cannot throw any exception at you. Maybe someone else has more patience. 
Greetings - Jacek
|
|
|
|
|
|
|
What kind of research?
How did you or your manager justify the time and cost or research or refactoring to upper management?
|
|
|
|
|
|
|
Management does not want time used for research or refactoring. So, such work gets wrapped as an enhancement to maintainability or feature improvement.
|
|
|
|
|
|
|
Management never has a clue what we are doing unless we tell them. Our product line is ten years old dating back to DOS versions, and refactoring is a constant in order to continue to port to newer compilers, operating systems, and interfacing software. Without research, you can't determine what 3rd party objects are available to shorten the development cycle... shoot, without 'research' how are you going to figure out how to fit to Vista, Win7, 64-bit versions...etc?
If management wants a product that does X we have to figure out what that costs, and predicting the development cycle impact on any product over 100k lines of code cannot be done without research. Pay the piper, or accept schedules with plus-or-minus factors in terms of months. Do the homework, or expect to start documentation and advertising when the product is completed due to lack of planning...'research'... and move to market two months too late.
Management has alternatives, costs, and choices. If they are briefed as to costs of trying to work in the dark, without research, they will make the right choice... but only if the development team can trust them enough to tell them what they are up to and are respected enough for their skills to be heard. If management is too dim to accept that, you need a new gig.
|
|
|
|
|
|
|
My last project began as research -- the company knew they needed a system to do X, but didn't know exactly how it could be accomplished. They hired me to try out a few ideas they had in mind. In the end, none of the ideas they had worked properly, but we were able to find others that did.
I wouldn't work at a place where I couldn't do research.
|
|
|
|
|
|
|
A lot of what I do is research-based. That's the engagement -- I'm the one they call when they want to do something nobody else has done (as far as they know).
|
|
|
|
|
|
|
How do you perform core development without researching and refactoring. In my opinion, its just part of the development process.
Joel Palmer
Data Integration Engineer
|
|
|
|
|
|
|
That's exactly what I was thinking.
-----
In the land of the blind, the one eyed man is king.
|
|
|
|
|
|
|
Part of the job actually. Sometimes it's necessary and cannot be avoided. So research it is. Sometimes it's better to spend a week in researching and writing a lib, that can be used later, instead to rush and start with the coding right away. Refactoring is also important as it will cut the maintenance costs later. Every system soon or later reaches a critical point and needs refactoring or else the time required to implement simple changes will be taking too long. If some manager cannot understand this he/she obviously has absolutely no clue about developing software and does not deserve to be a manager in a software development company at all and should seek a manager position in McDonalds!
|
|
|
|
|
|
|
I agree with everyone research has to be done. Development without research is at least one definition of crazy (isn't that the same thing as doing the same thing over and over expecting a different result). 
|
|
|
|
|
|
|
In my last cmpny.. I was involved in research only as the client withdrew the project
due to recession... 
and that too in two projects!!!
|
|
|
|
|
|
|
Upon writing the new software, I have learned some new things about programming. After completion, I went back to my previously written software and have performed major refactoring, which enables the improvement in speed to interpret large files of data and the application performances.
|
|
|
|
|
|
|
|
|
|
I work at a research institute... I have to work hard to justify doing real work.
|
|
|
|
|
|
|
I actually have to support and train software that I create/maintain. This probably consumes about a third of my time. Another third goes to coding, and the remainder to documentation, research, reading web blogs about the industry, or golf, depending on the weather. Having to provide front line customer support and training has definitely shaped the way I approach the development and testing roles.
|
|
|
|
|
|
|
In this project, I continue developing new features in the Framework of our application, but right now we are implementing the BI technology 
luisnike19
|
|
|
|
|
|
|
we always rant about lack of documentation and how management doesn't support unit testing, and yet "documentation" and "testing" are conspicuously missing from this list.
I guess we developers really don't give a damn about them either. I always thought so, I guess it's time though that we fess up to how we really feel.
Marc
Will work for food.
Interacx
I'm not overthinking the problem, I just felt like I needed a small, unimportant, uninteresting rant! - Martin Hart Turner
|
|
|
|
|
|
|
Marc Clifton wrote: we developers really don't give a damn about them either.
Leave alone the full-fledged documentation at least the developers should get into the habit of writing at least a one-line comment for the methods to save the posterity and they should cultivate the habit of refraining from commenting code blocks and depend on source control for saving alternate implementations.
A tougher enforcement besides a corporal punishment to the manager heading such a developer alone would bring a good discipline.
Vasudevan Deepak Kumar
Personal Homepage
Tech Gossips
The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep!
|
|
|
|
|
Suggest a survey
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Rant 
Admin