Live data from Hacker News

GitHub Copilot is generally available

github.blog

651–660 of 796 posts

Re: GitHub Copilot is generally available

#651

Earlier quoted context omitted.

I wholeheartedly agree with your analysis, but feel like it’s ignoring the elephant in the room: writing code is not the bottleneck in need of optimization. Conceiving the solution is. Any time “saved” through Copilot and it’s ilk is immediately nullified by having to check it’s correctness. From there, the problem is worsened by the Frankensteinesque stitching together of disparate parts that you describe. I can’t i…

Right on the money. What I want is a copilot that finds errors ala spellcheck-esque. Did I miss an early return? For example in the code below def some_worker if disabled_via_feature_flag logger.info("skipping some_worker") some_potentially_hazardous_method_call() Right after the logger call I missed a return. A copilot could easily catch this. Invert the relationship. I don't need some boilerplate generator, I need…

Business is trying to commoditize software development, because it's slow and expensive. All they have ever wanted, is to get their automation with the blanks filled in correctly, more or less immediately.

No-code, visual programming, gherkin, even SQL are all prior attempts at reducing the expense of software development, and of sidestepping the expensive, excuse laden gatekeepers that are software developers.

Copilot is an MVP of a technology that will probably eventually succeed in doing this, and my guess is, it's going to make CRUD slinging obsolete very soon.

Copilot is not backwards, it's just that it's a convenience tool for the execution of business, not for software developers.

When version 2 of the tool can both code and error check, hopefully you're already promoted to architect by then...

Re: GitHub Copilot is generally available

#653

Earlier quoted context omitted.

Right on the money. What I want is a copilot that finds errors ala spellcheck-esque. Did I miss an early return? For example in the code below def some_worker if disabled_via_feature_flag logger.info("skipping some_worker") some_potentially_hazardous_method_call() Right after the logger call I missed a return. A copilot could easily catch this. Invert the relationship. I don't need some boilerplate generator, I need…

Perhaps curly braces are useful after all.

Not that OP's problem is curly braces per se (they would make the error more obvious, but they wouldn't help with a missing return call), but since we're taling about them...

The insistence of a lot of smart people on using whitespace for logic purposes is THE most baffling thing in the IT space. And I mean that.

Why use some, oh I dont know, CHARACTER, to write down what you mean, why not instead use a NON CHARACTER. Now that's a great idea!

Let's use non characters, so a mix of tabs and spaces (which editors can implement AND display in a number of different ways, even depending on individual configuration!) fucks up shit. Using whitespace is also great because copy/paste is now an error-prone exercise in frustration, which is definitely what we want! Oh and also this will make sure that the peasants are not using our beautiful language IN NAUGHTY WAYS, e.g. you can't really write a deeply nested logic in a single function if it becomes a complete abomination of a mess just after like two or three indentations.

No, but seriously, Python's syntax in regards to whitespace, or any language that uses whitespace for control structures, is hot garbage. I understand that there are preferences, coding standard, etc. and I can tolerate a lot, but this, this is the one hill I'm willing to die on.

Re: GitHub Copilot is generally available

#654
I'm just happy that Microsoft is finally charging directly for a developer product!

When they keep giving out freebies (VSCode, npm etc.), I never know which direction the product is going to evolve (e.g. unnecessarily tight integration with Azure).

With this, there's at least direct alignment between end user & the product.

Re: GitHub Copilot is generally available

#655
I've been using the beta since last year and I love it. I think most of the people complaining about it either haven't used it, or are judging it on its most verbose guesses. That's not what I use it for mostly. For me, it's just a really, really good autocomplete. It's best for things with common patterns and APIs. But hey, they're common so I write them a lot. Boring stuff like creating a Response object, adding the right headers and response code. And look, it's worked out that I need a case for a 404 next, and has suggested the code for that to, and a 500 in my catch block. Sure, that's not much typing or cognitive load, but added up over many, many times then it's easily worth it.

And no, I'm not a beginner. I'm a principal with over 20 years experience. I don't really use it for the Stack Overflow-type stuff, but even as an autocomplete it's worth the money. As it happens I'm apparently eligible for free access as an open source maintainer, but I'd pay $100/year in a heartbeat for it. I'd pay for Intellisense if that was $100 too.

Re: GitHub Copilot is generally available

#656

Earlier quoted context omitted.

I really don't like it. I find I spend my time reviewing Copilot suggestions (which are mostly wrong) rather than thinking about code and actually doing the work.

I turned off auto-suggest and that made a huge difference. Now I'll use it when I know I'm doing something repetitive that it'll get easily, or if I'm not 100% sure what I want to do and I'm curious what it suggests. This way I get the help without having it interrupt my thoughts with its suggestions.

How do you do that?

Re: GitHub Copilot is generally available

#657
post #629

Earlier quoted context omitted.

It's a lot more complicated to crawl code somewhere in the web than to crawl github. They could even change github so it benefits their code crawling.

That would be a problem if Microsoft didn’t also have their own Bing

Oh, is Bing still a thing? Honest question, haven't heard it mentioned for years. Went from Altavista to Google (I believe, it's a long time ago...) and now to DDG a couple of years ago. Never considered Bing directly although I believe DDG results come or came from Bing.

Re: GitHub Copilot is generally available

#658
post #195

I've been using Copilot non-stop on every hobby project I have ever since they've let me in (2021/07/13) and I am honestly flabbergasted they think it's worth 10$/mo. My experience using it till this day is the following: - It's an amazing all-rounder autocomplete for most boilerplate code. Generally anything that someone who's spent 5 minutes reading the code can do, Copilot can do just as well. - It's terrible if y…

  it thinks it knows how and then produce good looking code at a glance but with wrong logic.
This is so accurate. I still like copilot and I might even pay for it, but I will never trust the logic. It always wrong in a way that _almost_ looks right.

Re: GitHub Copilot is generally available

#659
I've been using copilot for 6 months and it has been an exceptional tool worth the money even if not always generating correct code.

What i'm concerned with is that i think it can interrupt the flow of thoughts while programming since you have to review the generated code, but that is the price to pay to use such a formidable tool

Re: GitHub Copilot is generally available

#660

Earlier quoted context omitted.

I wholeheartedly agree with your analysis, but feel like it’s ignoring the elephant in the room: writing code is not the bottleneck in need of optimization. Conceiving the solution is. Any time “saved” through Copilot and it’s ilk is immediately nullified by having to check it’s correctness. From there, the problem is worsened by the Frankensteinesque stitching together of disparate parts that you describe. I can’t i…

Right on the money. What I want is a copilot that finds errors ala spellcheck-esque. Did I miss an early return? For example in the code below def some_worker if disabled_via_feature_flag logger.info("skipping some_worker") some_potentially_hazardous_method_call() Right after the logger call I missed a return. A copilot could easily catch this. Invert the relationship. I don't need some boilerplate generator, I need…

You missed the `else` branch, not a `return`.
Post reply on HN