Professional Programming questions

[Cogman]

So, I am still a college student, and an Computer engineering major at that. However, I took a class with someone who was impressed by how quickly I got answers ect. Anyways, he approached me with a job offer that he was offered, said it was part time and like 5 hours/week.

Here's the thing, the job will require some data base programming capabilities (something I've never done), and it will be my first job somewhat in the industry I am shooting for.

So my questions are.
1. How hard is database programming? Any suggested reading? I have already informed the employer that I don't have experience with it, but I am willing to learn. (from what I gather, it will most likely be MS Access. However, this is a startup company so I might be able to bend it towards a SQL database)

2. What should I be asking as far as pay goes? Obviously I'm inexperienced as far as professional programming goes. A rough guesstimate would be great. (or what I should consider when guesstimating)

Really right now I am just stoked that he approached me with the job opportunity. It is nice to be noticed

 

[imported_Dhaval00]

Depending on your definition of database programming, you can categorize the skills into niches. There is the DBA, there is the DBA programmer, there is the business intelligence developer, etc.

Conventionally, a DBA is tasked with monitoring and maintaining multiple solutions (these could be a mix of DBs, security, indexes, architecture, etc.).

A DBA programmer, IMO, is someone who knows the basics of SQL, but at the same time is not tasked with a conventional DBA's tasks. This is an individual who most likely works on the front-end, might be involved in writing basic functions, stored procedures, etc. Specifically for SQL Server 2005 and onwards, the expectation is that this individual also knows how to exploit SQLCLR. Mostly, these individuals are also notorious for writing queries that piss off the conventional DBAs; the 'junk' that they come up with adds to the maintenance list of the conventional DBA (not that I have something like this ). In most start-ups and mid-sized organizations, there are no conventional DBAs - so the expectation is that you better know what the heck you're doing. If *you* break it, *you* fix it.

A business intelligence developer is a newer title. These individuals are usually responsible for working with the DBAs and the DBA programmers to understand their data and performance needs. They most likely work on ETL jobs, do things around data warehouses, reporting, etc. The tools used could include Integration Services, Cognos, Analysis Services, Hyperion Essbase, etc. Needless to say, these data needs do not arise in smaller organizations, and hence, these individuals usually can be found in larger corporations.


The pay topic is kinda wishy-washy right now because of the economic conditions. Average salary for a front-end developer with no SQL experience and a bachelor's used to be about 55K - I wouldn't be surprised if that number has come down to 35-45K (for states like FL, WA, TX, AZ) because the number of 'laid-off' professionals with experience is huge. The only professions paying in the 55K range right now are those of chemical engineers and auditors (accounting).

IMO, this is a golden opportunity, given the economic conditions, dude. Just take it, gain and absorb the experience, learn (listen) as much as you can, and pray for the econoym to get better. Hope this helps.

 

[Cogman]

I figured it was a pretty good opportunity. The only thing I was really worried about is database design/implementation, as I think that might be my job (I don't know yet).

I'll be interested to see where this goes.

 

[presidentender]

DB programming isn't hard to do. It's a bit hard to do right.

For this job, I assume the pay is a secondary consideration - ask him for $10/hr and treat it as an extended interview.

Edit: It is imperative that you steer him hard away from Access and toward SQL. Access will not help your career nearly as much.

 

[chronodekar]

Glad to hear that you got noticed! Congrats!!

5hrs/week doesn't sound like much time to me. In the sense, to try and steer them to SQL.

IMO, if you are going to stick to that time-frame, don't make any radical suggestions just yet. It will come back to haunt you later, when you are called in at an odd time, just because some idiot who didn't know what he was doing broke the system.

I suggest that you use this opportunity to brush up on your MS access skills. Show them that you can do the little tasks well. Hopefully, they'll be impressed enough to hire you full-time later. Then, (if you decide to stick with them) you can suggest SQL.

 

[brandonb]

Database programming is not hard, but if you never have done it, it might be intimidating.

Just read up about SQL on the internet, and relational database design.

Ask for $10-11/h. This is your chance to get your foot in the door and do some real programming. You are going to have mistakes, its likely it will be a zero stress job. Here is a tip for you since you are new: The more you ask for salary, the more responsibilities they put on you, and the more you are accountable for your errors. If you make $60,000 a year and you have a ton of bugs in your code and your answer to your bosses is "I don't know...I've never done this before" alot, you're not going to be on anybody's "golden boy." However, if are being paid $20,000 a year, you will be. I'd be suprised on how politics and pay play into things. Use this opportunity to avoid politics and just learn some skills.