On the css side, I can tell you that rio (that is by no means the first library of its kind) actually does not require any knowledge of css to be used. It does not use the same concepts. While the simplification costs you some levels of customization, it is not something that would truly matter in a lot if not most of its use cases.
The simplified layout system comes with its own inspection tool built into the dev version of your app so you get productive in an hour or so. They really got that part right in my opinion. As soon as they make custom components done I’m gonna discuss adopting it for our internal tooling.
Yes - they have more legs. But what they are not is a homogenised mass, all as equally guilty or innocent of issues as the other. If 3 executives do something bad, those 3 executives are to blame. And not some nothing-to-do-with-people corporation.
But that’s the point - it’s just a promise. I have a similar career as the top comment, and turns out that Low code approaches only work when people who understand code use them. Be that Python or sql, real use cases are not the toy examples shown in all typical introductions to these tools.
That said, if this thing is customizable enough, a good data engineer can prepare canned steps that fit the general structure of the customer data process and it may have its place.
I imagine the use-case for low-code tools is when your ratio of "business experts" heavily outweighs programmers, and the cost of inefficient dev processes/tech debt is less than the cost of waiting to onboard people with a coding background.
Sure, but when fighting asymmetric warfare self control is paramount is it not?
Would you not be mad at the guy bragging that he’s a member of the Resistance? They are not the Oppressor with the capital O, but they are at least an asshole.
> A good example of this at the human level is a reflex. Your hand didn't go back to your brain to ask for instructions on how to get away from the fire.
Is this actually true? I thought it just involved a different part of the brain. Is there actually no brain involvement? Sure it does not need your awareness or decision making, but no brain? I find that hard to believe.
>A reflex arc is a neural pathway that controls a reflex. In vertebrates, most sensory neurons do not pass directly into the brain, but synapse in the spinal cord. This allows for faster reflex actions to occur by activating spinal motor neurons without the delay of routing signals through the brain. The brain will receive the input while the reflex is being carried out and the analysis of the signal takes place after the reflex action.
One way of seeing a subset of reflex behavior is speculative execution - as in, you'll start executing on stimulus before the brain has a chance to evaluate it, but when it eventually does, it may cancel the reflexive action. This is absurdly efficient if your reflexes are well-calibrated.
You pass an open api spec on creation. You can remove all methods you fear may be risky, and leave it enough so that he can read your emails or calendar, if you feel comfortable with that
The simplified layout system comes with its own inspection tool built into the dev version of your app so you get productive in an hour or so. They really got that part right in my opinion. As soon as they make custom components done I’m gonna discuss adopting it for our internal tooling.
I am not affiliated with them btw.