Call me old fashioned but I have a hunch that the separated and minimalist approach has value in learning programming. To this day I still find doing things with minimalist tools I am far more productive than my counterparts who hunt and peck through menus and mouse clicks. A big advantage I think it this separation and minimalism primmed my brain to see way to compose tools and ideas instead or relying on what the system tells me I can and cannot do.

Something the article talks about is how morality is engendered not found. That the community teaches morality and that we need this or there are gaps in our humanity. Considering how we treat others is a learned skill it is also a taught and reenforced skill. How do we as a society wish our youths to treat each other? We need our systems to engender that.

A question I have with the process is: can email based workflow still work with for a continuous integration/delivery pipeline?

Been coding professionally for a few decades now and I completely understand and validate this. I also do not understand the drive to want tools that fight them. Our CI is so slow doing IMO unnecessary checks. Code is prettified to look ugly and hard to read because others were too lazy to align text manually and just gave up on nice looking code.

All in the name of “making it easier for the less experienced.” To which I cringe because instead of investing in education and team quality standards we invest in tools to enforce a lowest common denominator in a failed attempt to pretend it increases quality when it just gets in everyones’ way.

I’d rather educate and engender personal quality, aesthetics, and pride in their own work. And if others don’t feel that quality matters then they are not a good fit for my team.

Updates are scheduled and only components that need updating get their render method called. I even threw in a way to pass objects to child components by means of a yield method.

Just in case someone found it intereting.