Any thoughts on applying #Agile development to the job of managing a website for an organization with very little in-house digital tech expertise? Obviously I'm not talking about a static brochureware site. I'm envisioning a portal site that offers extra features to both visitors and logged in members, such as Q+A tools, discussion forums, geographical localizations, and handling payments for membership dues, event registrations etc.
@kravietz I guess it depends whether we're talking about home/ community use or institutional use. Individual users choosing whichever distro suits their needs is fine. But for use in governmental organisations, a GNU/Linux distro customized for their needs (like #LiMux) would be necessary for security auditing, efficient rollout and end user support etc. Not to mention the UX can go through an #agile design process involving some of the public servants and general public who will use it.
It's pretty demoralizing to never get any responses from anyone but @lnxw48a1, but I am nothing if not persistent.
I realize I could interact more and gain more followers and I could post more. Maybe I'll give Mastodon a shot a see if I get more interaction there. I don't think I've joined an instance but maybe I have.
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
Role: Open Source Staff Engineer/Solutions Architect
Location: #Louisville, #CO or #Minneapolis, #MN
Position Summary:
Perforce is seeking a Open Source Staff Engineer/Solutions Architect to join our OpenLogic team. As a member of the support team, you’ll be responsible for assisting our clients to work through their technical questions on open source including ‘how to’, trouble shooting and recommendations on product use. Additionally, based on needs of our customers, you will be involved in presenting training classes (both onsite and remote depending on need of the client); short-term professional service engagements to assist with architect and design solutions; working on internal projects; and enhancing current skills by continuing to learn new open source technologies.
OpenLogic provides enterprise services for hundreds of open source projects — including #OpenJDK, #Kubernetes, CentOS, and #MariaDB — so you can boost efficiency and savings with free software, while cutting risk.
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.
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.
Make strategic contributions to the CentOS core and surrounding ecosystem, provide bug fixes ahead of the community where needed
Be a part of the on-call rotation.
Present knowledge via articles, blogs, and conference presentations.
Requirements:
Technical knowledge, skills and expertise in complex infrastructure, web-based software and enterprise software
Strong knowledge of the Linux #kernel and system architecture.
Understanding of software best practices; #SDLC, #SCM and #Agile development principles.
Ability to develop with #C / #C++ in a UNIX environment.
Utilization of common #Linux C/C++ build tools such as #gcc.
Solid understanding of CentOS 6.x and 7.x and included frameworks like #firewalld, #systemd, etc.
Strong #RHEL/CentOS background required
#Debian / #Ubuntu, #SUSE / #openSUSE / #SLES, other distro background a bonus
C, shell scripting, #perl, etc
Virtual Machine experience with #qemu / #kvm, #Azure, #AWS, #VirtualBox, #Vagrant
General experience such as: radius/Kerberos, lda, ipa/idm, monitoring, vpn, containers, centralized systems management, automation (ansible, chef, puppet, etc), version control (git, etc) or security hardening (CIS, STIGS, PCI-DSS, etc)
Excellent written, verbal, and presentation skills
Knowledge of open source packages
Database administration; #postgresql / #mysql / #mariadb experience very desirable
Experience with Linux distro package building (#rpm, #deb, #ipkg, etc) preferred
Existing contributions to the CentOS community a major plus
My new team (and my old team too, actually), is looking:
Interact with end users on technical problems.
Tier 1, 2 and 3 support for #CentOS and related #opensource 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.
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.
@AbbieNormal > And it's not a given that users know what they want
Users are the *only* people who know what they want from software. That's why #agile practices that involve end users in the design of user-facing software produced better software, faster, and cheaper, than waterfall methods. They won't always share their needs with the developer, true, but that's all the more reason not to put a paywall between them and the place they can do so. @bhaugen@Wolf480pl@rysiek@sullybiker
@LWFlouisa@wuhei@Goffi there's a whole field that needs to develop (and is developing) around designing #UX for free code software. What's been happening for a long time devs writing software and pushing at users. What some of us need to be doing is talking to communities that need software, and describing exactly what they ask for in terms devs can easily understand, quickly prototype, and get the community to test it and give feedback. #user-driven #agile development!
@nmashton that's a good question. I was reminded recently that one of the core principles of #agile development is "people over processes". Like permaculture, it's not about imposing cookie-cutter templates, but designing for a context. is about teams and organizations collaboratively designing the process by which they collaborate, by reflecting on what they've tried, what worked, and what didn't (the clue is in the name - *agile*). All the agile methods are just tools to be used as appropriate