The concept is interesting. In our experience with regular and top teams trying to do notebooks for runbooks.. there are a lot of gaps around the Jupyter UI specifically and the concept in general. It's a fascinating problem to work on.
None of the text on the landing page makes it clear what this is about other than the downright bizarre lip service about the "open source community" -- like, ok, that's nice, but I'm on this page because I want to know what this is, and I'm not going to invest more than a handful of seconds to figure that out. At this point knowing you care about the "open source community" means nothing to me, and you don't have any other information on this page other than your "open source community" lip service
The GH repo is somewhat better, but you have to figure that some (most?) people aren't going to bother to scroll below the fold -- which is just a listing of folders/files in the project root -- to see what this is even about. It's not an ideal target for your "Learn More" cta.
Either way, this really needs screenshots or some sort of visual demo to make it clear what value this adds and what usecases it fits, and all of that should be prioritized over the weird open source lip service
Thanks for your feedback.
We just launched the website and are moving fast to incorporate some of these suggestions to make the docs experience better.
If you asked me, I would advise as strongly as possible that you stop using the term "legos" for a class of component.
1. We all know what the owners of the trademark will do when they find it (justifiably, perhaps)
2. The plural of Lego is Lego - legos makes me wince every time I read it
Just call them blocks?
As for what this does... kind of an interesting idea, but I feel like the overlapping set of "people who need to do this sort of operation" and "people who want to build these in a UI rather than write a script" is pretty small.
We just launched the website and are moving fast to incorporate some of these suggestions to make the experience better.
We have tried to solve the problems with stock Jupyter for use as a production ops tool, given that its a fully capable programming environment (given the right connectors).
An AI powered noetbook? Great! Does it also use the blockchain? I need blockchain too. Also serverless internet of things devices to devops the synergy of my team.
I'm sorry but do you really expect engineers to create workflows on the graphical interface by clicking a button, choose from options, choose conditions and iterators ?
Your target audience - SRE Teams are engineers who would give up on using this in five minutes. They can accomplish the same thing using ansible, etc which they can configure using a text editor, mix with real programming languages where needed, store in version control and run using both a terminal and a GUI if needed.
18 comments
[ 2.7 ms ] story [ 57.0 ms ] threadThe concept is interesting. In our experience with regular and top teams trying to do notebooks for runbooks.. there are a lot of gaps around the Jupyter UI specifically and the concept in general. It's a fascinating problem to work on.
We just launched the website and are moving fast to incorporate some of these suggestions to make the docs experience better.
We have tried to solve the problems with stock Jupyter. Would love your product feedback as well!
https://github.com/unskript/Awesome-CloudOps-Automation/blob...
(setting aside the lack of try:finally: to close those cursors or why one needs a commit for a SELECT statement)
The GH repo is somewhat better, but you have to figure that some (most?) people aren't going to bother to scroll below the fold -- which is just a listing of folders/files in the project root -- to see what this is even about. It's not an ideal target for your "Learn More" cta.
Either way, this really needs screenshots or some sort of visual demo to make it clear what value this adds and what usecases it fits, and all of that should be prioritized over the weird open source lip service
1. We all know what the owners of the trademark will do when they find it (justifiably, perhaps)
2. The plural of Lego is Lego - legos makes me wince every time I read it
Just call them blocks?
As for what this does... kind of an interesting idea, but I feel like the overlapping set of "people who need to do this sort of operation" and "people who want to build these in a UI rather than write a script" is pretty small.
We just launched the website and are moving fast to incorporate some of these suggestions to make the experience better.
We have tried to solve the problems with stock Jupyter for use as a production ops tool, given that its a fully capable programming environment (given the right connectors).
Would love your product feedback as well!
Your target audience - SRE Teams are engineers who would give up on using this in five minutes. They can accomplish the same thing using ansible, etc which they can configure using a text editor, mix with real programming languages where needed, store in version control and run using both a terminal and a GUI if needed.
Docs for anyone else who can't figure out what this actually does from the homepage. https://docs.unskript.com/unskript-product-documentation/gui...
Also, where does "AI" come in ? Also who uses jupyter notebooks to run production code.