6 ms·
Work somewhere where software is the main product and not just a cost center. You can learn a lot quickly if you do cutting edge things with people who care abo
by maxxxxx 10y ago
Work somewhere where software is the main product and not just a cost center. You can learn a lot quickly if you do cutting edge things with people who care about technology and not just cost.
Solve real world problems. Doing elegant things
is very difficult because the real world is much more convoluted than theory.
Do a few things in depth. Don't jump at the latest thing every few months.
- colefichter 10y ago> Work somewhere where software is the main product and not just a cost center. > Doing elegant things is very difficult... These are great! I would also add: be certain that the organization shares your values. If you really care about code quality, elegant solutions, etc, you'll have a frustrating time working at a company that doesn't prioritize those things.
- canterburry 10y agoCouldn't agree more.
- kzisme 10y ago> Work somewhere where software is the main product So a software company as opposed to working in an IT department - programming and solving problems that really _aren't_ interesting? That's one of the main things I crave these days (and I think it would make a big day-to-day difference) is to work at a software company as opposed to a company who leverages software.
- maxxxxx 10y agoIt's even a money/salary issue. There is a huge difference between the CEO seeing you as someone who makes money for the company as opposed to just being an expense.
- kzisme 10y ago>It's even a money/salary issue. Does this mean that you salary isn't increasing, or that you aren't valued at all? I'm curious how most people receive or handle (or if raises are even a thing)
- bluedino 10y agoAutomate things and make people's jobs easier. Then you're valuable.
- arethuza 10y agoThat's reducing costs rather than increasing revenue. Of course, within a limited range they are equivalent but you really only have respect in a lot of organizations if you contribute towards the latter.
- sgt101 10y agoOdd - because margin being what it often is a dollar saved is worth three/four... ten... ?
- unit91 10y agoAgreed, though I'd modify "software company as opposed to working in an IT department" to "work on something profitable". :-) I don't work at a software company, or even a traditional "tech" company, but I write the software that powers our most profitable product. Since I'm the odd-man-out, and the higher-ups love org charts, they stuck me in the IT department. Net effect: IT just became a profit center and everybody in the company knows it.
- kzisme 10y ago> something profitable Would that be the primary product of your company, or something that empowers other employees to work faster, and push _their_ products more easily?
- unit91 10y agoPersonal preference. In my situation, it's a retail product at a company that has a lot of other retail products. The one I work on just happens to be very profitable, so it gets a lot of attention. But I'd be very happy working on the empowering problem you mentioned too. I've been blessed by having experience in several, very different kinds of applications (web apps to avionics). Over time, I've realized the specifics of the problem at hand are more-or-less irrelevant to my happiness. I'm looking for something that's sufficiently technically challenging, where I can be surrounded by honest, friendly people, and make decent money.
- kzisme 10y ago> I'm looking for something that's sufficiently technically challenging, where I can be surrounded by honest, friendly people, and make decent money. This is very close to my real goal as well - but CRUD apps seem like the norm lately :(
- jimmywanger 10y agoWithout internal billing, only the first thing (profits from products) is measurable, and the second thing is mostly invisible.
- devopsproject 10y agoYou want to be in a profit center, not a cost center.
- randcraw 10y ago> Work somewhere where software is the main product and not just a cost center. This is THE big difference between S/W dev and IT. For 20 years I worked in the former, and for the past 10 in the latter. No question about it: IT is hell. Theirs is a never-ending mission to reduce the cost of moving data and being "compliant" with often-meaningless ever-excessive corporate standards (and forever meaningless MBA/CIO fads and groupthink). Worst, in most businesses, IT doesn't have a respected mission. Ii provides an infrastructural service (a cost center) that other C-suiters dis as no more important than HVAC and sewer. IT appears on their radar in only two ways: 1) when something breaks and info clogs up or stops moving, and 2) when the budget is revisited and interest in IT cuts are reinvigorated. Since nobody else in the corp. respects IT's mission, senior mgt. compels the CIO to adopt meaningless surrogate goals because IT's actual mission isn't sexy enough. So for the next six months IT adopts "Platforms" or trains half the staff in Six Sigma, or outsources, or insources, or promotes of whatever other CIO groupthink initiative is in vogue at the moment. So yes, work somewhere software is valued, unlike IT.
- kzisme 10y agoI've noticed this even walking around at work in different areas other than where I sit. "Hey aren't you in IT can you help me with my computer issue" One of the things I dislike the most is being referred to as "The IT Department".
- unixhero 10y agoI am now in Telco The only place where I've seen IT being highly respected.
- maxxxxx 10y ago"senior mgt. compels the CIO to adopt meaningless surrogate goals because IT's actual mission isn't sexy enough. So for the next six months IT adopts "Platforms" or trains half the staff in Six Sigma, or outsources, or insources, or promotes of whatever other CIO groupthink initiative is in vogue at the moment." That describes exactly the IT department in my company.
- 10y ago
- hasbot 10y ago> Work somewhere where software is the main product and not just a cost center. I've done both and I can't say one is better than the other. I've worked on software products where marketing couldn't figure out how to sell it and kept changing the core functionality. Or where the CEO kept shoving his ludicrous ideas onto development. I've worked on rewarding IT projects where I worked very closely with the users and was very happy to see my work help them perform their day-to-day jobs. I've also worked on slog IT projects where the users had no idea what they wanted and we kept churning. After 28 years, I ended up preferring working close to the actual users.
- fixed_carbon 10y ago"Marketing...kept changing the core functionality" "CEO kept shoving his ludicrous ideas onto development" Check and check. There's also my personal favorite: marketing informs the dev team they've just inked a big contract with a tight deadline for features that were never discussed with the dev team. "We kinda told them we already had those features but hadn't released them yet. Can you guys build that real quick like?"
- pvdebbe 10y agoClassic. Our supports operative just happened to promise full IE support (we promise only Firefox) just like that.
- walljm 10y ago> After 28 years, I ended up preferring working close to the actual users. This is key.
- sgt101 10y agothis! but also note users and access to them is what "IT" have and "software" often struggles with. Run some field trials, do interviews and field visits to support requirements analysis...
- lliamander 10y ago
- JoshTriplett 10y agoDepends on what you want: if you work at a company where software is the product (or the service), it can be harder to make the case for releasing software as Open Source. If you work at a company where, say, hardware pays the bills, that can make it far easier to make the case for releasing software as Open Source.
- root_axis 10y ago> Work somewhere where software is the main product and not just a cost center. You can learn a lot quickly if you do cutting edge things with people who care about technology and not just cost. Very true, but the company culture also needs to be right in order for this to really take hold. There's also the fact that the work and schedule will likely be more demanding. This can be a positive if you enjoy the work, but a big problem if you dislike unpredictable hours. When the company's primary revenue source is software, you will have to work extended hours at some point or another to solve critical business issues.
- laythea 10y agoI agree with all of this and I think there is a third category of job where is software is neither the main business, nor IT. Once you have developed the necessary software skills in a "software house", in my experience, the best thing to so is to get stuck into a particular domain, where the company needs software developed (not IT), but is not the main business. These jobs and contracts attract the best $, but also in my experience, highest job satisfaction - you are not just a cog - well, less so, IMO.
- maxxxxx 10y agoIf you want to distill it to one factor it's to make sure you and your function are a respected part of the company and not just something that's easily replaced. If you are in that position usually the $$$ is good and the work is interesting.
- deleted 10y ago[deleted]
- gyrgtyn 10y agoI didn't think I had an answer for this thread, but this is it. After many years, I finally found my way into a software company. It's weird here... I don't feel like everyone is mad at me all the time.
- dhruvkar 10y agoI worked in the IT department of an early software company (est. 1980) based in the Bay area. It was slightly better, since people understood software's value, and Ops was shared between the devs and IT. However, maintaining that sort of culture always felt like a constant battle. Management often slipped into IT = cost center. In fact, my job officially became bridging this gap as an IT Business Partner. I don't think I did a very good job.