3 ms·

I totally understand that, but why not aiming high? Why we just say "you have experience configuring stuff, so we will just give you some extended json with tem

I totally understand that, but why not aiming high? Why we just say "you have experience configuring stuff, so we will just give you some extended json with templating, you won't be able to code....". I think this is bad approach (: We should always aim high and mentor those less experience to use programming languages for this. They don't need to know complex algorithms, distributed systems and performance optimization. It's really just more smart templating that is actually can be easier to use! (: > Templating systems are much more approachable for people who have a lot of experience configuring things via big blobs of text. I have mixed feelings about this statement. How reading or using jsonnet is easier? I am a principal engineer and I am struggling to work with this, how less expierience people can deal with that efficiently? (:

wpietri 7y ago
They can deal with it more efficiently because its model is closer to their current mental model, and so requires less cognitive load to achieve initial results. Gabriel talks about this under the label "worse is better". [1] I agree your preferred approach is better in the long term and at scale. But that only matters in the long term, and only if scale is eventually achieved. Tool adoption is generally a series of short-term decisions, and most projects start small. I agree mentoring people is great, but neither you nor I have time to mentor all the people just configuring things into becoming good programmers. [1] https://en.wikipedia.org/wiki/Worse_is_better https://en.wikipedia.org/wiki/Worse_is_better
- witcher 7y ago
  Interesting view, thanks. (: