Interesting enough this was not the result I was expecting, but makes complete sense. The foundation is systems here and I guess expecting something else was silly. I haven't touched any of the learning material, but sounds like a grade A job incorporating multi-facet challenges for systems administration and hands on scenarios. I found that diving in deep without the ability to ask for help and / or have resource material is the best way to go about a system if you truly want to understand it fundamentally, while this is a big task for most systems, you can subjectively break linux or anything else into several counterparts varying in complexities, entirely on how you feel, so the deep end in reality doesn't have to be that deep. Anyway, I was curious to know what everyone thought of the enterprise applications development / fundamentals, then realized they're from 2018-2019 (JB183)(DO292)(JB427) and some other blogs I found via search that don't have identifiers / terms. Then stumbled into (AD141) which was a few years back too, so now I'm curious to know what kind of programming studies you have for at least bash / shell scripting. The amount of usefulness a systems administrator can get from a few lines of shell, yeah it changes the game. I'm sure everyone would love it, maybe even more in depth development guides where the language can vary as far as dynamically typed perhaps, I guess the main ones would be C# (Relfection) - little more advanced, but could work it out, Python, Ruby, Groovy, Java (Reflection) - Easier imo than C#, JavaScript, Lua, Perl (maybe), PHP (maybe). Then even more in depth targeted outcome guides where you go from point A to point B with something structuring a full life cycle. Even a development environment tutorial would be a great for most people I think, start them off in nano or vim haha. Honestly I think most beginner developers stepping foot into the "enterprise" side of things could use an entire overview of that side of the coin and make it less dawnting when in reality it's mainly principal, ethics, and a strict governance of what you're doing - which sounds dawnting, but is easily broken down to expectations of an enterprise solution. Knowing these things out of the gate and having these kind of hands on learning avenues like you have for systems adminstration would definitely change the game. Also I will always stay true to C so whatever you got for that send it on out, I'll totally be down to review it. I may have completely lost topic here and maybe out of line, but I'm gonna hit the reply button anyway. I'm down to ellaborate or discuss any part.
Open Research and Development Laboratories
Enterprise Systems Architect
Kernel Engineer
|RH|FOSS|
Concurrency | Dynamics | Mutants | Memory Space
