Software developer question - dev shop or internal?

[K29]

I am going to write this question as general as possible to encourage more feedback. Looking for opinions here for assistance.

What would you say the main differences in working environment when comparing working for a dev house where you are a software developer being outsourced to projects, or working internally? Also in terms of salary package and so on?

Which is better?

I have tried googling but my search terms don't seem to be giving much. If you have any links to a good article comparing the two that would also be appreciated.

 

[etienne_marais]

Personally I prefer a dev house, you work with knowledgeable colleagues who can also stand in or help in a crisis and probably work for a boss who knows the technologies and have insight to problems and how long projects should take. Internal you are more likely to have to do work across the spectrum and be asked questions about Word for example.

 

[Hamster]

Dev house FTW because then the business is software and most staff are devs. When you work in an IT department at a corporation the focus is all about staying in budget and making business happy (there's a reason banks pay devs so much money, it's to keep them from leaving).

 

[profeet]

Dev house FTW because then the business is software and most staff are devs. When you work in an IT department at a corporation the focus is all about staying in budget and making business happy (there's a reason banks pay devs so much money, it's to keep them from leaving).

Unless of course the whole op is spearheaded correctly; however such instances are rare and can change quickly into another body shop.

 

[Hamster]

Unless of course the whole op is spearheaded correctly; however such instances are rare and can change quickly into another body shop.

There's always politics. I work for a dev shop but on a project at the bank. Only recently has the project management become very good but the politics remain. Worst is that the bigger team is led by people trying to build and protect their little empire.

Can't tell you how comforting it is to know that I can call my real boss anytime and tell him I've had enough if this k*k.

In the meantime though, the lead guy/architect is doing all he can to shield us from the bs so that's a plus.

 

[profeet]

There's always politics. I work for a dev shop but on a project at the bank. Only recently has the project management become very good but the politics remain. Worst is that the bigger team is led by people trying to build and protect their little empire.

There we have the true face of corporate.

Can't tell you how comforting it is to know that I can call my real boss anytime and tell him I've had enough if this k*k.

In the meantime though, the lead guy/architect is doing all he can to shield us from the bs so that's a plus.

Besides we all know minus big-brother, big-ego, big-selfprotect and of course big-politics one can actually just do your ****ing job :erm:

 

[BlindMelonChitlin]

It boils down to management. When working for an internal team, it's a catch 22 - on the one hand, you're seen as a guru by the staff, on the other, you work for people who don't understand your needs as they aren't into the software dev stuff - they're all about their core business. Fighting for your divisions share of the budget can be a challenge. On the other hand, if you like a steady environment where you can be top dog, internal can be a better environment.

With a company that offers development services, there are more opportunities for learning new stuff and facing new challenges - more engaging. If you have a poor manager, however, it can be very frustrating.

Internal - potentially more politics, less stress related to being in the deep end, you get the satisfaction of having a good handle on the systems you build and refine.
External - each project is a fresh start, can be less satisfying since you never 'fine tune' your creation. Generally you deliver on a schedule and budget and start from scratch on the next project (unless you re-use a your code for similar projects).

 

[rrh]

In my experience large organisations have more politics than do dev shops.

OTOH large organisations also normally have budgets for equipment, software, tools and training - all relatively rare in most dev shops.

 

[krycor]

Office politics happens everywhere.. You need to learn to deal with it.

I prefer large organizations as then they are likely less reliant on me which seems to happen often . In small organizations there is less Corp policy and so IT fast becomes McGuyver style, boere maak n plan and projects become either long winded or held together by best wishes, old coffee and me working my ass off and stressing. I'm very process and procedural driven so I excel in large corps but in small organizations I kinda end up getting frustrated as dev is exceptionally unpredictable. I'm an engineer so kinda expected.

In larger organizations they have proper project planning and as consequence of dev these days having a cost (where done right), plan use of resources.. So if the architecture is bad, the dev doesn't take the brunt unlike in small dev shops.

If you value having life balance, small dev houses are not where u want to be unless hey have a very conscientious pm or lead Eng who wants things done right and then there still will be yucky times but at least u won't be alone.

Did PM last year and kinda was cool as it highlighted all the stuff I know about planning vs dev etc. so yah.. I think the longer one works the better u become at handling office politics but less tolerant of shoddy management and planning.

 

[profeet]

I prefer large organizations as then they are likely less reliant on me.

Also a lot less reason to keep you; would they actually miss you?

 

[krycor]

Also a lot less reason to keep you; would they actually miss you?

Yes.. So many people will tell you in a small organization you impact is huge and thus this is where you should go to change the world.

But this is part true.. The part they don't tell you is that as a result you will be snowed under with work and expected to perform massive miracles all the time.. Do that for 1-2 years and the stress and strain will have a huge effect.

In a large organizations process are defined and worked on but may not be optimal. This you kinda have to work hard to make yourself stand out.. But again, if you great in process driven environments and can improve things or produce things with greater efficiency than thought.. People notice.

Now the advantage of large organization is that your variables you can play with is limited to its actually, contrary to popular belief, a LOT easier to pull it off .. Small places.. Too many variables thus it's more challenging

 

[profeet]

Yes.. So many people will tell you in a small organization you impact is huge and thus this is where you should go to change the world.

But this is part true.. The part they don't tell you is that as a result you will be snowed under with work and expected to perform massive miracles all the time.. Do that for 1-2 years and the stress and strain will have a huge effect.

In a large organizations process are defined and worked on but may not be optimal. This you kinda have to work hard to make yourself stand out.. But again, if you great in process driven environments and can improve things or produce things with greater efficiency than thought.. People notice.

Now the advantage of large organization is that your variables you can play with is limited to its actually, contrary to popular belief, a LOT easier to pull it off .. Small places.. Too many variables thus it's more challenging

Until retrenchments starts.

 

[krycor]

Btw in dev, Corp dev is not as fun as product dev at a new start up company .... Result is that I can throw a stone and hit many devs who wanna work on the next funky thing. Not many will wanna work on some boring framework that does what it does and no one knows much about.

If you passionate about that boring thing everyone ignores you standout and will likely be able to do it better than anyone else.

Lastly many people have this thought that innovative work needs to happen at day job all the time or it's a boring job & it won't pay well.. Well if you really like innovation I think you can make a lot more money with less income risk doing it outside of your Corp job too. I dunno seems to me like it's a perspective thing..

 

[krycor]

Until retrenchments starts.

True.. But that's why u should always be multi-skilled and trying things on own.

 

[profeet]

Btw in dev, Corp dev is not as fun as product dev at a new start up company .... Result is that I can throw a stone and hit many devs who wanna work on the next funky thing. Not many will wanna work on some boring framework that does what it does and no one knows much about.

If you passionate about that boring thing everyone ignores you standout and will likely be able to do it better than anyone else.

Lastly many people have this thought that innovative work needs to happen at day job all the time or it's a boring job & it won't pay well.. Well if you really like innovation I think you can make a lot more money with less income risk doing it outside of your Corp job too. I dunno seems to me like it's a perspective thing..

You seem to be steam rolling into some direction where we are not.

True.. But that's why u should always be multi-skilled and trying things on own.

You can shoot rainbow from your arse, but when its time in corporate its time. Don't think for a second that its safe in numbers; hiding away and playing it lekker will always work.

I'm just going to end with this...

[video=youtube;a7LH__BPqSY]https://www.youtube.com/watch?v=a7LH__BPqSY[/video]