Being a developer, I don't care if someone else uses my code. Code is like a brick. By itself it has little value, the real value lies on how it is used.
If I find an optimal way to do something, my only wish is to make it available to as much people as possible. For those who comes after.
It is a member since 2004, adopted the euro as its official currency since 2008.
But it is in a rather complicated situation since half of its territory is occupied by Türkiye (Turkey).
Drones were launched toward an EU nation (Cyprus). As an ally and one of the main EU military powers, France couldn't just turn a blind eye.
They don't make money on the hardware, but on the games sold.
Selling unlocked console would put them at risk of getting cannibalized by Steam.
Probably, but I won't touch that shit unless I have no way doing otherwise.
Edit : As an example, I got an "add or update" stored procedure that start line 5, and ends line... 226.
Yeah, you can do pagination, but you need two request : one to select everything, the second to only return the results between id x and id y. Needless to say, the performances are far from ideal.
But in recent version you do skip and take x, which is far easier to write. But my codebase date back to the 2000's, and it uses the old ways.
As an example, an SQL request to filter on an handful of parameters, and paginate, easily amount to 40-50 lines of SQL. And that's the easy ones, because some request uses multiple view, in which case I wouldn't be surprised to find a request doing more than 100 lines of SQL, maybe without even factoring the view in.
I work with a client using an Oracle DB. You have to do multiple request to even do something basic as pagination 😂.
They improved it over the years, but given the choice, I'd advice for anything else than Oracle. I'd even prefer MS Sql, which, given I'm pretty anti-MS, is a miracle.
To rethink something, it would require to think first.
Because heat diffuse at a limited rate. More heat won't magically make it faster.
Increasing the heat will continue cooking an already heat soaked layer, unable to radiate that heat to the inner layer fast enough.
At best you'll get an overcooked exterior, at worst a carbonized one. In both case, the inner layer will be barely warm, and raw, of course.
There really is an xkcd for everything 😂
Sound more like you learned the hard way what "abusing the system" mean.










That's not how LLMs work either.
An LLM had no knowledge, but has the statically probability of a token to follow another token, and given an overall context it create the statically most likely text.
To calculate such probability as accurently as possible you need as much examples as possible, to determine how often word A follow word B. Thus the immense datasets required.
Luckily for us programmers, computer programs are inherently statically similar, which makes LLMs quite good at it.
Now, the programs it create aren't perfect, but it allows to write long, boring code fast, and even explain it if you require it to. This way I've learned a lot of new things that I wouldn't have unless I had the time and energy to screw around with my programs (which I wished I had, but don't), or looked around Open Source programs source code, which would take years to an average human.
Now there is the problem of the ethic use of AI, which is a whole other aspect. I use only local models, which I run on my own hardware (usually using Ollama, but I'm looking into NPU enabled alternatives).