On Tue, Aug 6, 2019 at 10:27 AM G. Matthew Rice <[email protected]> wrote:
> Well, I'm glad you guys all learn everything in 10 minute sprints. I > still take half an hour to make a 3 minute egg. > I would argue that while these things can be learned in 10 minutes, 'muscle memory' and 'from experience' takes at least 3 hours ... likely spread over 3 days.** You keep saying 'automation track'. Maybe we could expand the DevOps cert > into a full and separate track (or diverging) and include some of LPIC-1 > (and LPIC-2)? > So, again, I want to preface that with ... 1) bjs was just saying the 'get away from bjs-like old fart stuff' or 'weighing it far less heavily than old-fart bjs wants' means ... 2) there *may* -- I stress *may* -- be merit to look at the 'future purpose' of LPIC-1 (and even LPIC-2) overall Right now another certification entity (*cough*Red Hat*cough*) has been in this cycle of changing things around, and it's now very different than it was just 5 years ago. One can get a RHCSA or RHCE without even passing a general RHEL exam, in addition to the specialty exams that don't require a RHCSA or RHCE as pre-requisite. Most of these changes are the last 3 years. So ... is Vi important today? Are sysadmins just 'interactive' and 'break-fix'? That's a really good question. Hence ... this is really for Fabian et al. to look at and possibly seeing where DevOps may or may not be overlapped with LPIC-1 (or even LPIC-2), if there shouldn't be more options in the 100 (or even 200) tracks, or if it's not viable. I was just trying to play my own 'devil's advocate.' Because I'm of the viewpoint ... A) If LPIC-1 will still be considered (future) 'interactive' and 'break-fix' support sysadmin, and editing is the common denominator, then Vi is probably still one of the most important skills for LPIC-1, especially as a foundation, or ... B) If LPIC-1 will not so much be (future) 'interactive' or 'break-fix' but can encompass a new focus on 'mo'better' and 'newer' stuff, then maybe we outta look at a new approach I'm an old fart and, worse yet, I also have a traditional engineering degree, so to me, Vi is like calculus ... you cannot do most anything else in engineering without it, just like a sysadmin that is 'interactive' and 'break-fix' cannot live without Vi in the Linux world. But at the same time, there are all sorts roles for sysadmins in the modern world, just like technologists in the engineering world, who don't need calculus and mechanics. So ... that's really the debate in my eyes. I know many will differ that we can reduce (even if not eliminate) Vi coverage, to cover other topics, but I really think it should be a far greater change. I now leave it to others to discuss. - Self-aware, 'old-fart' bjs
_______________________________________________ lpi-examdev mailing list [email protected] https://list.lpi.org/mailman/listinfo/lpi-examdev
