On point.....

  • 2
    While this is true, people don't get that since most of us are paid not for the years of experience but time. It's an odd perception but people would gladly pay your wanted amount if you would take a long time to fix the issue, rather than a quick solution.

    Think of it like a restaurant:
    Fast food restaurants are fast and they are cheap.
    Michelin star restaurants are slow, and they are very expensive.

    ps. I know that the difference is deeper but every other person thinks like that :)
  • 2
    @potata there is a limit though. I don't fancy walking into a restaurant, ordering and then waiting an hour for the food to arrive regardless of how good or cheap the food is...

    What they are really paying for is the knowledge and experience that it took to quickly analyse the situation and put in place a solution that works and that should be maintainable.

    If it takes a dev 3 hours to do something and your paying them 50 an hour, or you have a different dev that can do the same in 1 hour but changes 100 an hour, there your saving money with the faster dev.
  • 1
    This might work equally well as a plaque on a sysadmin's desk or on the wall of a brothel.
  • 2
    I DID NOT mean to insinuate that IT employees are sometimes treated like brothel employees.

    Wait. Yes, I did.
  • 1
    @ftyross Well, you don't have to repeat that to me :) I perfectly know the situation but thinking about the average Joe - it's not uncommon for him to think like that :)
  • 1
    @ftyross And where does quality enter into your equation? How about documentation and readability?

    I'd pay more for a developer who:
    - Documented/commented his code well
    - Made his code extensible and/or easily modifiable
    - Wrote code that was well tested and worked

    Yes, experience matters but I've run into too many "over experienced" developers who write uncommented, unformatted code which handles only the primary use cases and blows up if anything approaching an edge case comes along.

    "But, it meets the requirements" is the true mark of a dev who no longer gives a shit.
  • 1
    Not true, you are owed for the (knowledge + skill) * time spent on the task

    How long you took to learn shit is irrelevant
Your Job Suck?
Get a Better Job
Add Comment