Conversation
Notices
-
One of Epic's commandments is not to get acquired. Judy, the founder, put in a lot of legal work to try to make sure those values are upheld even after her death or incapacity.
And even if that weren't the case, Epic is far enough removed from our core competencies that it wouldn't happen.
Also, Epic is bigger than us, and as it turns out Epic doesn't also acquire (although there has been a little wiggle room there but they aren't acquiring us).
- LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} likes this.
-
#Louisville, #CO or #Minneapolis, #MN
Requirements:
Minimum of five years of software development and design or systems administration or level 3-4 technical support experience.
Technical knowledge, skills and expertise in complex infrastructure, web-based software and enterprise software
Understanding of software best practices; SDLC, SCM and Agile development principles.
Excellent written, verbal, and presentation skills
Expert level in a number of open source packages.
Broad and deep familiarity with multiple projects to include Java and #J2EE, #JBoss, #ActiveMQ, #Drools, #HornetQ, #Hibernate, #Spring, #Linux (focus primary on #CentOS or #Ubuntu), Apache HTTPD, #Apache #Tomcat, #MySQL, #PostgreSql, Open source project and community participation and Production/24x7 experience.
Database administration; postgresql/ mysql/ #mariadb experience very desirable
Expertise in #Cassandra, #Kafka, and/or cloud-native applications is a plus.
Responsibilities:
Interact with end users on technical problems.
Tier 1, 2 and 3 support for CentOS and related open source products.
Drive resolution of those problems, which include:
Open source software issues.
Questions around open source software usage.
Questions around use and best practices.
Review of the architecture and design where software is implemented.
Conduct professional services and training engagements.
Research, understand, and advocate open source software.
Interact with various open source communities.
Drive early resolution of issues.
Be a part of the on-call rotation.
Present knowledge via articles, blogs, and conference presentations.
May require 15% travel while completing on-site consulting.
https://www.perforce.com/careers/open-jobs?gnk=job&gni=8a7885ac6dcbf35f016df97b13130e54
-
it's highly unlikely I will get pulled into any acquisition discussions unless it were an entity in the monitoring space, and even then, doubtful unless Nagios itself
-
@musicman There are both pluses and minuses to acquisitions, but there does seem to be a size at which any organization becomes anti-people, including anti-employee. I’ve also noticed that not every sub-organization reaches that point at the same time or goes the same distance down that road as the rest of the (parent) organization.
Not saying that #Epic is or is not pro-people (or anti-people). Just a general observation.
(I do groan inwardly when I hear people saying they want to leave private industry because they perceive #USGovt as being more warm and fuzzy. They aren’t.)
-
Much like the private company, I greatly suspect it depends on what agency/branch and what position in said agency/branch.
I never had a conversation with Judy, though I was in her office for support once, but my impression is the reason for not getting acquired was to keep the value of "Do Good, Make Money". Of course, her interpretation of "Do Good"
They added the Make Money at some point because apparently someone (devs, sales, not sure...) was giving away the software. I am so happy to be working in #opensource now, even if it's only a little sliver of Perforce.
Douglas A. Whitfield
LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
All Chirp! content and data are available under the