From the career point of view, I've seen many programmers, more or less, in the long run, specialize in the industry|ies they've been working, so the business practices, ins and outs and logics became part of their strong point in that|those industry|ies.

But I found myself on the opposite side, I could care less about the business's practices, etc. because in the end I'm mostly passionate about reaching some technical satisfying accomplishment or a novel approach to solve some kind of problem or just learn new approaches.

So when I'm handed info mostly focused on business practices|logics I just boringly read through it.

How about you?

Obviously business problems and technical feasibility to solve them overlap. But wouldn't be better to have people capable to express their issues more from technical points of view than talking nonsense to someone who's clueless about the business <.<?

  • 1
    In some companies, team members are separated into two - technical and functional. The technical ones are the developers who of course have to know how to code. The functional ones can be accountants or other business specialists who use the application and have knowledge with the business. Some simply assign a business analyst to communicate between the non-technical people and the developers.

    I prefer the technical side as well. I didn't bother much with the business side although it does give you an edge over everyone else. Maybe if you want to focus on a specific industry, that would be nice.
  • 0
    @rutee07 I'm more prone to all-roundness because of my Jack of all trades way. So I'm likely to reach as many industries as I could even without a common theme u.u

    How many industries have you crossed?
Your Job Suck?
Get a Better Job
Add Comment