I just realize that companies dont value a good developer, they just want a developer that can do the job done for clients to get money, i understand that just recently and im sad that some people are just in it for the money not for the love of the craft and technology.

  • 14
    There is a large difference between "conveyor belt" development and "intellectual property" development.

    Many devs start out working for small webdev companies, marketing campaign firms or mobile app studios.

    There is a sales department which sells a virtual product: "A custom webshop for $499! Informational iOS app for $999!" You get a few days to re-skin some shitcode home brewed by a "senior" dev, and the conveyor belt moves on.

    Then there are companies which develop an actual constructive product. The sales department sells a platform, a service, a subscription. Maybe it's not the best product, but at least it's already real. It still needs refinement, but that's why you were hired.

    That's a step up from conveyor belt duty.

    But there is another method for filtering the good from the bad. You might think it's "features vs quality", "new code vs refactoring". Balance there is important, but I'd define it as:

    Guidance by clients vs guidance by the mission.
  • 10
    Think about it:

    You might pay Spotify $10/m. If you ask Spotify to make a button blue, will they do it? Of course not. If you tell Google translate the must support CSV uploads or you'll stop using the service, they won't even respond.

    The companies most likely to survive are those who don't listen to individual clients.

    They have a vision.

    Of course, they validate the vision through market research, they study UX design, the aggregate feedback. But they are led by the "Composition of Mission and Data".

    Not by random requests from "important clients". Not even by gut feelings from a manager. Just a long term mission, and hard, verifiable data.

    I have no deadlines, I am driven by motivation.

    I'm not going to pretend the codebase I work on is perfect. It's the most complex 32 million-lines-of-code monster of a platform I've ever dealt with. Every day I find ugly long classes and buggy untested methods.

    But I'm building constructively on a product I love, with people I respect.
  • 2
    Check this oldie out (a must read for all ‘programmers’):

    ”Engineers are hired to create business value, not to program things: Businesses do things for irrational and political reasons all the time, but in the main they converge on doing things which increase revenue or reduce costs. ”
  • 1
    @bittersweet thanks for the info , i got tired getting to reskin some old dinosaur project for a new client.
  • 1
    @bittersweet thanks for this, i know what to look for now.
  • 2
  • 1
    @Cesar No problem
  • 0
    This is sadly very true. What’s harder to deal with is the higher up you get you notice that middle and higher management making decisions have limited technical understanding yet are responsible for choices that should not lie with them.

    However there are companies that do exists with amazing dev-led cultures. When you find them - stay! They are a rare kind.
Add Comment