4 ms·
The problem would be picking all the bits of tech, so much of what you're talking about is stuff you learn when you start working with your first big ball of mu
by gonzo41 9y ago
The problem would be picking all the bits of tech, so much of what you're talking about is stuff you learn when you start working with your first big ball of mud.
Lets use java for simplicity. We're going to do a non trivial app thats web based so we dip into the exciting worl of java EE.
Learn about
maven
eclipse
jax-ws
jax-rs
cfx tools
wsi tools
Hibernate stuff
DB stuff.
Probably need to throw spring boot or cdi onto the pile of things to be a little familiar with.
Then you need to teach how app servers work. getting one setup. which computer/ os etc.
Zooming in take the build process, 'Setting up jenkins' Thats a big tutorial all on its own. you'd need to know Git or SVN or one of the others.
then you step into building a CI pipeline, Building a test suite, functional, unit and integration test. building reporting ontop all of that.
That would be mega tutorial series. And the moment you finished it, people would start pulling strips off it for being out of date. Or they would attack it for language and tooling choice.
- qwerty456127 9y agoPerhaps a good list of all the subjects with detailed commentaries could do. One could go find tutorials on specific parts then given the knowledge o what to look for and what's that about. May be short (yet illustrating the way it's done in the real world) examples on particular subjects could be included.
- gonzo41 9y agoThat would be one way to go, and probably a pretty good one. But yeah, the churn in the industry is crazy, so it would be some work to compile a list that's coherent and orthodox that didn't go out of date the moment you published.