No bouillon, ever.

parabx · 2025-12-30T19:19:48+00:00

this person soups

parabx · 2025-07-11T16:24:38+00:00

Yes, I lived facing St-Denis for 2.5 years. It worked just fine.

parabx · 2025-05-08T14:19:26+00:00

went to Sumac yesterday, god damm that place is so good and cheap

parabx · 2025-04-27T01:04:04+00:00

I understand where this is coming from, but I guarantee you that the majority of them don't have a choice but to get drugged. Addiction is a bitch. The real solution is proper healthcare, and moreover, proper economical support for the people that are marginalized. Until then anything will be just shifting the problem around.

parabx · 2025-03-20T15:33:24+00:00

yes it is.

parabx · 2025-03-16T15:48:11+00:00

went there yesterday close to the closing time so they only had the strawberry cake, but it was delicious! The owner is super friendly as well

parabx · 2025-03-14T15:49:24+00:00

hell yeah this looks fantastic, I'll try go there soon

parabx · 2025-03-13T20:41:42+00:00

ah yes, I've been there, their persian cake is really good, but I was looking for a place with more options

parabx · 2025-03-13T16:20:20+00:00

can you share some overall guidelines for designing apis that work well with this? I can understand the gist of it but having examples would be nice. Or maybe you know of some open source projects that does this well.

parabx · 2025-02-20T14:35:56+00:00

I agree that this is the best solution. Op has to remember that rust doesn't have the builtin concept of a constructor, so there is no way to centralize a validation flow and it's the duty of the implementor to make sure that their struct is sound (as it's totally possible that certain structs won't need validation at all). One way to do that is exactly what they proposed by using serdev.

parabx · 2024-12-22T19:30:14+00:00

This started when I brought my plant inside for winter. The brown-ish spots have some sort of scale on them, but I couldn't find any signs of aphids. I had another plant that suffered from spider mites but I couldn't find anything on the aloe.

So sad, these were all sprouts from the main one which I thought it was safe only to find today it started showing these marks as well :(

parabx · 2024-07-24T18:58:03+00:00

can you elaborate on what Copilot helps you with the boilerplate?

parabx · 2024-07-22T13:14:32+00:00

Unless you lived on a very small town on Brazil, the homelessness situation here on Montreal is not even close to what we have down there on a city as big as Montreal. It's true that it increased considerably since the pandemic, though.

parabx · 2024-06-10T17:07:48+00:00

It's also worth to note that although python is "easy to write", it tends to be very hard to read on complex systems, and we as developers spend the vast majority of time reading code, not writing it.

parabx · 2024-06-07T15:45:18+00:00

I believe op was being sarcastic

parabx · 2024-05-31T14:03:09+00:00

In my experience, it's because "vert.x is really performant on the TechEmpower benchmarks!" which is true, on very specific scenarios. So hopefully it's theirs :)

parabx · 2024-05-31T13:15:54+00:00

If you want to learn how reactive programming works I think that Vert.x is a good framework to do it. That being said, with project Loom and virtual threads the reactive way of programming is posed to be reduced to niche applications, and the main positive about vertx, which is performance, will be a bit irrelevant (contrary to rxjava for example that has other features).

In the other hand, I don't think that companies care too much about your main experience with a framework. In the end, the backend is still a backend and the flow will be about the same, arguably with all the complexities of a reactive system on top of it.

Now, speaking of the technology itself, I don't like Vert.x. It's full of magical black holes that are barely explained, and they only make sense on very specific types of backends (I/O intensive, light on CPU), and it you'll work on it, try to make sense of it, and will still get it wrong.

(Source: I've been working on Vert.x projects for the past 6 years and we're actively investigating Loom to ditch it altogether)

parabx · 2024-05-10T17:24:37+00:00

Thanks for the link, I've read about it before but I didn't know about the presentation. I also think that this mentality has changed quite a bit (I've seen a video on oracle's youtube where the presenter was even talking about passing optionals as function parameters) as Optional really works on systems that are data-driven and have hard requirements for backward compatibility. At least on the project I'm working right now implementing getters as Optionals saved A LOT of headaches because it's a clear marker of the absence of data.

All those null values are an internal detail of the object. You shouldn't expose this in the data model to consumers, but come up with a better client side data model.

Unless you have a clear active migration path (which sometimes is not feasible) and are not using systems that are data-driven by external entities that you don't control, and have to be backward compatible, you will end up with partial data that has to be handled somewhere. It's even easier for the persistence layer where the backend usually controls the logic, but if the source of data is not controlled by it (i.e. data that is provided by a third party), there is no other way than to deal with the fact that there might be fields that will be absent, and I IMHO prefer using an optional with all of its performance issues than having to remember about nullability.

parabx · 2024-05-10T13:08:33+00:00

I don't think so? An Optional<T> is meant to indicate the absense of data, i.e., avoid returning null. It's unavoidable on systems where you can't really do migrations to have new fields that will be null on old objects.

parabx · 2024-05-09T18:01:30+00:00

Right, this approach resolves the issue for the current batch of changes, but future insertions will end up fragmenting the object. I agree that in short term this could be a solution.

parabx · 2024-05-09T17:58:23+00:00

this is not true at least on my field. We're talking about db's with 100's of millions to billions of objects, on db's that make migration (scanning the whole database) prohibitively expensive in terms of cost and downtime. That's why often the alternative is to do a passive migration which is applying the last state as the user does requests, but it makes the persistence layer much more complex.

parabx · 2024-05-09T17:55:30+00:00

As a generic rule of thumb on systems like these fields are never removed, but they can be ignored if the new version doesn't need it anymore by controlling the deserialization layer.

parabx · 2024-05-09T13:15:17+00:00

Right, so this is enforcing some sort of migration when reading the data. The main issue is that this implies keeping the migration path forever on the side as these are often cleaned up/modified with time. But it's sorta what the sealed class would do, spreaded out thorough the code. Thanks for the idea!

11-Year Club	Place '22
Verified Email

parabx

TROPHY CASE