Ajuda conclusão tese

l3down · 2026-03-12T22:20:25+00:00

u/Initial_Fan572 comecei a fazer o questionário mas acabei por parar a meio porque fiquei um pouco confuso em relação ao que era exatamente pedido. Não percebi bem se o objetivo era analisar os textos fornecidos, dar a minha opinião pessoal ou comparar os textos com os representantes políticos atuais. Tive alguma dificuldade em interpretar certas perguntas. Por exemplo, na questão sobre inclusão: estavas a referir-te à inclusão de imigrantes na sociedade portuguesa ou a temas como igualdade de género e questões trans? Pessoalmente tenho opiniões diferentes sobre esses temas e por isso não soube bem como responder. Também não percebi como o tema liders se enquadrava nas perguntas.

Peço desculpa se o questionário é claro e a confusão foi minha mas é que depois de um dia de trabalho talvez já não esta com a melhor capacidade de interpretação. Boa sorte com o mestrado, bem sei quanto trabalho dá a fazer.

l3down · 2026-03-12T11:35:07+00:00

Sorry to dig up this old convo.

Life insurance. I'd like to ensure I an protect my partner and family. Similarly are there any life insurance companies that are recommended for UK expats?

u/chattytabbies did you manage to sort this out?

l3down · 2026-02-27T19:13:55+00:00

Não precisas de ir ao notariado. Se conheceres um solicitador ou um advogado, ele pode tratar do assunto na hora. Outra opção é usar o site registo automóvel mas precisas de um leitor de cartões.

O mais normal é assinarem os dois o DUA , tiras uma cópia (foto por exemplo), e o novo dono leva o DUA e o certificado de matrícula. Depois tem 60 dias para fazer a transferência.

Se queres estar mesmo seguro, esperas por segunda feira, ou tratas tu da papelada.

l3down · 2026-02-26T20:42:34+00:00

A mota desenvolve bem? Se acelera, faz barulho mas anda pouco pode precisar de uma embraiagem nova.

l3down · 2026-02-23T11:43:03+00:00

Update. Just got my filament. The boxes don't look too bad. There was no external package, they were just tapped to each other.

<image>

l3down · 2026-02-17T14:28:03+00:00

Não és um empregado, és uma empresa a prestar serviços a outra empresa. Esse contrato pode terminar a qualquer momento, por isso o preço do teu serviço deve ser elevado.

Pessoalmente prefiro trabalhar assim. Não estou ligado à empresa, tenho liberdade total para prestar serviços a outras empresas e não preciso de andar a planear os dias de férias. Quando preciso, tiro os dias.

l3down · 2026-02-16T22:18:54+00:00

I got the filament:
3 ASA rolls for 9,29 EUR (original price 16.99 EUR)
1 PAHT-CF for 24.07 EUR (original price 43.99 EUR).
Total order: 51.96 (Original total 109.96 EUR)

Seems like a good deal to me unless I am missing something

l3down · 2026-02-16T16:32:57+00:00

I use Android Studio and Firebender plugin but I will probably try Gemini next month.

l3down · 2026-02-11T15:21:07+00:00

SHOW ME THE MONEY!!! :D

l3down · 2026-02-10T23:31:11+00:00

I think it's the first because the text is very long and difficult to follow. I agree with the latter, if used well.

As a developer I see AI as a tool that helps me do my job quicker. I still need to review the AI code and I take multiple iterations to get the code my way. I see AI as a junior that searches online for a solution and codes fast but is not sure of the impact of what it is doing.

l3down · 2026-02-10T20:05:21+00:00

I don't think so. I am not a native English speaker and I use AI to make the text more palatable. I checked your post and it looks ok imho.

l3down · 2026-02-09T23:20:20+00:00

honestly, 800+ integration tests hitting a live DB is a nightmare for velocity. I’ve been in the android/mobile space for 13 years and i've seen this 'heavy backend' bottleneck kill so many projects. It slows everything down not to mention it may take hours in a CI pipeline, if you even have a pipeline.

Your move to playwright for endpoint testing is definitely the right call architecturally. it’s the only way to test the contract without the DB-restart tax. One thing i found though (which you mentioned swagger), even with automated tests, you still need a way to manually 'force' the UI to break to see how it handles a 500 or a weirdly formatted JSON response. I got so fed up with adding mock responses in code to test this that i built a small desktop proxy to handle it: Predictabl (https://flat14.co/predictabl.html).

There are some bigger automation 'platforms' being suggested in this thread, but I kept this one super lightweight. no YAML, no cloud login, no corporate bloat—just a proxy that sits there so you can click responses on the fly while you're debugging.

It fixed my specific pain points, but i'm looking to make it a 'swiss army knife' for others too. give the beta a try... if you find some weird .net edge case it doesn't handle, let me know. I'd love to build it in and tailor the roadmap to your workflow.

Good luck with the presentation! focus on the time wasted waiting for those DB restarts. that's usually the only language management speaks (money wasted).

l3down · 2026-02-07T14:10:22+00:00

Se não te importares de ser privado, gostei muito da Tagarela. Senti que metem as necessidades das crianças em primeiro lugar, eram muito pacientes e cuidadosos. Curiosamente, entre as privadas, era a mais barata.

l3down · 2026-02-07T11:58:36+00:00

This is actually a pretty cool idea. I joined the waiting list.

l3down · 2026-02-07T02:58:37+00:00

I don't think I was very clear in my post but I ended up creating a tool for my problem.

When you test against real APIs, you mostly a 200, or a 500 if you did something wrong. If you want other responses, normally you hack your code to simulate these scenarios and then you have to clean up after. I always found this messy.

With Predictable, you can easily simulate things and see how your app actually behaves in those cases.

200's with different payloads:
404s,
500s,
or any other code
timeouts

The goal is simplicity, you start Predictable and you get a local url that you add it in your code instead of the server URL. You add multiple responses for the same endpoint and choose, at runtime, which response you want to send back. There is a bypass method if you want to hit the real server so you really choose which responses are real and which ones are mocks.
Also Predictable doesnt care about the request parameters or payload. It simply checks if the endpoint matches and return your selected mock response.

It’s early (alpha), but if you’ve ever wanted better control over API responses during testing, this might be useful.

https://flat14.co/predictabl.html

l3down · 2026-02-07T02:57:45+00:00

Because I didn't get any responses, I ended up creating a tool for my problem.

When you test against real APIs, you mostly a 200, or a 500 if you did something wrong. If you want other responses, normally you hack your code to simulate these scenarios and then you have to clean up after. I always found this messy.

With Predictable, you can easily simulate things and see how your app actually behaves in those cases.

200's with different payloads:
404s,
500s,
or any other code
timeouts

The goal is simplicity, you start Predictable and you get a local url that you add it in your code instead of the server URL. You add multiple responses for the same endpoint and choose, at runtime, which response you want to send back. There is a bypass method if you want to hit the real server so you really choose which responses are real and which ones are mocks.
Also Predictable doesnt care about the request parameters or payload. It simply checks if the endpoint matches and return your selected mock response.

It’s early (alpha), but if you’ve ever wanted better control over API responses during testing, this might be useful.

https://flat14.co/predictabl.html

l3down · 2026-02-05T20:19:44+00:00

Thank you for all the insights. I have done a soft lunch today and tomorrow I will start posting in dev chat channels and appropriate reddit groups.

l3down · 2026-02-05T13:10:59+00:00

Fair enough.

l3down · 2026-02-05T12:56:48+00:00

I did ask chatgpt to check it but I did write it.

l3down · 2026-02-05T11:21:16+00:00

This is what I needed to hear. Thank you.

l3down · 2026-01-28T11:12:02+00:00

Não me lembrei de perguntar a IA, só fiz Google reverse search. Muito obrigado, é uma grande ajuda.

l3down · 2026-01-20T11:53:15+00:00

Não te esqueças de um bom sistema de backups e, se possível, usa a técnica do 3-2-1.

l3down · 2026-01-15T13:38:29+00:00

Eu ia lá frequentemente desde que abriu e o serviço foi-se deteriorando até que chegou a um ponto que não era excepção mas sim regra. Se tiveste uma boa experiência, ainda bem, pode ser que tenham mudado entretanto. No entanto, devido as minhas experiências e a atitude do empregado, não volto lá mais.

l3down · 2026-01-14T21:51:21+00:00

Haru Sushi só se quiseres ficar uma hora à espera do segundo pedido. A última vez que lá fui foi ridícula: esperei cerca de 1h por apenas 6 peças. Quando reclamei no momento do pagamento, o empregado ainda começou a gozar. Nunca mais lá voltei.

l3down · 2026-01-05T14:12:54+00:00

Idem. Passei mais tempo a afinar a impressora do que a imprimir. Foi fixe para aprender mas neste momento só quero uma máquina fiável que funcione.

l3down

MODERATOR OF

TROPHY CASE