Did GitHub Copilot increase my productivity?

Post by specialist » Mon, May 13, 2024, 7:03 PM UTC

marcus_holmes wrote: post #87

Years ago, over a decade ago now, I was a .Net developer. Microsoft introduced Entity Framework, their new way of handling data in .Net applications. Promises made, promises believed, we all used it. I was especially glad of Lazy Loading, where I didn't have to load data from the database into my memory structures; the system would do that automatically. I could write my code as if all my memory structures were popul…

Post by tracker1 » Mon, May 13, 2024, 7:28 PM UTC

rspeele wrote: post #241

marcus_holmes wrote: post #87

Years ago, over a decade ago now, I was a .Net developer. Microsoft introduced Entity Framework, their new way of handling data in .Net applications. Promises made, promises believed, we all used it. I was especially glad of Lazy Loading, where I didn't have to load data from the database into my memory structures; the system would do that automatically. I could write my code as if all my memory structures were popul…

Lazy loading was a mistake in EF. A lot of apps had awful performance due to lazy loading properties in a foreach loop creating N+1 queries to the database. It would be fine in dev with 50-100 rows and a localhost SQL and blow up in prod with 1000s of rows and a separate Azure SQL. Also if you relied on lazy loading properties after the DbContext had been disposed (after the using() block) you were out of luck. With…

Post by yawaramin » Mon, May 13, 2024, 7:41 PM UTC

simonw wrote: post #72

Loocid wrote: post #70

Earlier quoted context omitted.

They mean they have 20 years experience in programming, which helps them ask good questions.

Yeah, that's what I meant. With LLMs having deep domain knowledge in a field helps enormously in terms of prompting them as productively as possible.

Post by randomdata » Mon, May 13, 2024, 8:12 PM UTC

freedomben wrote: post #281

randomdata wrote: post #268

Earlier quoted context omitted.

Whatever you want. It's your life. Traditionally, though, SQL generation was known as query building. The query was executed via database engine or database driver, depending on the particulars. ORM, as the name originally implied, was the step that converted the relations into structured objects (and vice versa). So, yes, technically if you maintain your data as tuples end to end you are not utilizing ORM. Lastly, t…

I agree with you, but I do think there's a little fuzziness between full-blown ORM and a tuple-populating query builder in some cases. For example Ecto, which can have understanding of the table schema and populate a struct with the data. It's just a struct though, not an object. There's no functions or methods on it, it's basically just a tuple with a little more organization.

Post by threecheese » Mon, May 13, 2024, 9:51 PM UTC

dathinab wrote: post #227

theshrike79 wrote: post #114

Earlier quoted context omitted.

With VSCode at least you can say @workspace to Copilot and it'll take it into account. No idea if it feeds all of the code to the LLM or just parts, but it's pretty good at interpreting what the code does

It guaranteed can't have all of your code in the LLM context, or even all of your file (in case of longer, through not even quite long files). Through it could do stuff like go through your repository(ies) and generate embedding for sections of it and then have a vector database + retrieval argumented generation (RAG) system.