Skip to content

Update supporters.md #79

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Aug 21, 2025
Merged

Update supporters.md #79

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
eca4181
Update supporters.md
praveeno Aug 2, 2025
42cd931
Merge branch 'main' into patch-1
TyDunn Aug 5, 2025
d4c44ee
Merge branch 'main' into patch-1
TyDunn Aug 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

In the era of [Large Language Models (LLMs)](https://www.youtube.com/watch?v=zjkBMFhNj_g), software development is becoming increasingly automated by AI copilots. Many folks are forecasting that AI will replace developers in as little as a few years, while investors declare the arrival of superhuman AI software engineers. This worries some developers and annoys others.

Our motivation with `amplified.dev` is to instead 1) empower developers and 2) raise awareness of systemic issues we’ve seen in how engineering organizations are adopting, using, and evolving AI software development systems.
Our motivation with `amplified.dev` is to **(1) empower developers and (2) raise awareness of systemic issues** we’ve seen in how engineering organizations are adopting, using, and evolving AI software development systems.

Our hope is that, over time, we can find a shared vocabulary for discussing these problems. For now, we describe the [current state of the world](#where-we-are-today), [where we are heading](#where-we-are-heading), and [what amplified developers need to do at their organizations today](#amplified-developers):

Expand Down Expand Up @@ -178,7 +178,7 @@ You want to give LLMs as much relevant information as possible to get the best s

Already today you’ll want to deploy embeddings, a “chat” model, a remote configuration server, a shared index, and more, so you need permissions and integrations that enable you to index any codebase and reference it with context providers. There is also lots of data from across the software development lifecycle that you will want to pull in more and more over time (e.g. GitLab issues, Confluence docs, etc.).

Best practices from web apps and DevOps apply here too. Permissions and integrations can get messy quick, so having a good approach here will set you up to evolve much better.
Best practices from web apps and DevOps apply here too. Permissions and integrations can get messy quicky, so having a good approach here will set you up to evolve much better.

### 5. Adopt open-source interfaces

Expand Down
1 change: 1 addition & 0 deletions supporters.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,5 +69,6 @@
- [Irfan Raza](https://github.com/irfaan008)
- [Rob Goodridge](https://github.com/robe070)
- [Jurie Smit](https://github.com/justaghost)
- [Praveen Soni](https://github.com/praveeno)
- [Nathaniel Davis](https://github.com/ntedvs)
- [Lucas Roberts](https://github.com/rlucas7)