• Maciejasjmj (disco)

    You know, "Experience Your Own Support Stories" might not be the best way to market yourself on a website where "support stories" mean "tales of clueless idiots working front-line customer service"...

  • JBert (disco) in reply to Maciejasjmj

    On the upside, people who do respond are very motivated if they still want to do this whilst knowing what they get themselves into.

    That or they're certifiably crazy.


    Filed under: Also INB4 "both"

  • apapadimoulis (disco) in reply to Maciejasjmj
    Maciejasjmj:
    You know, "Experience Your Own Support Stories" might not be the best way to market yourself on a website where "support stories" mean "tales of clueless idiots working front-line customer service"...

    Fair point... although it seems a lot of the support stories are from the other perspective.

    Anyway, you know makes a fine single malt even nicer? Having it at the conclusion of painful/difficult support experience.

  • Nprz (disco)

    This part:

    you could reach an expert/mastery level in a very short time (what would take most developers ten+ years), but it will require a lot of dedication and a lot of a hard work.

    Sounds like something we've discussed in another thread. But instead of paying $40, I get paid? Sounds too good.

  • machtyn (disco)

    This is quite nice. Coming out of college, I was still intimidated and uncertain if I could be an actual developer. (It turns out I can.) So I went into QA where I started writing tools to assist QA. But at that first job, the QA was overworked and under-appreciated. So, on to contracting in QA. Finally a number of years later, I get to work on automation, C#, Selenium... it's been great! And I've found out I'm really pretty good at this programming, developing thing. I'm not going to be happy going back to writing test documents and manual testing.

    My point is that it is good that there is a company that provides a quick path to build confidence, training, and mentorship in development through these alternate paths. These alternate paths also produce a more rounded developer (as they understand the QA or support world.)

  • SirNuke (disco)
    Comment held for moderation.
  • Yamikuronue (disco) in reply to machtyn

    Any idea how I can attract people like you? I'm having trouble finding good QA contractors in my area >.>

  • dkf (disco) in reply to SirNuke
    SirNuke:
    Programming really isn't that radically different on a certain level, and saying you'll pick up 10+ years of coding experience in radically less than 10+ years of time triggers "scam scam scam."

    Like many primarily-mental activities, it takes around 10 thousand hours of diligent effort to achieve mastery in computer programming. For most people, that in turn takes about 10 years to do (because life and goofing off take up the rest). Be better at sticking to the required type of learning and you might shorten the number of years a bit, and spend your time not learning and you'll never get to 10k hours.

  • Luhmann (disco) in reply to dkf
    dkf:
    10 thousand hours of diligent effort
    [image]
  • dkf (disco) in reply to Luhmann

    You don't need to do all that. After all, you don't need to be an expert. ;)

  • Luhmann (disco) in reply to dkf
    dkf:
    you don't need to be an expert.

    A little bit pedantry and dickweedery should just get the job done

  • algorythmics (disco)

    "We need a support analyst, but don't worry, you won't be on support forever!"

  • serguey123 (disco) in reply to apapadimoulis

    Am I the only one that think "purising" spirits is wrong? Anyways, you should also hire a proofreader for your website.

  • izzion (disco) in reply to algorythmics
    algorythmics:
    "We need a support analyst, but don't worry, you won't be on support forever!"

    After all, we have to pull the plug at some point, it's the only humane thing to do.

  • apapadimoulis (disco) in reply to SirNuke
    SirNuke:
    Let's not pretend, however, that you can work @ Inedo for a year and "reach expert/mastery level."

    Definitely not, and that's why I tried to keep it non-specific ("you could reach an expert/mastery level in a very short time"). I think, absolute miminum, 3 years; and that's dedicating most nights and weekends, and working closely with mentors. But more realistically, 5 years... and largely a result of longer days and a low bullshit-to-work ratio.

    serguey123:
    Am I the only one that think "purising" spirits is wrong? Anyways, you should also hire a proofreader for your website.

    Just checked, and both Merriam and Webster agree with you. So, I fixed it. Thanks.

  • Nprz (disco) in reply to Yamikuronue
    Yamikuronue:
    Any idea how I can attract people like you? I'm having trouble finding good QA contractors in my area >.>

    Obviously people like him don't stay in QA long enough to be recruited. And he also said he ain't going back (unless he can't find another dev job).

    I also had my start in QA. At first I was astonished at how the dev at my company could produce such complicated things. So I told myself (and others) that if I went into dev, it probably wouldn't be at the company I'm at. Fast forward (checks linkedin profile) ~5 years and I made the jump to dev because I felt I was doing enough debugging of problems and my automation was better than some of the production code. So, it is nice to have a place to spring board. My only regret was going from being some all-star QA to just another dev.

Leave a comment on “Experience Your Own Support Stories at Inedo”

Log In or post as a guest

Replying to comment #:

« Return to Article