Discussion on:

10 signs that you aren't cut out to be a developer

I know exactly what you mean. My "hobby"programming has always been more interesting... and more advanced than my professional programming. In fact, I have found that it is the code-level skills learned in "hobby" programming that impress at the job interview, not the "how to hook yet-another-database-to-HTML" which comprises most "professional" computing!

J.Ja

With regards to commercial code generators, you are correct -- most suck at anything other than the most basic code.

That said, however, when you are doing the same mundane tasks over and over again, why not write your own code generator? Then it will generate the code you want it to generate.

This can be as simple as an Excel spreadsheet that you use to "generate" repetitive lines of code with only a few variations. Or, it can be something as complex as something that connects to a database, reads the field information about a table and builds an entire screen (or web page) from that information.

After all, if you build the generator, you are in total control of the code it generates.

that I was talking about using out-of-the-box code generators. I agree that writing your own code generator is useful if you are doing a lot of same type of code. Also, for UI development using the IDE's code generator for creating the controls can be useful. However, relying on the code generator to hookup the data links for those controls can be fraught with problems.

You're right. I remember back when I was just coding for fun I would do stuff I needed a program for to do something else, or just play around with some interesting stuff and add ideas of my own.

Now, it's whatever the boss needs. And while most of it is interesting, there's also an element of you really have to get this finished. There's been some projects put on the back burner but none abandoned. When you're coding just for a hobby, you're free to forget about a project altogether if you don't feel like doing it anymore.

But I luckily I haven't come across a work project I didn't want to do. I guess I'm one of the more fortunate ones.

As for IDEs, I discovered that quickly when I started using Visual Studio 2005 and programming database-driven web sites. Often you'd have to tweak the code for the database stuff.

I have completely stopped using Visual Studio's database tools, and the .Net databound controls. They have done nothing but cause me misery. Unless you are hashing out something dumb, like the stereotypical CD collection app or recipe app, they just get you "stuck", and when you need something custom, it sticks out like a sore thumb.

J.Ja

One of the most regular DB application questions on this site is with my databound control, how do I do this.

Sometimes you can, but it usually turns into an unmaintainable kludge.

You lose control, and you lose granularity, which explains how bloated and inefficient they are.

I have to say I am torn when it comes to IDEs/code generation. On one hand, we get paid to do a good job, and IDES/code generation tools can definitely save some time (which translates to money). On the other hand, developers tend to "disconnect" from their applications and what is going on behind the scenes. Developing not only involves making something that works, but also being able to fix any problems and/or improve performance, and that can only be done by knowing the inner workings of the underlying technology. I know many people out there who are using tools like VS 2005 with ASP.NET or what have you to design sites and don't have the slightest idea of how the compiler works, or why their application is running so slow. All they know is drag and drop on the design surface and boom, the page is connected to the database. I mean honestly, just think about it, how many of us have grown so accostumed to intellisense that if you are to code something manually, you probably don't remember half the methods of a .NET GAC assembly class, lol....
I personally am an old school guy and even though I do take advantage of some of the features of the IDE, I try to code as much as I can by hand. This way I have full awareness and control over my applications at the same time that I make sure my knowledge is up to date without having to press F1 every 10 minutes to try to remember what a method does.
As far as hobby vs professional, hobby is definitely more fun. You can learn more advanced stuff on your own and use it for future jobs. The only problem I personally face with hobby programming is that I never finish what I start!!!, lol... I always find something else that sparks my interest and leave all sorts of projects behind, lol...
I sux

I'd say about 1 in 1000 software people have all those great qualities. That's probably why most systems everywhere are in such horrible shape.

So, don't let a failing grade on this checklist discourage you. Just jump right in and join the crowd. That's what most developers do because they have no idea what else they'd do for a living.

Like, dude, you need to know the right paradigm for generating verbal signals when interfacing with us in audio mode. You expect us to grok your thoughts??? I have an idea -- CAT-5 brain implants so we can FTP over TCP/IP our thoughts directly. Of course that means we need to clarify who is the domain controller and whether the other is a member server or a dumb terminal.

Perhaps we can do better with ASCII files run through the 'more' pipe. Maybe if we used HTML e-mail via 802.11g. Then again, what about an RPC via SOAP over TELNET?

Okay, I've officially scared myself with the above, which is fitting since today is Halloween.

Now to get a bit more serious.

The best developers (as opposed to code-grinders) need to be able to communicate with normal people. This means either avoiding the technospeak altogether or else teaching them what a given term means when you use it. This is essential for requirements gathering and "selling" your proposed solution to management or clients.

These same "best developers" can turn around and, if necessary (but hopefully it isn't), spout out the technobabble that the code-grinders need to hear in order to do their coding.

Okay, I can't resist one more technospeak item

Now it's time to CTRL-Z

You forgot one: If you fail your college programming class [C++] two semesters in a row.

And #11: You just got hired by Microsoft as a development team leader. (You must fit all 10 above to qualify for #11.)

Well written and accurate. Thanks for keeping it real.

Doesn't matter I can't get a job doing it anyway.

So far most of your ideas are well... not common. Let's take one of them, I love to watch an employee waste tons of time chasing their tail trying to learn something on their own and point this out to the employer and the fact that I learned to do it in an afternoon going to a class. Also, the type of person that is so dogged usually doen't work well with others in most ways and will keep beating a dead horse as you allude to again and again. Another trait that most employers don't like no to mention co-workers. These endearing traits probably are the reason programming is not on most people's to do list, even if they have the ability to do it.

nt

I have done the whole 2 month 10 to 12 hour days thing and ultimately it's not worth it. I feel like the more that developers make this the norm, the more it becomes standard practice in the industry. Then of course if you want to be the guy who goes home at 5 or 6, then your considered a slacker.

Clearly I expect to work late hours sometimes (deployments, server crashes, smaller client emergencies) but I think all developers in the industry should not let themselves become 60+ hour workers (ie your lack of a personal life and work compensating for that is bad for the industry in general... If you make it a norm). I especially feel like young developers (like myself) are expected to do these long hours just because we have the energy to do so.

But let's remember that programming is an art to some extent and we all love writing good code but when you kick the bucket, it's ultimately going to be your friends/family/lovers that matter, not the business layer you spent 3 or 4 months of your life slaving away on.

Are there developers out there who didn't major in Computer Science, Math or related degrees? Sure. But the line of demarcation becomes painfully obvious the more complex the software need gets ... and it is sure obvious where best practices are concerned. Straining the limits of computer science is still a top-10 software risk. The right academic background helps to eliminate that.

iv done my engineering in computer science wid a pretty good knowledge bout most of the subjects .........but iv got no interest in coding but iv good communication skills.........is der a job profile which is apt in a situation like mine.........

Why does every programmer and or developer, even this site say you have to self teach?????? WTF!!!!!!! I can try and teach myself PHP like I have been for the past 3 years still dont get a THING about it!!!! NOT ONE!!!!! Plus why even go to school or get educated at all??? Just teach your self and dont do what the internet was intended for like SHARE INFORMATION!!!!