sourcegraph

_journals/2024-06-24_2231.md

@@ -0,0 +1,9 @@
+---
+title: June 24th, 2024
+date: 2024-06-24, 22:31:42 -07:00
+section: journal
+link: https://sourcegraph.com/blog/the-death-of-the-junior-developer
+tags:
+  - AI
+---
+[[The Death of the Junior Developer]] by [[Steve Yegge]] "It's a bad year to be a junior anything…within a few years, the norm for source code will be that it is written and modified by LLMs via prompting"

_notes/CHOP.md

@@ -0,0 +1,7 @@
+---
+title: CHat Oriented Programming
+tags:
+  - acronym
+  - AI
+---
+CHat Oriented Programming -- [[Steve Yegge]]'s name for using LLM's to code. This effectively replaces IDEs and "completion" oriented programming as many IDE's are helpful with.

_notes/Cody.md

@@ -0,0 +1,9 @@
+---
+link: https://sourcegraph.com/cody
+tags:
+  - app
+  - AI
+---
+Cody is an AI coding assistant that uses advanced search and codebase context to help you understand, write, and fix code faster.
+
+Built by [[Sourcegraph]]

_notes/Public Handbook.md

@@ -0,0 +1 @@
+Many organizations have public handbooks. This is a page to collect backlinks to them.

_notes/Sourcegraph.md

@@ -0,0 +1,23 @@
+---
+link: https://sourcegraph.com/
+tags:
+  - organization
+  - allremote
+---
+Sourcegraph is a code intelligence platform that allows developers to rapidly search, write, and understand code by bringing insights from their entire codebase right into their editor. We help developers and companies with billions of lines of code create the software you use every day.
+
+Building [[Cody]], which is being evolved into [[CHOP]]
+
+Sourcegraph [[Public Handbook]]: <https://sourcegraph.notion.site/d7614e3e9dc04c09ac2d42d57f1816e6>
+
+An [[All Remote]] company, which means:
+
+>- We work [asynchronously](https://www.notion.so/communication/asynchronous-communication.md) across time zones and continents.
+    - You choose when you want to work. (Most people work the normal working hours for their time zone.)
+    - You don't need to ask permission or tell anyone if you need to step out.
+    - We try to limit the number of synchronous meetings, but there are some company and team meetings that you need to attend which might be outside of your normal working hours. We do our best to optimize meeting times for all involved participants.
+> - All teammates are encouraged to work remotely. Sourcegraph provides a budget for home offices or office spaces to teammates as needed.
+> - We use our business office address in San Francisco to provide a mailing address, for corporate filings, and on-site workplaces as legally required.
+
+[Sourcegraph Public Handbook](https://sourcegraph.notion.site/All-remote-guidelines-4d1270d806294bf4ae6db7ab02911957)
+

_notes/Steve Yegge.md

@@ -0,0 +1,13 @@
+---
+tags:
+  - person
+  - developer
+wikipedia: https://en.wikipedia.org/wiki/Steve_Yegge
+---
+Famous for many excellent blog posts on programming and culture at large tech companies such as Google and Amazon.
+
+* [Steve Yegge on Medium](https://steve-yegge.medium.com/)
+* [Stevey's Blog Rants](https://steve-yegge.blogspot.com/)
+* [Stevey's Drunken Blog Rants](https://sites.google.com/site/steveyegge2/blog-rants)
+
+Working at [[Sourcegraph]] building [[Cody]], an AI coding assistant

_notes/The Death of the Junior Developer.md

@@ -0,0 +1,34 @@
+---
+link: https://sourcegraph.com/blog/the-death-of-the-junior-developer
+tags:
+  - article
+  - AI
+author:
+  - Steve Yegge
+published: 2024-06-24
+---
+> a lot of people picked a bad year to be a junior developer. A whole lot of people. I wouldn't want to be just getting started in the industry today.
+> 
+> Not just the computer industry. Any industry. It's a bad year to be a junior anything.
+
+First example is of a law firm:
+
+> Increasingly, they need only senior associates, who (a) describe the tasks to be done; i.e., create the prompts, and (b) review the resulting work for accuracy and correctness. The high-end LLMs do so well with tasks normally fielded by junior associate lawyers, that there isn't much room left for the real junior associates on payroll.
+
+Writing and editorial jobs:
+
+> Market forces are nudging everyone towards having senior writers who are also good prompt engineers: An arrangement that meets all of their needs faster and cheaper than hiring junior humans.
+
+> (Gene) estimates using an LLM as a writing tool gets him there 2-3x faster now, helping him meet his personal requirements and quality bar.
+
+On to programming:
+
+> Since then I've found several other super amazing colleagues who have also adopted this coding strategy to accelerate themselves. And frankly it has been a bit of a relief to hear confirmation coming from so many great people that chat-first programming is indeed a New Thing.
+
+> Chat-based programming, which I will preemptively label **Ch**at **O**riented **P**rogramming ([[CHOP]]) or just "chop", because I suspect I'll be to be saying it a lot, is a brand-spanking new phenomenon. Like, seriously, just over a month old. I first noticed it when GPT-4o came out, which was mid-May.
+
+> <mark>Programming this way is arguably on its way to being an order of magnitude speedup from completions-based programming.</mark> A 10x improvement might sound like an exaggeration. But we just saw examples from legal practice, publishing, and data science in the same ballpark, with 5-30x speedups for certain kinds of tasks, and estimates of at least 2-3x overall boost to productivity.
+
+> I wrote this post a week ago and have been thinking hard about whether I believe the premise, which is that within a few years, the norm for source code will be that it is written and modified by LLMs via prompting. For all practical purposes, all source code will be written this way, with exceptions becoming ever rarer.
+>
+> Not only do I believe it, I could even see it happening in 12-18 months at the current rate of LLM progress.