Is part of the issue dev perception? I worked to keep devs out of Puppet. It was invisible to them. Now they’re finding themselves having to do infra code that others did for them before.
-
-
Replying to @tmclaughbos @chrismunns
there's also this weird resistance to declarative code that I'm seeing. Lots of config approaches are being driven by "let devs code it in JS because that's where they're comfortable", which I sort of get, but seems like in the long run loses a lot of benefits
3 replies 0 retweets 4 likes -
I'm in this camp. I see both sides. To me, there is a big benefit to JS everywhere. By turning JS into a declarative plan can't we get the best of both worlds?
1 reply 0 retweets 0 likes -
I don't think so. The JS is what gets checked in to source control, and thus you lose the easy inspectability and language independence
4 replies 0 retweets 2 likes -
Replying to @ben11kehoe @southpolesteve and
Interested to hear more about this - IME sufficiently complex declarative config isn’t that inspectable either way.
2 replies 0 retweets 0 likes -
Replying to @mweagle @ben11kehoe and
In my ideal world there is only application code. Tooling can staticly analyze (or run) that code and output a set of isolated functions and a declarative infra plan.
2 replies 0 retweets 0 likes -
Replying to @southpolesteve @mweagle and
In my ideal world, application code approaches zero, and there's only configuration.
2 replies 1 retweet 3 likes -
Replying to @ben11kehoe @southpolesteve and
k - for extracted infra plan I'd be concerned that "annotations" of some form would be required to provide service-specific params. For config-only, do you imagine that's the representation people would edit (eg: XProc/XSLT style)?
2 replies 0 retweets 0 likes -
Replying to @mweagle @ben11kehoe and
Isn't java era XML config hell what we are all running away from? that was before my time so I really don't know for sure.
1 reply 0 retweets 0 likes -
Replying to @southpolesteve @ben11kehoe and
Yes - there was a "XML all the thingz" movement that seemed to punt intrinsic application awareness to a runtime, external "config problem".
1 reply 0 retweets 1 like
I would like some resource to learn about dev from ~90's into early 00's. So much of what we do seems to be reactive to practices of that era. I wish I could connect the dots better.
-
-
Replying to @southpolesteve @mweagle and
History is definitely path-dependent. We're often stuck with suboptimal solutions. At best, we learn to accept it and work with it. At worst, we convince ourselves it's actually the best of all options.
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.