Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

We’re all building our own software factories. But, our coding and code review agents are missing a curated map of the software they’re working on: how repositories connect, what depends on what, and where a change can have an impact. That’s why we built Software Map in Qodo 🚀...

159,868 Aufrufe • vor 27 Tagen •via X (Twitter)

13 Kommentare

Profilbild von Itamar Friedman
Itamar Friedmanvor 27 Tagen

The software map is quite rich, and we are adding more curated data into it. Read more here:

Profilbild von Yoav Vainrich
Yoav Vainrichvor 27 Tagen

Like Graphify?

Profilbild von Itamar Friedman
Itamar Friedmanvor 27 Tagen

Related, but there are a few meaningful differences that make Qodo Software Map more fitting for the agentic-SDLC. Let's take the "Edge" for example- Graphify: a fact: X imports/calls Y Qodo: a contract: what couples X and Y, what breaks, why it matters It started that since we needed this representation to push Qodo review agents quality, and realized that giving access to coding agents makes their generated code become grounded to reality and improve quality to begin with

Profilbild von Bernardo Ferrari
Bernardo Ferrarivor 27 Tagen

Can I add another repo on top and take the diff out of them? Like when converting from cpp to Rust.

Profilbild von Itamar Friedman
Itamar Friedmanvor 27 Tagen

You are looking to transform/refactor an entire repo from cpp to Rust?

Profilbild von Bernardo Ferrari
Bernardo Ferrarivor 27 Tagen

I have done several times. I rewrote R language in rust and I'm finishing command&Conquer Generals

Profilbild von idan levin
idan levinvor 27 Tagen

So it’s essentially a dependency map for you code base? (very nicely visualized)

Profilbild von Itamar Friedman
Itamar Friedmanvor 27 Tagen

Dependency map, yes, but every edge carries the contract: including for example the files that couple two repos, and what breaks if you touch them. Qodo re-analyzes on merge, so it doesn't rot. Another major challenges we faced was to surface the soft dependencies.

Profilbild von idan levin
idan levinvor 27 Tagen

Got it tnx @vladikk you’ll like this

Profilbild von Ori Berkovitch
Ori Berkovitchvor 26 Tagen

Wonderful work @itamar_mar and team. Looking forward to give this to our coding agents... 😍 Self reflection like never before. Let them see their own internals?

Profilbild von Tomer Damti
Tomer Damtivor 27 Tagen

It’s look amazing 🤩

Profilbild von Ben Mo
Ben Movor 27 Tagen

shared database tables are a nasty one for this. two repos can be tightly coupled without either importing the other. glad you're digging into the soft dependencies too

Profilbild von Itamar Friedman
Itamar Friedmanvor 27 Tagen

Exactly. The soft dependencies is one of the hard nuts here. Also tracking changes reliable.

Ähnliche Videos

Today we’re introducing Base Code. It’s an early preview of how we think software will be built in the future. It’s a product that encapsulates everything we’ve learnt from: - How our users are building software. - How we’re building internally, scaling to hundreds of millions of dollars in revenue while keeping our engineering team very small and focused. Here are some of the principles behind it, which align with how we at Base44 think about the future of software engineering: Cloud: - Software will move past local desktop environments (where current tools are widely used) and move to the cloud. - Moving everything to the cloud is not easy. Setting up dev environments with databases, infra components, services, mock data, etc. is easier said than done. - Base Code first scans your code repo and sets up everything - every infra component (databases, Redis, etc.) - in the cloud. It runs nonstop until your preview environment is ready. - From an enterprise standpoint, it’s also the logical thing to do: a centralized, governed dev environment instead of handing out keys and secrets to all team members. - Once Base Code does that, EVERY team member can work in this environment. No more syncing local environments. Internally, this (cloud) is one of the main things that enabled us to move so fast. Collaboration: - Once everything is in the cloud, everybody can write software from anywhere (any browser, your phone, WhatsApp / iMessage coming soon). - You can easily see what everyone is working on, where they’re at, and how they’re prompting - and jump to their environment in one click. - We’ve built many great collaboration features from the ground up. Loops, automations, software factories: - A full, working cloud environment allows for many advanced capabilities we will unveil soon-think agents running in the browser and testing on every device and in any browser. - It also allows the use of automations to build software factories-e.g., agents reading support tickets, identifying bugs to fix or features to develop, implementing the changes, verifying them in the cloud, and potentially pushing them. And lastly, there’s a real advantage in being model agnostic. -------------- As always, we’re releasing it very early. It’s far from perfect-but we’re looking for early feedback so we can build it together with our great community and make this vision a reality. *We’re giving it away for free for 30 days*. Give Base Code a try. Connect any GitHub repo, get your live preview, and share it with your team. I’d love to hear what works and what doesn’t:

Maor Shlomo

1,996,804 Aufrufe • vor 14 Tagen