gituliar
Joined 16 years ago
Joined 16 years ago
Basically `Error` is an alias to `std::string`. This way code is more meaningful as returning just std::string is too generic.
It's also my convention to report errors as return arguments in this particular codebase, instead of throwing exceptions for example.
Definitely, some can use both.
Again, it very much depends on the persona. All I need to be productive is a clear to-do list and no destruction, to focus on my work. No extra techniques, like Pomodoro, is necessary in my case.
Instead, I put my tasks in a Moleskine notebook, mixed with other notes and ideas of mine. In front of each task I put a square box, to be checked when the task is completed in the future. Usually tasks are 1-2 hours long, they are for evenings, longer tasks are for weekends. It's crucial to keep tasks small, no longer than 1 day of work, so split big tasks into small. This is crucial, as abstract tasks lead to procrastination and make you lose focus. The checkbox gives satisfaction when done and remains in the notebook, so that you can see a lot of completed by reviewing your notes.
I use this technique for 3 years now and it works for me. Not sure if it's known by other name as I came to it myself. Hopefully, this can be useful for others as well.
In your example, at first you pay taxes in Germany and if Estonian taxes are bigger, you pay the difference there.
More here https://socialsecurity.belgium.be/en/internationally-active/...
For example, option price among other params depends on the interest rate. For the last decade interest rate was around 0% in Europe and slightly higher in US. If you train on that data only, there is no chance to "learn" option prices in the high-interest-rate environment which we saw for the last few years. Hence, you need synthetic data to learn that region of the market space.
The finite-difference covers wider range of problems, including stochastic volatility models, like SABR or Heston.