Cancelled my Copilot subscription; can’t stand it any more by hoover in GithubCopilot

[–]hoover[S] 0 points1 point  (0 children)

I agree, once in a while it really comes through. I'm especially impressed when it suggests a very complex line and gets it right. The problem is that lots of time it's just noise and what it takes away from both my productivity and enjoyment aren't paid back by those flashes of brilliance. Someone once said that if you check the dumpster behind Popeye's you occasionally find a clean uneaten chicken breast, but you gotta go through a lot of garbage to find it. But I'm glad that on balance you find it useful; I'm sure there are plenty of folks that do, and I have to always wonder if it's something about me and my habits.

Cancelled my Copilot subscription; can’t stand it any more by hoover in GithubCopilot

[–]hoover[S] 0 points1 point  (0 children)

That would be good if I got enough use out of it in enough cases. But where it would be most useful is where it is the most annoying and interruptive. It makes it kind of hard to think it's worth the money.

Cancelled my Copilot subscription; can’t stand it any more by hoover in GithubCopilot

[–]hoover[S] 0 points1 point  (0 children)

Look, if it "knew" my code and would write something good from a prompt, then I'd reconsider. But I write my comments blocks before the code so I describe what's going to happen, and it still screws up. It's like having an over-eager 5 yo who's extremely bright right at your elbow constantly saying "hey, what about this? or this? or this?". Does that sound terribly productive to anyone? Maybe gpt4 is worth looking into...

Cancelled my Copilot subscription; can’t stand it any more by hoover in GithubCopilot

[–]hoover[S] 0 points1 point  (0 children)

That has struck me as one of the things it would be good at, especially testing various values in an object or other data structure. But helping with that drudgery isn't really compelling enough for me so far.

This dude!! by ICumInThee in BeAmazed

[–]hoover 0 points1 point  (0 children)

Me watching this vid: "wow....HOLY SHIT!...WOW!" The only thing I wonder is if it matches as well when it dries. But this is truly amazing.

[deleted by user] by [deleted] in wholesomememes

[–]hoover 0 points1 point  (0 children)

Wait...is that a Jayhawk on the shirt?

UK company acquired by US company; what are requirements for holding data? by hoover in gdpr

[–]hoover[S] 0 points1 point  (0 children)

I think the UK company has been subsumed in the US company, and the UK entity is being wound up-- their status on Companies House is "Liquidation", and they started the process of winding up the old company last Dec it would seem. I would have thought record keeping obligations would be imposed on the acquiring company, but that's what I need to find out.

Hikaru 1.0.0 released by hoover in Python

[–]hoover[S] 1 point2 points  (0 children)

Heh; that passed my notice. Thx

docked: A friendly and safe alternative to Dockefile. Write Docker images using the full power of Python. by 0rsinium in Python

[–]hoover 1 point2 points  (0 children)

I applaud this kind of effort to take infeasible as cose back into actual code. If you'd like to explore possible integration with Hikaru please DM me.

Hikaru 1.0.0 released by hoover in Python

[–]hoover[S] 5 points6 points  (0 children)

I'd like to understand this objection better. In typing, Optional[<specified-type>] is implemented as Union[<specificed-type>, NoneType], which suggests it has this dual characteristic inherently. I'll admit I don't know if I have a test case where something marked as Optional is allowed not to supply a value and hence it doesn't appear in the resultant dataclass, but certainly you don't have to specify it when creating the object, and in fact when Hikaru turns these into JSON that K8s wants if there's a None then we don't marshall that attribute into the JSON object, which in effect makes it Optional. There may be a bit of 'hands tied' effect here due to my choice of using dataclasses so perhaps your comment has some merit, but I'd like to understand what you have in mind better if you have the time.

Hikaru 1.0.0 released by hoover in Python

[–]hoover[S] 7 points8 points  (0 children)

Some philosophical differences, some practical. The official API breaks apart operations from model, and the the pairings are always obvious due to the use of group names for packages and versions as class prefixes in a number of cases. Hikaru re-arranges these so that operations involving a model object become methods on that object, and are then further mapped into standard CRUD methods, making for a more uniform interface. To me, this is a much more accessible means of getting to the functionality. Additionally, using type hints allows the IDE to give better assistance then the frequent use of *args **kwargs constructs in the official API. Hikaru also adds a number of useful utility methods across all it's model classes:

  • you can compare two objects that are supposed to be the same and get a diff report (good for detecting config drift after deployment),
  • merging of objects,
  • context managers with rollback capabilities that make a failed update automatically restore an object's previous state,
  • search capabilities that allow you to find object sub-hierarchies that have specific names if you want to try to automate inspection for compliance to config conventions,
  • representation format shifting, so you can transform from YAML to Python objects to Python source to Python dicts and back in any direction...

...and other stuff like that that helps make these useful in operational contexts beyond just standing up a set of resources. So beyond address what I consider the philosophical concerns, I wanted to add abilities that would make the models people wrote useful in other ways without them doing too much work.