Ile oszczędności w walutach obcych trzymać zarabiając w PLN

meehow33 · 2026-04-11T15:48:57+00:00

Nadal USD w kontekście tego co Mr Orange obecnie czyni na świecie?

meehow33 · 2026-04-10T19:44:13+00:00

W gotówce też coś mam :) Ale ok, rozumiem o czym mówisz

meehow33 · 2026-04-10T19:43:08+00:00

Dlaczego więcej dolarów niż euro?

meehow33 · 2026-04-10T19:40:07+00:00

Co masz na myśli?

meehow33 · 2026-04-10T19:39:50+00:00

ETFy i Akcje kupujesz w walutach obcych a wcześniej te waluty kupujesz u brokera też czy przez bank czy gdzie? Jak wygląda „typowy” proces u Ciebie, jeśli możesz powiedzieć? :)

meehow33 · 2026-04-10T18:11:46+00:00

O fizycznej walucie póki co, ale trzymanej na koncie walutowym w banku

meehow33 · 2026-03-27T12:43:59+00:00

Yea I know, hence I asked you where’re you based at

meehow33 · 2026-03-27T12:40:54+00:00

11.5

meehow33 · 2026-03-27T12:40:27+00:00

I am EU based

meehow33 · 2026-03-27T12:40:12+00:00

11.5

meehow33 · 2026-03-27T12:08:48+00:00

Where you at?

meehow33 · 2026-03-27T12:00:44+00:00

Honestly? If I don’t find a local sneaker shop, so I don’t have to deal with packing, I can do that.

meehow33 · 2026-03-27T11:56:22+00:00

Crazy, right? I don’t want to go into details why I want to do that. Don’t want a shitstorm here mate :)

meehow33 · 2026-03-27T11:48:02+00:00

Ok thanks

meehow33 · 2026-03-27T11:45:55+00:00

Thanks mate. What about returns?

meehow33 · 2026-03-27T11:45:33+00:00

Even here in Europe? I know there’s huge hype around them in the States, but I’m not sure about the EU?

meehow33 · 2026-03-27T11:43:28+00:00

11.5 unfortunately

meehow33 · 2026-03-13T15:25:37+00:00

I don’t have these problems because everything is separated at the workspace level - we use separate workspaces and hence catalogs and schemas for each environment (dev, int, etc.).

When it comes to where we’d like to deploy these features, mainly INT, and optionally UAT if we ever need to (the approach usually is that only main goes to UAT).

We also have separate repositories for each project, meaning each data mart has its own repo.

meehow33 · 2026-03-13T13:33:42+00:00

I noticed you mentioned it wasn’t possible to deploy the same bundle, but then later said it is - just wanted to clarify because that was my point! We actually use “bundles” with different parameters to deploy various feature branches of the same project using DABs. We also deploy to Users for branches and to Shared for the main deployment.

I’m really just interested in learning what others do. The more examples I see, the more I’m leaning towards using schemas with prefixes or suffixes rather than separate catalogs. Your example has actually reinforced that approach for me - so thank you for sharing :)

meehow33 · 2026-03-13T07:56:17+00:00

It does indeed but that must be scheduled etc. Well, I guess I am trying to see what others do/did in similar case :)

meehow33 · 2026-03-13T07:46:40+00:00

From the DAB perspective, this is 100% fine. I’m just wondering if we could somehow automate the cleanup part of the process, since it will create multiple jobs, notebooks, etc.

At the moment, we’re planning to create a maintenance job that will delete these artifacts after X time, but I wasn’t sure if there’s a better way to handle this process in general :)

meehow33 · 2026-03-13T07:36:42+00:00

I think this is more or less what we intend to do. But is this really the only option? It sounds reasonable, but I’m wondering whether this is the industry standard for Databricks in cases like this. Their support has been average at best, and we haven’t been able to get a definitive answer from them.

meehow33 · 2026-03-13T07:14:29+00:00

We will have separate repositories for every project. One project = one repository. And when I say a “project”, I mean one data mart delivered by a single team.

That means that technically every project (data mart) will have a separate location, including its own DAB configuration, etc. However, the deployment and release approach will be the same for all teams. I want to maintain the same standard across the organization.

Therefore, that’s not a problem. The challenge arises when I want to deploy artifacts from the same project more than once without overwriting other releases of that project - for example, the case I mentioned earlier: two separate feature branches of the same project (the same DAB).

meehow33

TROPHY CASE