|
Hi, I am a student working my way for an associate’s degree in Information technology. My main focus is computer programming and I have finals coming up, but for one class I have to do a report about what it’s like to be computer programmer. This is a little hard for me since I have no connections to anyone that is currently employed in the field.
I have come up with some questions if anyone on here would be willing to answer my questions and send them to me via email it would be greatly appreciated and I would really enjoy getting a better understanding of what the life of a programmer is really like.
There is roughly 30 questions, but feel free to answer as many as you like. When I get around to reading it and I liked what I seen then I will use it for my final project, which is an informational interview report. I will also email you back informing you that I am using you as my interviewee for the project.
My email address is xxxxxxxxxxxx@hotmail.com and I will attach a link to a Google Docs file to this post for anyone who is interested. Thanks to anyone who is willing to take the time to help me with this, it’s greatly appreciated.
modified 27-Feb-16 21:19pm.
|
|
|
|
|
Kore1322 wrote: what it’s like to be computer programmer
It's wall-to-wall chicks: Sex & Drugs & Rock & Roll, maaaaan.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I just was on my way to warn the guy that all computer programmers are liars...I can skip that now
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
You think we should tell him "it's indoor work with no heavy lifting"?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: no heavy lifting I use a special keyboard with metal plate on its bottom - that's heavy...
Every time I want to hit the computer, not only I have to lift it, but also have to crawl under my desk to actually hit it...I would not say that, this is an easy work...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Steel toe-cap boots. Just kick the damn thing!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Boots! 10 out of 12 months I wear sandal!!! And take them off too...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Please, please tell me that's not "with socks"?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
No socks...Too hot for me...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Yup, the chicks are all driven by hormonal impulses which compel them to offer their hot bodies to men with a high earning potential, and few earn so much as programmers. Most programmers die of sexual exhaustion, usually in their early fifties.
Will Rogers never met me.
|
|
|
|
|
Just an aside are these 'chicks' you speak of kinda like the ones from Dilbert that reside on the moon?
|
|
|
|
|
If he doesn't believe you, he can take a look at your photo. Hard to believe you're only 26.
This space for rent
|
|
|
|
|
The white is because of the intensive life style...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Quote: When 900 years old you reach, look as good, you will not.
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Roger Wright wrote: Most programmers die of sexual exhaustion, usually in their early fifties.
I guess I'll be living a bit longer then.
Marc
|
|
|
|
|
Actually, my first job was just that, without the chicks. Devon! My god, I don't know if wales is the same, but the locals are a wild bunch!
|
|
|
|
|
Feel free to send me the link via email (in my sig).
/ravi
|
|
|
|
|
Kore1322 wrote: When I get around to reading it
Sounds like you'll make an excellent programmer.
|
|
|
|
|
I recently tried out UVI workstation (MIDI based virtual instrument software) and was impressed enough that I went out and bought a mid-priced (but with great feel) 88-key e-piano, MIDI to USB cable, and an additional suite of sounds from UVI. (you don't get full editing capabilities with the sample sounds, which is mainly what I'm after)
So, after getting it all setup and working, I notice that I can't get the attack/punch that I'm expecting. The problem seems to be latency. I tried it on 3 pretty fast PCs to rule out a crappy sound card as an issue. The results are all similar...about a tenth of a second from pressing a key until the speaker gets the signal. It's actually very similar to the reason I quit playing my bass guitar through the line in jack. It worked great until I moved to a new rig with Win7. After failing to get that to work, I was forced to find a place for a half-stack in my home office. It works, but I miss the ability to use headphones.
Sorry, I've gotten off topic, so back to it. Unfortunately, it seems that typical PC sound cards are just not up to the task of delivering sound in near real-time. Google has found something that might work but before I spend anymore on this venture, I thought maybe one of you has maybe done this before and can offer advice. What I am looking at now is this[^], a USB connected external sound card (they call them 'audio devices') that also has MIDI I/O...the idea being that this device was made for this purpose and should give acceptable results. However, nowhere in the specifications do they provide a measurement of latency. Anybody here have experience with one of these?
Hope I haven't bored you too much! Have a great weekend everybody!
"Go forth into the source" - Neal Morse
|
|
|
|
|
If you are using an on board sound card you can get workable latencies by installing asioforall wdm wrapper(free) and using asio mode instead of the windows default wmd or wasaipi way which are paltry.
If you get a real sound card someday you should use the manufacturer's asio drivers and not the asioforall wdm wrapper though.
|
|
|
|
|
Genius man! I had tried ASIO4all on a previous system with the same soundcard in an attempt to reduce latency on the line in. It didn't work then, so I dismissed it for this case. Based on your advice, I downloaded the latest version, installed, selected it as the output device in UVI workstation, and latency is way reduced...to a tolerable level anyway! Thanks! Now, I'm like a kid in a candy store!
"Go forth into the source" - Neal Morse
|
|
|
|
|
Hmmm, Bass Guitar through the line in, I only tried it once noisy & an impedance mismatch made it sound like I was playing a banjo. At that point I gave up trying use a PC for audio input. The midi delay you speak of has got less than back in the day (when Dave Bronze play a Roland Midi Bass with the Art Of Noise, and had to relearn proper time when the tour ended). Awkward. When I was at Uni one of the courses I chose was 'Studio Technology' we had to do a whole assignment on Midi. Basically the latency has fallen over the years from really noticable to as it stands now, which is not too bad if you keep the signals midi and only convert it when you go for output. Short answer try it, you might find it OK. One ofthe reasons 'they' are cagey about the delay is it is getting less each major revision and 'they' don't want to have to do the documentation every five mins.
|
|
|
|
|
Thanks for the reply! ASIO4All drivers fixed the latency problem. (thanks Ron) I was able to play bass through the line-in just fine up to 2009 when I made the jump from Win2K t0 Win7. It probably only worked OK since the bass has active pickups.
BTW, Nice story about Dave Bronze!
"Go forth into the source" - Neal Morse
|
|
|
|
|
There is a driver called virtualmidisynth that may help you.
You configure it with a sound font and can set the latency down to 10 milliseconds.
MIDI used to work great in Windows. Alas, it is now a second class citizen.
|
|
|
|
|
Thanks, I'll check it out!
"Go forth into the source" - Neal Morse
|
|
|
|