5 ms·

Hey! Thanks for the question. Our editor isn't a regular coding editor. You don't actually write code with e2b. You write technical specs and then collaborate

by mlejva 4y ago

Hey! Thanks for the question. Our editor isn't a regular coding editor. You don't actually write code with e2b. You write technical specs and then collaborate with an AI agent. Imagine it more like having a virtual developer at your disposal 24/7. It's built on a completely new paradigms enabled by LLMs. This enables to unlock a lot of new use cases and features but at the same time there's a lot that needs to be built.

walleeee 4y ago
I'm not sure I follow this answer. What are the entirely new paradigms? Writing is still the initial step. If text editing remains a core part of the workflow, why restrict the user's ability to edit code?
- b112 4y ago
  why restrict the user's ability to edit code? Because funky brackets are confusing.
mayank 4y ago
> You don't actually write code with e2b. You write technical specs and then collaborate with an AI agent. If I want to change 1 character of a generated source file, can I just go do that or will I have to figure out how to prompt the change in natural language?
- arthurcolle 4y ago
  I'm sure there would be a way to edit the artifacts... otherwise this would be a constant exercise in frustration!
  - mypalmike 4y ago
    So, not too different from typical real world coding tasks today.
  - RoyGBivCap 4y ago
    I feel like this would be like trying to edit a confluence page. It's in the frustration valley between WYSIWYG and just writing code. The worst of both worlds.
eikenberry 4y ago
Writing technical specs a fancy way to say coding. This reads to me like you're writing a new programming language tightly integrated with an IDE that targets a new AI based compiler.
- eterps 4y ago
  That's a brilliant and witty way to put it :D
- spyder 4y ago
  Hmm... Where is the new language in this? The specs is just human language and some JSON for defining structures. It's more so that the human language becoming a programming language with the help of AI.
  - xwdv 4y ago
    You’re right, it is just English language. And over time, people will discover some basic phrases and keywords they can use to get certain results from the AI, and find out what sentence structures work best for getting a desired outcome. These will become standard practices and get passed along to other prompt engineers. And eventually they will give the standard a name, so they don’t have to explain it every time. Maybe even version schemes, so humans can collaborate amongst themselves more effectively. And then some entrepreneurs will sell you courses and boot camps on how to speak to AI effectively. And jobs will start asking for applicants to have knowledge of this skill set, with years of experience.
    - namaria 4y ago
      >And over time, people will discover some basic phrases and keywords they can use to get certain results from the AI, and find out what sentence structures work best for getting a desired outcome. This just sounds like a language that is hard to learn, undocumented, and hard to debug
      - xwdv 4y ago
stinkbutt 4y ago
by technical specs you mean some kind of prompt mechanism, no?

by mlejva 4y ago

walleeee 4y ago

I'm not sure I follow this answer. What are the entirely new paradigms? Writing is still the initial step. If text editing remains a core part of the workflow, why restrict the user's ability to edit code?

b112 4y ago
why restrict the user's ability to edit code? Because funky brackets are confusing.

mayank 4y ago

> You don't actually write code with e2b. You write technical specs and then collaborate with an AI agent. If I want to change 1 character of a generated source file, can I just go do that or will I have to figure out how to prompt the change in natural language?

arthurcolle 4y ago
I'm sure there would be a way to edit the artifacts... otherwise this would be a constant exercise in frustration!
- mypalmike 4y ago
  So, not too different from typical real world coding tasks today.
- RoyGBivCap 4y ago
  I feel like this would be like trying to edit a confluence page. It's in the frustration valley between WYSIWYG and just writing code. The worst of both worlds.

eikenberry 4y ago

Writing technical specs a fancy way to say coding. This reads to me like you're writing a new programming language tightly integrated with an IDE that targets a new AI based compiler.

eterps 4y ago
That's a brilliant and witty way to put it :D
spyder 4y ago
Hmm... Where is the new language in this? The specs is just human language and some JSON for defining structures. It's more so that the human language becoming a programming language with the help of AI.
- xwdv 4y ago
  You’re right, it is just English language. And over time, people will discover some basic phrases and keywords they can use to get certain results from the AI, and find out what sentence structures work best for getting a desired outcome. These will become standard practices and get passed along to other prompt engineers. And eventually they will give the standard a name, so they don’t have to explain it every time. Maybe even version schemes, so humans can collaborate amongst themselves more effectively. And then some entrepreneurs will sell you courses and boot camps on how to speak to AI effectively. And jobs will start asking for applicants to have knowledge of this skill set, with years of experience.
  - namaria 4y ago
    >And over time, people will discover some basic phrases and keywords they can use to get certain results from the AI, and find out what sentence structures work best for getting a desired outcome. This just sounds like a language that is hard to learn, undocumented, and hard to debug
    - xwdv 4y ago

stinkbutt 4y ago

by technical specs you mean some kind of prompt mechanism, no?