I've started spending each github outage planning our move to an alternative. I guess I'm not alone. Where are you all moving?
"No moat", well... How I see this is that its so important to bundle the model with the right tooling. Like a racecar, having the best engine doesn't help if the rest of the car lacks other winning properties…
aha, so I need more karma
what, can I change the topbar color?
You have to realise there is a almost full complete disconnect between engineering and business value
Relatively long distances of road and power transmission lines to reach the two most remote locations. Especially considering they seem to be limited in capacity (only 319 and 469MW). Curious to know if something bigger…
I see it differently. I see the low-code stuff as an opportunity to let the business-folks handle the usecases where the complexity is low, and value of rapid iteration with deep domain-knowledge is more valuable. Also,…
> My main issue with low-code/no-code is that it attempts to solve the complexity problem, without understanding what "complexity" is. I get your point. But without low/no-code tools I would argue a lot of simple…
Not really. But you can tell your ISP it is not RFC compliant, I will tell mine.
I've started spending each github outage planning our move to an alternative. I guess I'm not alone. Where are you all moving?
"No moat", well... How I see this is that its so important to bundle the model with the right tooling. Like a racecar, having the best engine doesn't help if the rest of the car lacks other winning properties…
aha, so I need more karma
what, can I change the topbar color?
You have to realise there is a almost full complete disconnect between engineering and business value
Relatively long distances of road and power transmission lines to reach the two most remote locations. Especially considering they seem to be limited in capacity (only 319 and 469MW). Curious to know if something bigger…
I see it differently. I see the low-code stuff as an opportunity to let the business-folks handle the usecases where the complexity is low, and value of rapid iteration with deep domain-knowledge is more valuable. Also,…
> My main issue with low-code/no-code is that it attempts to solve the complexity problem, without understanding what "complexity" is. I get your point. But without low/no-code tools I would argue a lot of simple…
Not really. But you can tell your ISP it is not RFC compliant, I will tell mine.