• Get involved.
    We want your input!
    Apply for Membership and join the conversations about everything related to broadcasting.

    After we receive your registration, a moderator will review it. After your registration is approved, you will be permitted to post.
    If you use a disposable or false email address, your registration will be rejected.

    After your membership is approved, please take a minute to tell us a little bit about yourself.
    https://www.radiodiscussions.com/forums/introduce-yourself.1088/

    Thanks in advance and have fun!
    RadioDiscussions Administrators

Programming to Engineering?

G

GenericPosterGuy

Guest
I'm giving some thought lately to my next step in the business...I've always been interested in engineering although I don't know much about it. Has anyone here made the programming-to-engineering move? What did you have to learn / do / know to make the move? What's the best thing for a budding engineer to do learn that which must be learned? Thanks.
 
> I'm giving some thought lately to my next step in the
> business...I've always been interested in engineering
> although I don't know much about it. Has anyone here made
> the programming-to-engineering move? What did you have to
> learn / do / know to make the move? What's the best thing
> for a budding engineer to do learn that which must be
> learned? Thanks.
>

Most likely if you go to school for engineering. Otherwise, I can't see companies hiring you. (I'm not an engineer. But I assume)
 
> I'm giving some thought lately to my next step in the
> business...I've always been interested in engineering
> although I don't know much about it. Has anyone here made
> the programming-to-engineering move? What did you have to
> learn / do / know to make the move? What's the best thing
> for a budding engineer to do learn that which must be
> learned? Thanks.
>

I made the leap several years ago (I was a PD/Morning Guy), though I worked as an assistant to the Engineer while doing my programming duties so that I could learn.<P ID="signature">______________
</P>
 
> > I'm giving some thought lately to my next step in the
> > business...I've always been interested in engineering
> > although I don't know much about it. Has anyone here made
>
> > the programming-to-engineering move? What did you have to
>
> > learn / do / know to make the move? What's the best thing
>
> > for a budding engineer to do learn that which must be
> > learned? Thanks.
> >
>
> I made the leap several years ago (I was a PD/Morning Guy),
> though I worked as an assistant to the Engineer while doing
> my programming duties so that I could learn.
>


OY! Waking up to Doc every morning...... Now THERES a nightmare! <JK>
 
Has anyone here made
>
> > the programming-to-engineering move? What did you have to
>
> > learn / do / know to make the move? What's the best thing
>
> > for a budding engineer to do learn that which must be
> > learned? Thanks.


As matter of fact, about two years ago, I made the move from programming to engineering. Best thing to do is get someone (who is an engineer) to allow you to learn from them. I did this for years, learning everything I could learn...help him out, and just absorb as much as I could. I never went to school for it...I have practical experience. I was lucky enough to have a guy who I consider a friend and a mentor, and continue to learn more each week. As we speak, I am getting ready to build a complete station from the ground up!<P ID="signature">______________
Zach Morton
Chief Engineer
Legend Communications Of Wyoming, LLC.
KGWY/KAML/KIML/KLGT/KZZS/KBBS
Office (307) 686-2242
Cell (307) 660-9101</P>
 
> Has anyone here made
> >
> > > the programming-to-engineering move? What did you have
> to
> >
> > > learn / do / know to make the move? What's the best
> thing
> >
> > > for a budding engineer to do learn that which must be
> > > learned? Thanks.
>
>
> As matter of fact, about two years ago, I made the move from
> programming to engineering. Best thing to do is get someone
> (who is an engineer) to allow you to learn from them. I did
> this for years, learning everything I could learn...help him
> out, and just absorb as much as I could. I never went to
> school for it...I have practical experience. I was lucky
> enough to have a guy who I consider a friend and a mentor,
> and continue to learn more each week. As we speak, I am
> getting ready to build a complete station from the ground
> up!
>
Excellent post. I too (some 30 years ago) had several great mentors who took the time to explain and let me help and learn things never taught in school or written in a textbook. Learning by doing is by far the best I was told. As for mistakes...you learn by them as well. Although at times it tries my patiance, I
think back on the people (engineers) who went the extra mile to explain in detail to a question I asked.
I enjoy helping others learn what I have over the years. Best of luck to you.
 
> > Has anyone here made
> > >
> > > > the programming-to-engineering move? What did you
> have
> > to
> > >
> > > > learn / do / know to make the move? What's the best
> > thing
> > >
> > > > for a budding engineer to do learn that which must be
> > > > learned? Thanks.
> >
> >
> > As matter of fact, about two years ago, I made the move
> from
> > programming to engineering. Best thing to do is get
> someone
> > (who is an engineer) to allow you to learn from them. I
> did
> > this for years, learning everything I could learn...help
> him
> > out, and just absorb as much as I could. I never went to
> > school for it...I have practical experience. I was lucky
> > enough to have a guy who I consider a friend and a mentor,
>
> > and continue to learn more each week. As we speak, I am
> > getting ready to build a complete station from the ground
> > up!
> >
> Excellent post. I too (some 30 years ago) had several great
> mentors who took the time to explain and let me help and
> learn things never taught in school or written in a
> textbook. Learning by doing is by far the best I was told.
> As for mistakes...you learn by them as well. Although at
> times it tries my patiance, I
> think back on the people (engineers) who went the extra mile
> to explain in detail to a question I asked.
> I enjoy helping others learn what I have over the years.
> Best of luck to you.
>

Oh yeah...I've made a mistake or two since I started, but hey...you won't learn unless you do. I started as assistant engineer a few years ago, on to Market Chief 6 months later, and have been Chief Engineer for 2 years of 7 radio stations in two markets. It's a rewarding experience and way different than the everyday "stuck in the studio" stuff...and for those who like instant gratification...nothing is more rewarding than taking a sick transmitter, fixing it, and pressing HV ON and watching it come back to life. Makes you warm and fuzzy all over.
<P ID="signature">______________
Zach Morton
Chief Engineer
Legend Communications Of Wyoming, LLC.
KGWY/KAML/KIML/KLGT/KZZS/KBBS
Office (307) 686-2242
Cell (307) 660-9101</P>
 
> > > Has anyone here made
>snipped...

> Oh yeah...I've made a mistake or two since I started, but
> hey...you won't learn unless you do. I started as assistant
> engineer a few years ago, on to Market Chief 6 months later,
> and have been Chief Engineer for 2 years of 7 radio stations
> in two markets. It's a rewarding experience and way
> different than the everyday "stuck in the studio"
> stuff...and for those who like instant
> gratification...nothing is more rewarding than taking a sick
> transmitter, fixing it, and pressing HV ON and watching it
> come back to life. Makes you warm and fuzzy all over.
>
Yep, can't beat the "troubleshooting in the mind" while driving to a transmitter site.
5 Miles away....tower lights on....theres, AC
1/2 Mile away, you hear the station, exciter and stl ok
Then you open the door....
you smell, look and listen for the next clue!
 
> I'm giving some thought lately to my next step in the
> business...I've always been interested in engineering
> although I don't know much about it. Has anyone here made
> the programming-to-engineering move?

I did it back in about 1968, so the route might not work
anymore.

Had been doing most of the technical work at a station in
Providence, the "engineer" being a part-timer who owned a
small station in a nearby market. An FCC inspector figured
it out but couldn't prove it. I went off to a quickie
license school and continued the OJT I was already doing.
Within a few months I bailed out of radio and went over
to television operations, then worked into maintenance.

But....only so much money to be made there. So I bought my
own ticket and got a vendor pass to NAB and went there (Vegas).
Not so much to SEE as TO BE SEEN. Met some really good people
with makers/suppliers of TV equipment and hung out with some
of them. A few months later there was an opportunity in
sales engineering with one of the biggest. Applied; was
called for an interview and, when I arrived, everybody already
felt they knew me. Turned into a really nice career in sales,
international sales, marketing, and finally training product
managers and salesmen. Good enough to retire at 55 and do
what I want, including playing at radio.

Moral: Why limit yourself? Think ahead, way ahead!<P ID="signature">______________
When you're done impeaching the prez, keep on going; recall every member of congress and lock 'em up! Let's try NO govt. for a while.</P>
 
> Excellent post. I too (some 30 years ago) had several great
> mentors who took the time to explain and let me help and
> learn things never taught in school or written in a
> textbook. Learning by doing is by far the best I was told.
> As for mistakes...you learn by them as well. Although at
> times it tries my patiance, I
> think back on the people (engineers) who went the extra mile
> to explain in detail to a question I asked.
> I enjoy helping others learn what I have over the years.
> Best of luck to you.

I'm kinda in the same situation. For 25+ years, I was a medium/large market jock but started to grow weary of it. I was always interested in how it all worked, and even though I didn't need it all those years ago, I studied for, and got my first 'ticket'--when you had to have a 1st to do this stuff--and hung around the engineering types. (Please don't get me started on individual licensing requirements. Am I the only one who thinks dumping that requirement was extremely STUPID?!?) I think alot of those guys and I got along because I spoke their language. I'm now teaching radio & TV and have a (small) list of client stations (mostly smaller AM's) that I do contract work for. I'm fortunate because I've had the opportunity to work with, and learn from alot of people I admired. The one major thing that has helped me is maintaining those old contacts/friendships to use as my 'phone-a-friend' in case I run into anything that's a little beyond me. I'm still learning this stuff... everyday.
 
Am I
> the only one who thinks dumping that requirement was
> extremely STUPID?!?)

Nope...the guy I replaced didn't know the first thing about how to keep a radio station on the air...when I got here, I had to help him fix the AV network, and the transmitters were in sad shape. I still believe that we should have the General requirement to be an engineer...but just my honest opinion.<P ID="signature">______________
Zach Morton
Chief Engineer
Legend Communications Of Wyoming, LLC.
KGWY/KAML/KIML/KLGT/KZZS/KBBS
Office (307) 686-2242
Cell (307) 660-9101</P>
 
> > > > Has anyone here made
> >snipped...
>


Started the same way myself in 1990. I realized that satellite and computers were going to take over and since I did not want to move to a big city, I needed to find another avenue to stay in radio. I took night courses in electronics at the local tech school. This gave me the basic info I needed to start. I then became the engineer of a small AM/FM combo. None of this would have been accomplished if it was not for some great engineers who were always there when I needed them, and they still are 16 years later.

You WILL make some mistakes, there is no question about that. The trick is to learn from those mistakes. Always take notes about the problems you find and how you fixed them. You will see that problem again somewhere down the road. <P ID="signature">______________
Robert Combs
Cumulus Broadcasting - Savannah
Any opinion expressed here are my own and do not reflect any opinions or association with Cumulus Broadcasting.</P>
 
I'm someone who is living the life right now in transition...

I'm a PD, afternoon host, and Operations Manager. I'm starting to learn that my interest is slowly focusing on the Operations and engineering side of things. I've been very lucky to have some great engineers along the way to serve as mentors and be willing to teach me what they know about fixing stuff. I've always had a good knowledge of electronics, and so much of this stuff came naturally to me. I'm not too far off from getting my first full-time engineering job.

So, the best advice I can give is if you're currently employed at a station, get to know your engineer. Join mailing lists such as the radiolist.net that provide a good forum for engineering chatter. Most engineers love to share their stories and would welcome an opportunity to have an apprentice. Schooling is optional, at best it would give you the basic electronic knowledge and theories to get you started.

Best of luck!


> I'm giving some thought lately to my next step in the
> business...I've always been interested in engineering
> although I don't know much about it. Has anyone here made
> the programming-to-engineering move? What did you have to
> learn / do / know to make the move? What's the best thing
> for a budding engineer to do learn that which must be
> learned? Thanks.
>
<P ID="signature">______________
The power is yours!</P>
 
Just remember the good engineers have kept their stations on the air, the great ones have knocked them off once or twice in their career!

(It means you've learned what not to do and what little idosynchrasies , however you spell it, your transmitting equipment has)...


My warm and fuzzy feeling comes when I finished doing work on the transmitter to keep us on the air, and driving home late in the evening, from the top of the mountain, looking over the cities and all the lights, thinking "you know, those people are home, some, maybe a lot, are watching my station right now, and it's a big part thanks to me!".

It's why I like doing what I do...
 
Hey Zach:A little off topic, but you said that you're working on building a new station from the ground up. This sounds exciting! Is it in your market? FM?
 
If you know anything about computers and the systems used in your stations, you have a leg up. Great way to get your foot in the door. Then, as the rest have said, start shadowing any engineer that will let you. Most are willing to share some of what they know and some are willing to go over the top to help you. Ask about reading materials so you can begin to understand the theory behind what you are getting into. If you find you like it, take advantage of the OJT and maybe pick up some classes at the local college. If you can support your practical experience with a degree, you are way ahead in the game.Good Luck, it was a jump I made several years ago and I love it!K
 
I've just decided to persue engineering after programming a radio station for a few years. I have the technical background. However, I'm wondering how to gain knowledge of all the FCC requirements and regulations - things like modulation limits, EAS maintenance, logs, and the tons of other rules I'm sure I don't even know exist yet. Where can I read up on these? How did you learn? Thanks.
 
In answer to your question...yes, it is an FM licensed to the town of Wright in Northeast Wyoming...it will cover Gillette rather nicely...which is where the money is. Starting from the ground up...studio's will be in Gillette with the rest of our cluster...tower will be about 8 miles south of town at 900'. Got the land secured this week...pin and anchor locations are set...next step is the core samples...then ERI will build this monster tower.Keep in mind that most radio towers in Wyoming are less than 500' tall, so this one will stand out!For those trying to get into engineering...I would follow what everyone else has advised...it's a great career field. What other job can you get that allows you the wide open spaces as your office? Yeah, granted, it does take you out at night more than not, but at least you don't punch a clock.
 
Field_strength said:
I'm wondering how to gain knowledge of all the FCC requirements and regulations - things like modulation limits, EAS maintenance, logs, and the tons of other rules I'm sure I don't even know exist yet. Where can I read up on these? How did you learn?
The FCC has it all rules and regs on the web these days http://www.fcc.gov. You might also try http://www.hallikainen.com as another source.I personally started out in mobile communications, and later became a ham.Willie, WJ3G
 
GenericPosterGuy said:
I'm giving some thought lately to my next step in the business...I've always been interested in engineering although I don't know much about it. Has anyone here made the programming-to-engineering move? What did you have to learn / do / know to make the move? What's the best thing for a budding engineer to do learn that which must be learned? Thanks.
I've been straddling the programming / engineering line for a few years now. Aside from safety courses, I don't have any formal engineering training, but have learned most of what I know by reading, joining the SBE, and through fellowship with other engineers. As time has gone by, I find myself more actively working in the engineering world than programming.I was lucky enough to know an engineer that saw my interest in engineering when I was a part timer running the board for football games on a local AM. He showed the me transmitter, explained the dangers of RF and high voltage to me, and let me fix things up around the station.In my case, the move to engineering came later from a push through management. I demonstrated an interest, and they had me take on more and more responsibilities until they finally cut ties with the contract engineer and hired another part-time engineer. It has worked out quite well so far.With 2 directional AM arrays, I had to learn how to keep the pattern properly adjusted. I keep Jack Layton's book "Directional Antennas Made Simple" handy when I make a trip to either of our directional AM's. It's a good feeling to know that your antennas are in good shape and you know how to keep them that way.My weakness right now is troubleshooting the FM transmitters. I can troubleshoot with the manual, and understand the basic building blocks, but am not at the level yet where I can make a component level diagnosis withould consulting the manual or calling tech support.Learn safety first - then start observing, reading, learn the basics of electricity and signal path, and you'll start to pick things up.
 
Status
This thread has been closed due to inactivity. You can create a new thread to discuss this topic.


Back
Top Bottom