Need to process data in batches?
Forget the complex math. Use .Chunk() in LINQ:
1) Takes an IEnumerable
2) Splits it into fixed-size arrays
3) No external libraries needed
| GitHub | https://github.com/cedx |
| https://linkedin.com/in/cedxbelin |
Need to process data in batches?
Forget the complex math. Use .Chunk() in LINQ:
1) Takes an IEnumerable
2) Splits it into fixed-size arrays
3) No external libraries needed
Realising that most of my fears about LLM-based AI services can be summed up thus:
The mega corps want to create Knowledge-as-a-Service.
They made your TV a subscription.
They made your music a subscription.
They made your books a subscription.
They made your car a subscription.
Now they want you to become dependent on them for knowledge for a monthly fee.
It's a shame Safari and iOS don't support the "is" attribute. It's so useful for turning a table row (i.e. "<tr>") into a web component.
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/is
What a strange time. I just read this sentence in an article about an HTTP client:
"Lightweight : Just 157~ KB in size"
Sorry but 157 KB is NOT lightweight. Especially for an alternative to "fetch".
FrankenPHP elePHPants are now available worldwide 🧟♂️ Get yours before they sell out! Expect your order to ship in March.
Marre des traductions par IA de Microsoft : c'est une catastrophe.
Je ne compte plus le nombre de fois où un libellé n'a plus aucun sens dans leurs logiciels ou leur documentation.
Exemple parmi tant d'autres... (J'ai en un rayon !)
Chrome : "Désactiver les traces de pile asynchrones"
(OK, je comprends ce que ça veut dire)
Edge : "Désactiver les arborescences des appels de procédure"
(Plus aucun rapport avec le code asynchrone !!!)
Relative dates are terrible: they don't help anyone determine the exact day and time of an operation.
Please stop using relative dates.
LLMs are so bad for coding.
Copilot: `NullabilityInfoContext` is thread‑safe. [...] The internal cache is thread‑safe.
The .NET documentation: This type is not thread safe. [...] methods can't be called concurrently from multiple threads, as they use a non-concurrent cache internally.
(My code confirms that `NullabilityInfoContext` is NOT thread‑safe)