|
More than half my class at uni were completely unemployable in the field, both before and after they picked up their diplomas.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
In chronological order;
Concrete-industry (five years)
Academics (Nope, didn't fit in there, 2 years tops)
Pharmacy (Introduce a bug and kill someone)
Oil-industry (Just for a year)
Document Control / CAD (Two years and counting)
I'm a developer. To the software it matters not which "industry" you are in. It is all simply data, all stored in a database, all fetched in a similar manner.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Eddy Vluggen wrote: To the software it matters not which "industry" you are in. It is all simply data, all stored in a database, all fetched in a similar manner.
Except it's really not. Software can be tailored for an industry - processes, regulations and even laws may need to be understood and followed. Often times there are specific terms for specific industries. In my case, we're controlling really expensive and really powerful industrial machines that operate in a VERY flexible manner. Instructions and machine reactions need to be very well thought out with specific knowledge of the industry and the machine(s) involved.
Government is not reason; it is not eloquent; it is force. Like fire, it is a dangerous servant and a fearful master. ~ George Washington
|
|
|
|
|
Mike Mullikin wrote: Except it's really not.
Every damn niche thinks it is special.
Mike Mullikin wrote: Software can be tailored for an industry
Software is built based on specs, so yes, it would be tailored. Regardless of the niche, it would be.
Mike Mullikin wrote: processes, regulations and even laws may need to be understood and followed
Yes, but those simply translate to conditions that the developer checks. As long as there is a domain-expert (and no, my domain and industry is software development) I can model and build it.
Mike Mullikin wrote: Often times there are specific terms for specific industries.
There's also specific terms if you are writing a debugger, or a password-manager. Those are translated to logic, and then to code.
Mike Mullikin wrote: In my case, we're controlling really expensive and really powerful industrial
machines that operate in a VERY flexible manner.
More flexible than say, a generic, programmable all-purpose machine?
Mike Mullikin wrote: Instructions and machine reactions need to be very well thought out with
specific knowledge of the industry and the machine(s) involved.
Yawn.
Same goes for most industries; the price of errors can be high. Still your industry is a flow of information, and it is that flow that gets automated. As an analyst I do not need to be a domain-expert. Should not be in fact; one starts leaning on assumptions that the analyst recognizes.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
I expect no less from a job hopper. Good luck! ![Rose | [Rose]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/rose.gif)
Government is not reason; it is not eloquent; it is force. Like fire, it is a dangerous servant and a fearful master. ~ George Washington
|
|
|
|
|
Keep it, you might need it someday 
|
|
|
|
|
I think it comes down to what you call yourselves, you are an engineer and Eddy is a software developer. You have very different concepts on what you do, you must be a domain expert as well as a developer, Eddy, and I, need domain experts to function as developers.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Mycroft Holmes wrote: You have very different concepts on what you do, you must be a domain expert as well as a developer, Eddy, and I, need domain experts to function as developers.
Probably true. We're a smallish (450 employees worldwide) family owned business. We don't hire pure developers for short periods of time. We hire people who plan to stay a good long time and become experts in our industry.
Different world I guess...
Government is not reason; it is not eloquent; it is force. Like fire, it is a dangerous servant and a fearful master. ~ George Washington
|
|
|
|
|
Mike Mullikin wrote: We don't hire pure developers tarts for short periods of time
FTFY
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
You and I both! What we are has been established, all we need to work out is the pay!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Matt U. wrote: letter shop/printing service.
Been in this world for 15+ years.
Started at the lower level - interfacing with Docutechs, sending mailmerged data down, etc... Slowly made my way into the front office. Now I'm doing almost exclusively intranet-based order management/crm stuff.
|
|
|
|
|
The letter shop I worked for was my first major role in the professional world, so to speak. While I enjoyed the people I worked with, and I enjoyed the company's culture, it was very limiting. They're only about 13 years old, they're locally owned/operated, and they have about 75 employees total, in one local facility. They were very closed minded from a development standpoint. Limited to core technologies, like C#/.Net, some HTML and JavaScript.
It was a wonderful place to really get my foot in the door in the development world. I don't have a bad thing to say about my experience there, other than I feel like I basically grew out of where I was. There wasn't really any room for advancement, because there were only about 15 people in IT altogether, so there was nowhere for me to go.
The only software I ever got my hands into was their internal system that would parse clients' files (various formats including flat text, CSV, XML, etc.) and pass the data along to an existing service that would handle the rest. So I didn't get to do much there. I didn't want to be bored and halted in career growth.
djj55: Nice but may have a permission problem
Pete O'Hanlon: He has my permission to run it.
|
|
|
|
|
My company was pretty much the same, though I started further back in the pipeline than what you described. Then they got bought, and bought again. Went from one office with ~60 employees to dozens of offices, and over 2000 employees. You know, never changed jobs, but changed companies and business cards several times, that sort of thing. The current company's IT department is larger than the place I started with.
|
|
|
|
|
I've worked in 4 different industries.
Computational Chemistry , Linguistics (automatic text correction), Entertainment (2D animation) and Engineering (metrology).
But I've mostly been doing generic C++ framework and GUI work in all of those domains.
I'd rather be phishing!
|
|
|
|
|
My current job, which I've held for 24 years, is working for a company that builds commercial ink-jet printers. I've also done a fair amount of work as an after-hours consultant. The common thread through all of it has been process control and real-time machine control. I enjoy what I do. I've worked at several layers in the product line, from device drivers to UI.
Software Zen: delete this;
|
|
|
|
|
Lets see
Manufacturing - sewage pipes
Technology - Hitachi and Wang
Engineering
Mining Construction
Fruit Wholesaling
Tyre Retailing
Finance - Investments
Health Systems (NHS)
Back to Finance - Banking
Specialisation is for ants.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Developing the Instrument Software for medical diagnostic instruments, currently working as Sys Admin in Charge for the Swiss Air Force.
The console is a black place
|
|
|
|
|
Hmmm...Let's see...
E-commerce (mostly backend, data processing, GUI front-end at times too )
These days, I work for a company that creates software for OTN management, planning and optimization. Pretty interesting, really
This isn't a signature
|
|
|
|
|
Not really. My company is a consultancy so we have clients in a variety of sectors. I like variety and learning about domains so that's good for me. That said I've spent the last nearly 3 years working with oil and gas clients for the most part.
|
|
|
|
|
Defense. Navy. US Gov't employee. Highlights: Navair, ES-3A, NavSea, Aegis 5" gun, Tomahawk Launch Control. Couple trips to Iraq to work counter-IED. Retired now, but it was more interesting than the manufacturing sector I started out in.
|
|
|
|
|
Very nice. Sounds like it'd be a hectic job, since that sector is extremely critical. Not sure what kind of quality measures they have in place, but I'd think the slightest "off" code could cost more money than I know. Haha.
djj55: Nice but may have a permission problem
Pete O'Hanlon: He has my permission to run it.
|
|
|
|
|
ES-3A had excellent quality control, Tomahawk very nearly as good as ES-3A, Aegis Gun quality sucked. The gun had an impossible development schedule and the people were just demoralized and didn't try very hard at quality, although I thought we could do better, and was glad to leave the project.
Yeah, it was hectic but rewarding. When your software works, it saves soldiers and sailors. If it doesn't, they may die, which was my concern with the gun. Don't know of any incidents where sailors were hurt, but the potential was there.
|
|
|
|
|
Right, I understand. The rewarding aspect, I'm sure, was enjoyable.
djj55: Nice but may have a permission problem
Pete O'Hanlon: He has my permission to run it.
|
|
|
|
|
I'm in the actuarial consulting business. I develop valuation software in FORTRAN and related utilities in C#. I know, I said the F word.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
