xbfjvusb6

Solved for most the image text I see on social.

I find OOP fine but it's not something you can just let rot. You need to be ok with redefining classes and refactoring things around the new boundary lines regularly as requirements change.

This requires a testing suite that gives you confidence to make these sweeping changes quickly. Without it, it's not a fun way to work.

Also, you don't have to go all in on oop. I like to use procedural most of the time only defing objects for things I find more easy to reason about as objects.

For example, I'll write the command line interface in procedural that looks a lot like a complicated bash script and then define objects that do the work. This often results in objects not really changing much because they're not defined until later in development when their needs are well known. The place that changes is usually feature switches, command toggles, output formats, and the like. All that can be objects if you want but for the most part a function or two goes a long way and results in easier to change code.

OCR is a solved problem. It's like one call to tesseract and you're done.

The fact they haven't done this just shows how inept their employees are.

I am. Only issue is that it isn't the worst place I've worked and it's hard to find better than what I have where I'm at.

Search the CPU name on AliExpress.

It's a black box but the CEO has communicated dev performance is dependent on amount of code shipped. I suspect they're using sloc or pr counts behind the scenes.

I've done everything you're recommending. CEO doesn't care about any of that. Only metric they care about is money made and code shipped.

They do say they care about communication and apparently track it but I havnt seen it reflected in comp reviews so my conclusion is code shipped is the only metric.

We have sloc and pr tracker stat pages so Im making a guess they are using sloc.

This. I can tell HR, my lead and skip about how good my communication, soft skills and team work have been this year but come comp review they don't give a crapola about any of that. All they look at is how many sloc I've shipped.

Stupid high dxy makes international markets tighten the purse strings. Whowouldathunkit.

> I disagree

This is an argument. A bad one, but an argument none the less.

Copilot seems to be copying code snippets from the internet wholesale. It's not using AI to generate snippets which would possibly be ok.

Copyright doesn't care about the size of the abuse or the size of the works involved.

Microsoft is creating these copies and even facilitates their redistribution on GitHub.

I know legally it's more likely the users of copilot that are at risk here but we said the same thing about torrenting.

Look at Napster, LimeWire or the pirate bay. The outcomes Microsoft deserves here is pretty cut and dry.

You're right. It's a few orders of magnitude worse than that.

It's not just one snippet, it's thousands of them, every day being slurped up and copied across code bases everywhere license free.

If the pirate bay can get jail time for facilitating mass copyright infringement, maybe Microsoft needs a little jail time too.

It's been said in this thread already:

Either licenses matter or they don't. Pick one.

My license isn't "you can take a bit but not the whole bit".