This article states that failure-rate went from 8-9% to 25%, but I'm curious how that compares to the regional average. If say 35%-40% of 9th graders failed in surrounding regions, it would be an argument to keep the lottery based system.
94 karma · joined January 3, 2020
This article states that failure-rate went from 8-9% to 25%, but I'm curious how that compares to the regional average. If say 35%-40% of 9th graders failed in surrounding regions, it would be an argument to keep the lottery based system.
https://github.com/vmware-tanzu/carvel-kapp
https://github.com/k11n/konstellation
https://github.com/kalmhq/kalm (We ended using this one, which came with a set of matching web UI)
1) Tutorials <- starting point 2) How To <- intermediate 3) Reference <- comes back to it regularly 4) Discussion <- final step to understanding
However as the video mentions, it's all connected in a circle, as perhaps having some discussion up-front(why, context, alternatives) is useful for newcomers to evaluate whether this project is worth diving into.
Curious as to whether the author(and everyone) thinks on how much "discussion" should be put into the "Getting Started" page.
Doing all MOOC is bad for some of the reasons the articles covered. But doing all projects is also sub-optimal because sometimes it is hard to know what you don't know. Balancing theory and practice works the best for me.
In that case it's mostly the parents that subsidize the lifestyle up until college level.
"you want to do it without having to standup layers of infrastructure on AWS or be beholden to the legacy players like Heroku or other providers who don’t get that you want the same Netlify like experience on the backend."
So exactly how is Heroku "legacy"? From past experiences pushing a simple backend service onto Heroku was pretty smooth and "Netlify-esq".
It would be nice to explain or show the shortcomings of using Heroku as the backend for your Netlify app.