Jonkman Microblog
  • Login
Show Navigation
  • Public

    • Public
    • Network
    • Groups
    • Popular
    • People

Conversation

Notices

  1. musicman (musicman@nu.federati.net)'s status on Wednesday, 11-Apr-2018 11:29:17 EDT musicman musicman
    #hiring Technical Support Analyst - Check out this great #job at my company #jobopening #applynow http://bit.ly/2EDYRqf

    This is for the #Australia office, and you must know #Chinese.
    In conversation Wednesday, 11-Apr-2018 11:29:17 EDT from nu.federati.net permalink

    Attachments

    1. Now Hiring: Perforce Software, Technical Support Analyst - Sydney, Australia
      Position Title: Technical Support Analyst Location: Sydney, AUS Reports to: Director of Professional Services & Support * The heart of a startup. * The stability of an established company. * Software that accelerates innovation at the world's leading companies. Apply to Perforce today if this sounds interesting to you! We're a leading global software company looking for smart, fun, talented team members. At Perforce, you'll enjoy competitive benefits while working with and learning from some of the best and brightest in business. Before you know it, you'll be in the middle of a rewarding career at a company headed in one direction: upward. **Position Summary** Perforce is seeking a Tier 2, Technical Support Analyst to join our Global Support Team, liaising with members from Sales, Professional Services and, Development to assist in resolving a wide variety of customer issues. You would be responsible for ensuring the success of our customers by effectively providing dependable and timely resolution to Perforce's Helix Core software. The ideal candidate is expected to be self-motivated, proactive, results- oriented and able to provide a high level of customer satisfaction through the delivery of world-class technical support services. **Essential Functions** * Represent Perforce as the first point of contact for their technical support queries. * Review scope of customer issue and determine best course for resolution. * Develop and maintain technical expertise in assigned areas of product functionality and utilize it effectively to help customers. * Resolve customer issues expeditiously. * Resolve database and performance issues. * Research, document, and escalate cases according to procedure. * Customer driven feedback to functional areas in order to influence process/product improvements. * Author technical documents on common issues and solutions in order to build the knowledge base. * Positive attitude - Support engineers are required to be respectful, fair, gracious, and knowledgeable. * Create and set up test environments. **Required Education, Experience and Skills** * Ability to speak Mandarin Chinese and English fluently * 2 or more years' experience providing support directly to enterprise customers. * Technical or Bachelor's Degree in IT, CS or similar. * Linux experience * Basic networking experience * Outstanding customer service skills. * Strong analytics and problem-solving skills. * Ability to work in a team. * Excellent written and verbal communication skills. * Able to work well under pressure and prioritize accordingly. * Organized and dedicated. * Good attention to detail. * Experience with Perforce, Git, or other version control software is desirable. **About Perforce** Enterprises across the globe rely on Perforce to build and deliver digital products faster and with higher quality. Perforce offers complete developer collaboration and agile project management tools to accelerate delivery cycles -- from agile planning tools to requirements, issues and test management, which then link to all source code, binary assets and artifacts for full build and release tracking and visibility. The company's version control solutions are well known for securely managing change across all digital content -- source code, art files, video files, images, libraries -- while supporting the developer and build tools your teams need to be productive, such as Git, Visual Studio, Jenkins, Adobe, Maya and many others. Perforce is trusted by the world's most innovative brands, including NVIDIA, Pixar, Scania, Ubisoft, and VMware. The company has offices in Minneapolis, MN, Alameda, CA, Mason, OH, the United Kingdom, Finland, Sweden, Germany, and Australia, and sales partners around the globe. For more information, please visit [www.perforce.com](https://www.perforce.com/). **Perforce is an Equal Opportunity Employer: Minorities, Women, Veterans, Disabilities**
    1. clacke (clacke@social.heldscal.la)'s status on Wednesday, 11-Apr-2018 11:58:42 EDT clacke clacke
      in reply to
      @musicman Is that your new company? You were with Nagios, right?
      In conversation Wednesday, 11-Apr-2018 11:58:42 EDT from social.heldscal.la permalink
      1. musicman (musicman@nu.federati.net)'s status on Wednesday, 11-Apr-2018 12:43:32 EDT musicman musicman
        in reply to
        That's correct. I went from a little over 8.5 miles one-way to ~8.5 blocks. I suppose I should have sent that post to !vcs, since it's actually perforce and git related, and not just a, say, finance position. We did have have #gitfusion and #gitswarm, but those are deprecated and now we have #Helix4Git. I don't have a sense yet for how much I'll be able to stay in git land, but we do have a fair amount of FLOSS tooling at https://swarm.workshop.perforce.com/ -- for the most part, I don't think the stuff there is useful outside of perforceland, but some of the #SDP stuff could pretty easily be refactored to work with other products, I think. This is what one of our consultants that occasionally works on the SDP said anyway, and I understand his argument. It's a step backwards as far as FLOSS-ness, but before I agreed to an interview I made sure there would be no restrictions on me contributing to Apache or git. There are not. It might be different for someone hired as a developer, but that doesn't really matter for me personally since that is not, and likely will never be, my role.
        In conversation Wednesday, 11-Apr-2018 12:43:32 EDT from nu.federati.net permalink
        1. clacke (clacke@social.heldscal.la)'s status on Wednesday, 11-Apr-2018 13:02:59 EDT clacke clacke
          in reply to
          @musicman Didn't know Perforce did any free software at all. Thank you for broadening my knowledge.
          In conversation Wednesday, 11-Apr-2018 13:02:59 EDT from social.heldscal.la permalink
          1. musicman (musicman@nu.federati.net)'s status on Tuesday, 17-Apr-2018 16:57:40 EDT musicman musicman
            in reply to
            so, I did not realize this until about 5 minutes ago, but our primary command line interface is BSD and appears to have been since at least 2014: https://swarm.workshop.perforce.com/projects/perforce_software-p4/files/2018-1/LICENSE

            I still think it is weird that BSD has "All Rights Reserved" right up there at the top.
            In conversation Tuesday, 17-Apr-2018 16:57:40 EDT from nu.federati.net permalink
            1. Ben Pfaff (blp@quitter.se)'s status on Tuesday, 17-Apr-2018 17:06:21 EDT Ben Pfaff Ben Pfaff
              in reply to
              @musicman @clacke "All Rights Reserved" is more of a magical legal formula than any particular statement of license.
              In conversation Tuesday, 17-Apr-2018 17:06:21 EDT from quitter.se permalink
              1. clacke (clacke@social.heldscal.la)'s status on Tuesday, 17-Apr-2018 20:57:02 EDT clacke clacke
                in reply to
                @blp @musicman Actual lawyer Richard Fontana disagrees and spent energy and time during his time at Red Hat to get rid of it on the Fedora sites. It is a contradiction to first reserve all rights and then turn around and give them away one line later.
                In conversation Tuesday, 17-Apr-2018 20:57:02 EDT from social.heldscal.la permalink
                1. Ben Pfaff (blp@quitter.se)'s status on Wednesday, 18-Apr-2018 12:29:39 EDT Ben Pfaff Ben Pfaff
                  in reply to
                  @clacke @musicman Well, if it can be gotten rid of, I agree that's even better.
                  In conversation Wednesday, 18-Apr-2018 12:29:39 EDT from quitter.se permalink
                  1. clacke (clacke@social.heldscal.la)'s status on Wednesday, 18-Apr-2018 14:11:18 EDT clacke clacke
                    in reply to
                    @blp @musicman It's redundant at best, contradictory at worst. They should get rid of it.
                    In conversation Wednesday, 18-Apr-2018 14:11:18 EDT from social.heldscal.la permalink
                    1. musicman (musicman@nu.federati.net)'s status on Thursday, 19-Apr-2018 09:32:57 EDT musicman musicman
                      in reply to
                      The way Bradley Kuhn explained it to me when I was on the Johns Hopkins legal team was that the idea was that the All Rights Reserved applied to the copyright notice itself, but I still don't think that's the intent, since I don't think anyone would mind if they created a different license for a new project. Really, what's needed is a definition of the license, and then you can reference it. I don't think the current text is ambiguous, but I think that would be best practice to eliminate the doubt.
                      In conversation Thursday, 19-Apr-2018 09:32:57 EDT from nu.federati.net permalink
              2. musicman (musicman@nu.federati.net)'s status on Thursday, 19-Apr-2018 09:16:50 EDT musicman musicman
                in reply to
                I don't remember any such magic from law school. This sentiment likely stems from the US pre-Berne. The whole Berne thing is super-complex because the bill was in '76 if memory serves. Started in '78. We didn't "fully" go in until '88 (or '89), and really didn't go in until Golan v Holder...in 2012. And I think VARA was '94. What a complete and utter mess.
                In conversation Thursday, 19-Apr-2018 09:16:50 EDT from nu.federati.net permalink
            2. clacke (clacke@social.heldscal.la)'s status on Tuesday, 17-Apr-2018 21:02:33 EDT clacke clacke
              in reply to
              @musicman BSD generally doesn't have it, just they by reflex included it with their copyright statement.

              https://opensource.org/licenses/BSD-2-Clause
              In conversation Tuesday, 17-Apr-2018 21:02:33 EDT from social.heldscal.la permalink
        2. clacke (clacke@social.heldscal.la)'s status on Wednesday, 11-Apr-2018 13:06:58 EDT clacke clacke
          in reply to
          @musicman Getting that kind of relief in your commute situation does sound like a move up. I'm happy for you that you could find something that close.
          In conversation Wednesday, 11-Apr-2018 13:06:58 EDT from social.heldscal.la permalink
          1. musicman (musicman@nu.federati.net)'s status on Wednesday, 11-Apr-2018 15:27:04 EDT musicman musicman
            in reply to
            yeah, I think if !nagios had better community relations the commute might have been worth it, but the #icinga fork really soured things for a lot of people on both sides (I suppose that pretty much always happens, to some extent). Nagios LLC still takes contributions on Core, but it may be that contributions were being rejected that competed with XI.

            We'll see how things go at Perforce, but my hope is that after my non-compete is over Tarus will have some remote openings at #OpenNMS. Back in 2007, OpenNMS sponsored a conference I spearheaded. They were a local-to-me company at the time.

            As far as I'm aware, perforce is still gratis for people working on open source projects. Why, in 2018, anyone would do that, I'm not sure. I'm not sure when the policy started, but I bet back before #git, that actually meant something to people.
            In conversation Wednesday, 11-Apr-2018 15:27:04 EDT from nu.federati.net permalink
            1. clacke (clacke@social.heldscal.la)'s status on Wednesday, 11-Apr-2018 15:37:48 EDT clacke clacke
              in reply to
              @musicman I don't know OpenNMS. There's probably a FLOSS Weekly ep about it I should listen to.
              In conversation Wednesday, 11-Apr-2018 15:37:48 EDT from social.heldscal.la permalink
              1. clacke (clacke@social.heldscal.la)'s status on Wednesday, 11-Apr-2018 15:42:16 EDT clacke clacke
                in reply to
                @musicman Ha! Not only one, they were there right at the beginning too!

                https://twit.tv/floss15
                https://twit.tv/floss418
                In conversation Wednesday, 11-Apr-2018 15:42:16 EDT from social.heldscal.la permalink
                1. musicman (musicman@nu.federati.net)'s status on Wednesday, 11-Apr-2018 15:46:06 EDT musicman musicman
                  in reply to
                  they are compatible with NRPE...and a bunch of other stuff. I don't really know anything about OpenNMS other than that. :) I should fix that, but I think the first priority is learning Spanish since I want to go to South America and my wife pretty much said knowing Spanish was a prereq....even though we could easily go to Bueous Aires (I know this is incorrect, but do not care enough to find out the correct spelling) where my old roommate lives or to Georgetown (which is in the only English-speaking part of South America...but whatever, I don't make the rules, I just follow them)
                  In conversation Wednesday, 11-Apr-2018 15:46:06 EDT from nu.federati.net permalink
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

Jonkman Microblog is a social network, courtesy of SOBAC Microcomputer Services. It runs on GNU social, version 1.2.0-beta5, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All Jonkman Microblog content and data are available under the Creative Commons Attribution 3.0 license.

Switch to desktop site layout.