OpenDevin – open-source implementation of devin

• OpenDevin

  8 23,616 9.7 Python

  🐚 OpenDevin: Code Less, Make More

  

There are two parts to “writing a Devin”.

1) a pretty user interface, a backend service layer, all the normal things you’d need for a desktop app or saas.

2) a backend that can actually do work.

I’m going to go out a limb here and say, building an MVP of the UI is a waste of your time.

…because, unless you know how to build the backend (ie. part 2), you actually, have no idea what you need to build for part one.

You can copy of the UI from the Devin videos.

You can build your own langchain framework.

You can fine tune an open model on GitHub issues.

…but just like having building a gpt4 is harder than just “add more params”, building something that works like Devin appears to work requires a reasonably sharp “step up” in capability between what literally everyone has been doing with gpt4 until now, and being able to turn that into a useful framework for solving actual engineering tasks.

So… don’t hold your breath. If you see someone building a UI (like this https://github.com/OpenDevin/OpenDevin/tree/main/frontend, https://github.com/stitionai/devika/tree/main/ui; just read the commitmlog, it’s basically just ui) it means they’re doing the easy work (part 1) because they don’t know how to do the hard part (part 2).

…so, interesting, but this doesn’t smell like a really serious effort.

• devika

  9 16,812 9.2 Python

  Devika is an Agentic AI Software Engineer that can understand high-level human instructions, break them down into steps, research relevant information, and write code to achieve the given objective. Devika aims to be a competitive open-source alternative to Devin by Cognition AI.

  

There are two parts to “writing a Devin”.

1) a pretty user interface, a backend service layer, all the normal things you’d need for a desktop app or saas.

2) a backend that can actually do work.

I’m going to go out a limb here and say, building an MVP of the UI is a waste of your time.

…because, unless you know how to build the backend (ie. part 2), you actually, have no idea what you need to build for part one.

You can copy of the UI from the Devin videos.

You can build your own langchain framework.

You can fine tune an open model on GitHub issues.

…but just like having building a gpt4 is harder than just “add more params”, building something that works like Devin appears to work requires a reasonably sharp “step up” in capability between what literally everyone has been doing with gpt4 until now, and being able to turn that into a useful framework for solving actual engineering tasks.

So… don’t hold your breath. If you see someone building a UI (like this https://github.com/OpenDevin/OpenDevin/tree/main/frontend, https://github.com/stitionai/devika/tree/main/ui; just read the commitmlog, it’s basically just ui) it means they’re doing the easy work (part 1) because they don’t know how to do the hard part (part 2).

…so, interesting, but this doesn’t smell like a really serious effort.

• SurveyJS

  surveyjs.io featured

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

Suggest a related project