• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Question to professional software engineers...

jinduy

Diamond Member
¿

right now i'm in a corp environment... not really digging it after a year at all... too political, everyone's always trying to find someone else to blame.
 
I intentionally picked small companies for this job and my previous one.

At a small company you have a huge impact on the product and get to do a wider variety of work.

At a large company you can easily end up a small cog in the machine, and might end up pigeonholed into a narrow, repetitive kind of work.

.... and at a small company everyone is expected to do their job or they're out the door.
 
Large = Safety Net. Available resources for training and tools/Paperwork up the rear for standardization / cutthroat egos
Small = Put up or shut up. Less resources/more inovation/more recognition / possible less pay but potential for growth.

Been at both - prefer small
 
interesting points...

i've only been in corporating and i can agree with the paperwork up the rear for standardization
 
Startups...if you have good skills you'll have a job regardless. If you do it right you have a job for at least 2 years, you can influence the products, the culture, and have the flexibility to contribute to the management tasks such as strategic and revenue based decisions

For one, if you get into a funded startup you'll make the same amount with more room for growth and the ability to hit it big with options. A few people I know make a living out of taking jobs at startups and collecting options and have done very very well
 
Originally posted by: EagleKeeper
Large = Safety Net. Available resources for training and tools/Paperwork up the rear for standardization / cutthroat egos
Small = Put up or shut up. Less resources/more inovation/more recognition / possible less pay but potential for growth.

Been at both - prefer small


some 'pure' bigshop people couldn't hack it if downsized and forced into a smaller company where you may have to demonstrate a wider range of skills.

u wonder if they deserved the big bucks back at the big shops, some really do not.

 
Originally posted by: abc
Originally posted by: EagleKeeper
Large = Safety Net. Available resources for training and tools/Paperwork up the rear for standardization / cutthroat egos
Small = Put up or shut up. Less resources/more inovation/more recognition / possible less pay but potential for growth.

Been at both - prefer small


some 'pure' bigshop people couldn't hack it if downsized and forced into a smaller company where you may have to demonstrate a wider range of skills.

u wonder if they deserved the big bucks back at the big shops, some really do not.

the thing that bothers me with these "big shops" is that there's too much job securities sometimes... i see people who have no place in our team and always have to have someone else cover their butts, the managers might know or they might not know but it's very hard to fire someone or lay them off in my company.
 
I prefer the small shop / small team environment.

Building software systems is similar to manufacturing something. You figure out who your customer is and create something to satisfy their need.

Many times in the big environment, a smaller scale project with a limited shelf life is required to be 'manufactured' using the same processes that you would use to augment parts of the Enterprise Architecture. This is far from optimal and results in lots of wasted time and effort for the small project.

The small shop / small team allows for flexability in the software process so that you enjoy the freedom of scaling processes up or down, depending on the needs of the project.
 
Engineers build things.

Researchers come up with ideas that Engineers can use :thumbsup😱r show that are no good.:thumbsdown:
 
Back
Top