|
Those people need their head examined!
|
|
|
|
|
 ;PAre you a genius or something?
Saif
Peace for life
|
|
|
|
|
What is your profession because i heard you are a champ at computers is that right??
Salman
|
|
|
|
|
My favorite part is coding it. It feels really good after I get all the design problems taken care of and I start smashing out those algorithms. The feeling of successful progress is very motivating and satisfying.
█▒▒▒▒▒██▒█▒██
█▒█████▒▒▒▒▒█
█▒██████▒█▒██
█▒█████▒▒▒▒▒█
█▒▒▒▒▒██▒█▒██
|
|
|
|
|
I prefer the "invoicing" phase myself.
|
|
|
|
|
I prefer cashing the cheque
You may be right
I may be crazy
-- Billy Joel --
Within you lies the power for good, use it!!!
|
|
|
|
|
PJ Arends wrote: I prefer cashing the cheque
True. I've invoiced and not received payment for several months (college/university moves at a very slow speed).
--G
|
|
|
|
|
|
This survey is overly centered on one single class of development work "Business data access applications", i.e. applications that run on top of a database, a business logic layer and then some user interface on top. Things like accounting, payroll, e-commerce and things shoehorned into the design model of those tasks.
But there is a lot of development out there which cannot be reasonably viewed or understood in that narrow frame of mind. Most codeproject.com featured articles are complete developments that don't fit the model. Implementing the Windows operating system, office, SQL Server, Visual Studio or any of their competitors don't fit these models either.
Sure, one can stretch the concepts listed in the survey so far that they *could* be misused to describe things beyond their world, but that doesn't really make sense unless required by law or contract.
Over the years I have seen thousands of projects that insisted on using the "Database-centric" tools and concepts for tasks that would have been better off without them. At least half the CMS based web sites in the world are glaring examples .
Database-centered development is the job and skill of millions of developers, just as COBOL based development was 30 years ago. But it is not, and never was, the entire world of software development.
This message is hasty and is not to be taken as serious, professional or legally binding.
I work with low level C/C++ in user and kernel mode, but also dabble in other areas.
|
|
|
|
|
So, what keeps you coming back to it? What keeps your love alive? Or is it just a job? Got bills to pay.
This statement was never false.
|
|
|
|
|
OK, so
a) I should have added "None of the above because these don't fit me"
b) Give me another list and we'll do this again some day
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
Though i gotta say, i hate the term. What, like someone's just handing me the data in a nice little package... Huh. If your idea of a UI is spewing out a big pile of data-bound fields and relying on help text to get the user through it, then i don't want to ever use your app. If your "presentation layer" doesn't include a crunchy "beating the data into submission" layer sandwiched between a tender layer of dodgy statistical analysis (to "calculate" data that the sappy DAL folk didn't think to pass on...) and a layer of tangy rendering goodness... well, shucks, ya just aren't tryin'. 
Also good: Design, Testing, Tweaking...
Also bad: DAL, Deployment.
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
|
|
|
|
|
More people choose bug fixing than testing.
<font=arial>Weiye Chen
A self proclaimed hermit living in a cave, with his PC connected to the world.
|
|
|
|
|
I did. Its more fun. Its more of what keeps me coming back. The challenge of fixing something. Kinda the reason I started programming was the attraction of solving puzzles. Testing doesn't hold that same attraction, its busy work. Necessary, but busy.
But, I see your point. Just the poll is about the lure of dev, not the required bits.
This statement was never false.
|
|
|
|
|
As far as I'm concerned, the most exciting part of development is the very beginning when a need is recognized then followed by the "aha!" experience when a conceptual solution is visualized.
The next most exciting part is when a user of the developed concept talks about how "their system" successfully does whatever it was supposed to do.
Everything in between is grand but the above two points are the best.
Mike
The NYT - my leftist brochure.
dennisd45: My view of the world is slightly more nuanced
dennisd45 (the NAMBLA supporter) wrote: I know exactly what it means. So shut up you mother killing baby raper.
|
|
|
|
|
I had chosen Architecture, Data Access Layer, and Bug Fixing and tweaking, but that's mostly because I was focused on those checkboxes.
I agree wtih you 100%. I hadn't thought about it at first, but there's a real exhiliration from figuring it out, and seeing the results with the customer, beit common user or fellow dev.
This statement was never false.
|
|
|
|
|
It's just some of the people that you encounter that I would happy to do without. 
Marc
Thyme In The CountryInteracxPeople are just notoriously impossible. --DavidCrow
There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer
People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh Smith
|
|
|
|
|
This is what it's all about (in most business applications). All that presentation layer, GUI design, bug fixing and testing has only one reason: To feed the right data to the data access layer and get the right data out of it.
I love windows services. Service programming is great, because I'm down low at the data acceess layer, I don't need to care about how to communicate with the common user ... all there is is the clean, unformatted, real information. A place for developers, free of beautiful-looking facades and user-readable error messages. 
____________________________________
There is no proof for this sentence.
|
|
|
|
|
It's just great fun creating tool library components. Beside saving all the work of redesigning a useful interface/class/control/algorithm, there's the challange of making it as smart and bullet-proof as possible.
Which leads to a useful (yet missing) category: developer acceptance.
If another developer adopts one of my tools, I really feel like I've done something worthwhile.
A broader term, suitable for the survey, might have been 'Recognition and Acceptance' (the survey seems obsessed with two-item types). Not in an egotistical sense, but in the sense that it is an affirmation that what was done was done well and for some purpose.
Ego feeding? That could also have beeen a choice. I get that from two sources: a reputation of "that guy's apps work" from users - when they go month after month without a glitch. The other is from an anecdote: My now-former-employer let me go (after 9 years, with 2 weeks severence pay and no warning) to replace me with someone who, they claimed, codes faster. The said he had done in one year what had taken me two. It's now over three years and they're still selling my app, with a few tweaks added on. But the ego boost? That came later. I discovered they had to hire (as in ADD) a second programmer to try and get the job done. Some of the best fun you can have with your pants on . . .
Balboos
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
|
|
|
|
|
I looked for options saying "designing and building something I know will be useful in my next project as well as this one" or "making use of work done on previous projects to shorten development time on this one" but missed them both.
I suppose "tools" is as near as I'm going to get.
Brian
----@
|
|
|
|
|
Mostly because I am an odd ball in development anyhow. Most of my work is within the presentation layer, because 3D graphics is all presentation. I prefer R&D work, doing what has not been done. Repeating easy to do stuff doesn't interest me in the least and will put me to sleep, sometimes litterally. It doesn't matter if I am debugging a complex simulation, designing a new data flow, or rendering FX, if I am doing it as part of a larger "this has not been done" project, I love it all. The more on the cutting edge I am, the happier I feel.
So I put presentation layer because my main project lies completely within the presentation layer, but really they all apply, it just depends on the scope of the project.
_________________________
Asu no koto o ieba, tenjo de nezumi ga warau.
Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
|
|
|
|
|
?!
Developers, Developers, Developers, Developers, Developers, Developers, Velopers, Develprs, Developers!
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
Linkify!|Fold With Us!
|
|
|
|
|
I think that option is split out in to the various layers.
|
|
|
|
|
Not really.
Whoever wrote the poll assumes that everybody is writing business application software.
I don't have any Data Access Layers, Business Logic, or Presentation Layers in my projects.
|
|
|
|
|
ed welch wrote: I don't have any Data Access Layers, Business Logic, or Presentation Layers in my projects.
Really. What layers do you have?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
