View Full Version : So what's the real world like when......

02-13-2002, 08:35 AM
it comes to programming at a job. Just curious on what to expect. Working on a associates degree. Already have a business degree. Wondering if you are required write a certain amoung of code a day and what would be the typical day on writing code? Plus how do companies treat wet-behind-the-ears newbies?

02-13-2002, 08:40 AM
Depends on the company... Newbies (if you actually start programming, which is realtively rare AFAIK) usually get the littl ecrap projects that should be done that no one else wants to do... Or, they could hook you up with a mentor, to teach you about their software... Or, maybe you'll be CEO in 6 months.... It all depends :D

02-13-2002, 09:01 AM
What type of knowledge should one have?

Mastering the basics such as loops, functions, classes and OOP?

Being able to create windows apps?

Advanced topics like creating software to make dynamic images?

I am curious what 'skill sets' they assume one has, besides a degree, I can't quantify what makes a master c++ coder

Thanks, just curious

02-13-2002, 09:09 AM
There's no blanket requirements...

> Mastering the basics such as loops, functions

Probably would be a good idea, althoguh that can probably be assumed if you have a degree...

> classes and OOP?

Would be nice... Not necessary everywhere (what if you're only programming in C?)

> Being able to create windows apps?

Good if Windows, bad if Linux...

> Advanced topics like creating software to make dynamic images?

Maybe, but not everyone needs something that complex...

> a degree

This'll probably get you a job faster than everything - not many people are going to give you a programming test...

Sorry if my answers sound kinda fuzzy, but there's no set business model that every company abides to, so companies (and even different departments in companies)are going to have different wish lists.

02-13-2002, 09:12 AM
Essentials to give to a new employee:

A pile of not quite up-to-date documentation about some software which is like what your supposed to do.

A copy of some source which will not compile.

A vague run down of where all the various libraries are/were in a weird network that you have to have worked on for a year before you understand.

A specification for what you are supposed to be doing, missing a couple of chapters, (eg. those dealing with what is to be done - they'll be marked "TBD").

A list of people who will help you, except...

1: they don't know they're supposed to help you
2: they have no time
3: they're suspicious of your motives so tend to hide real info
4: they have no useful information

... and at least one of them will spend hours boring you stupid about how he saved the company from almost bankruptcy by his brilliance in solving an insolvable problem in 1983.

So, get going then.

02-13-2002, 09:58 AM
5: they get to know of your existence the second you step through their door... and don't have a clue what you want

02-13-2002, 01:03 PM
6: When they do help, it's only to add something completely retarded to an otherwise finished project..

02-13-2002, 11:09 PM
I couldn't tell you how new programmers are treated, since our HR department screens out anyone with less than five years experience. Weren't you at one time a new programmer?

02-14-2002, 04:36 AM
I was told that the 'newbies' were made to work with senior programmers in groups, helping to make some stuff.

Deckard did you script the movie Office Space??? :D

nice avatar BTW.

02-14-2002, 07:03 AM
My day at work as newbie:

Come in at 7:30
surf dilbert.com and former pamie.com 'till 8
code until 13:00
take a break until 13:30, most of the time just talking a walk outside
code some more until 16:30
leave for home

My day now:

come in at 10:00
listen to all complaints and questions that poped up from 7 to 10.
solve some
read all email
code some
code some and wait for complaints and questions to come
code some
leave in time for Buffy ( 19:30 )

02-14-2002, 07:28 AM
Originally posted by tim545666
Weren't you at one time a new programmer? Obviously, but we don't have any 'newbie' programmers here, so I couldn't tell you what my company would do with them.

To help you with what (logically) might be your next question, when I was a newbie at some other company, my day was suprisingly similar, but the coding tasks were easier and my opinion counted much less. The pay reflected that.

02-14-2002, 07:31 AM
Originally posted by ihsir
Deckard did you script the movie Office Space??? :DMy co-workers and I like to think so. ;) We even refer to our VP as Lumberg. Also (for what it's worth), Nick Pappageorgeo quotes (from Vegas Vacation) go over really well here. Go figure.

02-15-2002, 03:44 AM
>>My day at work as newbie:
I remember being like that.
So eager to code, looking forward to seeing the end product of my work.

As a newbie I got sent to the outback. Not a hole, but somewhere they put the dirt after they dug one. Saw up to 3.5Km long trains real close, too close, in the shadow of the salt piramids.

Worked >12hrs per day / 7 days per week with no paid overtime.

>>My day now:
Less impressed with what I can do on a PC, as I know how much more there is to be learned and how much harder it is to find. Realise that when I thought I knew it all I knew nothing.
More impressed with the quality of the caffine, we now have a expresso machine in the office.