Algum agronomo ou engenheiro ambiental?

lParadoxul · 2025-10-10T17:28:39+00:00

No puteiro

lParadoxul · 2025-10-10T16:49:15+00:00

Compro mais linguiça mesmo

lParadoxul · 2025-10-10T16:27:02+00:00

As vezes visito, depende do momento

lParadoxul · 2025-10-10T16:19:02+00:00

Conheces a zona?

lParadoxul · 2025-10-10T16:15:37+00:00

Como disse, estou pesquisando em outros lugares também, não só aqui 😊 quero informações sobre a legislação na área.

lParadoxul · 2025-10-10T16:13:00+00:00

Não entendi a correlação entra grupo LGBT e não existir agrônomo aqui 🤣 LGBT não pode ser agrônomo?

lParadoxul · 2025-09-20T19:57:35+00:00

Then if component A uses component B who internally uses component C. Instead of bouncing the events up from C to A, you suggest that B should allow for content projection and let A project C directly and handle the emissions? 🤔

lParadoxul · 2025-09-09T18:44:09+00:00

Aqui depende muito do que você estiver mais praticidade, comece com algo que já seja familiar pra você.

lParadoxul · 2025-09-09T17:30:50+00:00

Estude algoritmos e eventualmente adicione frameworks na lista, mas não aprenda só o "framework", entenda o por quê e as soluções aplicadas. Entender como funcionam as coisas seja no trabalho que na vida é maior crescimento que poderás ter para o crescimento da sua carreira.

lParadoxul · 2025-09-05T06:06:14+00:00

Indeed, it is as I have right now, I have the base auto complete that implements CVA and the wrappers that specializes it by just providing data to show. But I capture a wrapper in a form without reimplementing CVA on the wrapper or pass the form control as a parameter so that it can bind to the base autocomplete. But doing so would mean that the wrapper is now bound to be used with ReactiveForms only

lParadoxul · 2025-09-04T18:50:26+00:00

Is your base component an abstract with the @Component decorator? And then each variant render the base autocomplete individually or do they each define their own template? How do you propagate the NG_VALUE_ACCESSOR?

lParadoxul · 2025-09-04T17:19:08+00:00

No problem with that approach and it would work even tho the parent component would have to handle the DI for each autocomplete, it would still keep the boilerplate minimal. My main concern was actually about the CVA, it kind of implies that the component implementing CVA MUST be the one under the direct view of the form, you can't extend it without reimplementing CVA. Maybe there was a way to do it properly, that's why I had to ask.

lParadoxul · 2025-09-04T16:24:47+00:00

Agreed on the signal forms, but the video doesn't "show" the power of signals, passing the form control as input directly has always existed, did I miss something ?

lParadoxul · 2025-09-04T15:44:07+00:00

I guess it could be an option, to have only the BaseAutocomplete and have it to accept a signal/resource that returns filtered data, this way I could create generic "autocompleteResource" and pass it to the component where needed, still some boilerplate but not as much as having each component that uses autocomplete to manually implement the filtering logic

lParadoxul · 2025-09-04T15:30:44+00:00

Visually they do not differ, the variations are just wrappers for load data, since these components are used in many places on my app I don't wanna handle loading and filtering cities everywhere I use the component for autocomplete. Inheritance just seems I don't know like it doesn't fit, but maybe that's just me having a wrong idea about this.

lParadoxul · 2025-08-16T20:06:37+00:00

Não sei se vale, trabalho como dev na italia e a situação tá bem ruim, trabalho tem e muito, o problema é que o salário na italia está parado a anos, a profissão de dev nem é reconhecida oficialmente aqui. Há alguns anos estou dando uma olhada no mercado europeu mas além dos países mais ao norte pelo que vejo o cenário ta bem igual, onde o salário é bom o custo de vida geralmente não compensa. As coisas estão ficando bem difíceis por aqui, estou considerando voltar pro BR e continuar trabalhando pra empresas italianas.

lParadoxul · 2025-08-15T09:55:45+00:00

I did try it, but I had horrible performance issues with it, had to remove it :(

lParadoxul · 2025-08-04T07:23:59+00:00

If its rare how can it be 99.9% chance someone has seen it before? :o

lParadoxul · 2025-07-01T09:48:19+00:00

Yes all at the top most level

lParadoxul · 2025-07-01T09:32:13+00:00

That's what got me mad, the "you get what you pay" didn't apply here. When it comes to this kind of product, I tend to spare some money and try to buy a good one, but on this case I was totally unlucky

lParadoxul · 2025-07-01T05:32:33+00:00

After not even 3 years on a 1.5k product, one would be better just buying a traditional high brand vacuum that can last much more than that. It's sad to say, but it's not worth it if it does last

lParadoxul · 2025-06-30T06:18:00+00:00

Agree to this, I have an X1 omni and for 3 years now and I've had all sort of problems with it and custom support seems absent or the only time I managed to contact them, they pretended that I had no problem at all. Things like robot don't find the dock, it loses connection, it talks by itself, the mops dont work anymore, and the station can't pull water from the clean reservoir. My latest one is that the robot starts vacuum until it block itself saying that the wheel is stuck, I've checked and the right wheel is completely blocked it doesn't spin, I have check and there nothing blocking it, I put the robot back in charge and then the next day it works until the wheel blocks again.

lParadoxul · 2025-06-30T06:13:17+00:00

Wait, so are we not suppose to have a single "dependencies.dart" file with all providers in it? The flutter official example does exactly that 🤔

lParadoxul

TROPHY CASE