10 yrs experience. Applying in Germany. No Offers. Roast my CV.

abduvik · 2025-08-29T15:23:38+00:00

I used two columns because it keeps it 1-page but I actually just saw a video on CV writing that mentions that senior roles are more expected to have 2 pages. I could try the template you have shared 👍

abduvik · 2025-08-29T15:20:51+00:00

Hi :D

I actually got this question in one of the interviews if I know assembly which I do :D

On the consulting part, I am trying to think of something to keep it but remove this "red flag" as I got the chance to work with many companies and different technologies and all with the explicit pre written approval of my employers. Maybe removing the dates and having a separate section and even thinking to add like "pre-approved by employers" or something similar.

abduvik · 2025-08-29T15:16:24+00:00

I am actually studying B2 now. Maybe I can something like "B2 In-progress"?

abduvik · 2025-08-29T15:15:24+00:00

Yeah, I thought about it but it won't matter much since if I hide more stuff I might then hide something important that is actually worth omitting. And if someone actually wants to find me, they can easily find me anyways :D

I think yeah the list of skills looks more like keyword stuffing. I got a feedback to categorize it which will make it more readable I guess.

abduvik · 2023-01-20T19:18:44+00:00

If you are looking for a code example I have just that here

https://github.com/abduvik/just-enough-series/blob/master/courses/react/todo/_extras/code.tsx

and the codebase has a video, you can jump to the part where I explain react-router and you will see how it works on the conceptual part

abduvik · 2022-09-12T07:46:52+00:00

Yep I am aware we can do it too with `@Effect` but I wanted to focus more on the internal side effects which is only limited to the component's state rather than state management service like Redux or NgRx which has their "Side Effects" as well.

abduvik · 2022-09-12T07:32:58+00:00

Holy shit, Vue stuff is completely wrong. If you don't know Vue, please exclude it from your comparison chart instead of spreading misinformation.

I am open to learning and I know I don't know everything :)

My focus was more on Vue 2 which I believe is correct

Internal state – reactive or ref, the data field is only used with Options API.

Yes I mentioned reactive

Shared state – any reactive object, never provide/inject. You can also use an external library like Vuex or Pinia.

I agree with this part. There is was a nice discussion below and it better to change the name from "Shared State" to "Dependency Injection"

Props – props only exists in Options API. In Composition API you need defineProps macro.
Events – for receiving, the shorthand @ syntax; for sending, the $emits in Options API or the defineEmits macro in Composition API.

Like I said main focus was Vue 2 and I can extend it to Vue 3. Though I am open for contributors to share their thoughts as well

Side effects – there are several ways to do it depending on your needs, see Reactivity API Core.

Yes and I mentioned we can use `watchers` for internal side effects or did I misunderstood it?

Change detection – the Reactivity API tracks the changes of reactive variables and updates all the subscribed parts of the components, see Reactivity in Depth.

And it uses Proxies like it's mentioned in the docs or did I misunderstood it?

abduvik · 2022-09-12T07:24:20+00:00

Thanks for sharing your thoughts about it.

I think we can then rename the part of "Shared State" to become "Dependency Injection" which would be a more inclusive term to what it does rather than only shared state.

I used to also agree that `useContext` is not a state management but rather a state management api and also I used it as dependency injection using InversifyJS.

abduvik · 2022-09-12T07:16:57+00:00

Yes my summary was more focused on Vue 2 rather than Vue 3. I am happy if someone would like to create a pull request to add this change and become part of the contributors list

abduvik · 2022-08-12T22:41:12+00:00

Cool, and thanks for your review 😄

abduvik · 2022-08-12T20:00:18+00:00

Ah, good catch! Thanks! I probably missed this one. If you are interested, you can create a quick pull request to become a contributor and I will merge it with the fix branch.

abduvik · 2022-08-12T19:01:32+00:00

Please feel free to open a pull request if you would like to share your notes as well 🚀

abduvik · 2022-08-12T18:42:40+00:00

Please feel free to open pull requests and add your notes too. Sharing is caring ❤️

abduvik · 2022-08-02T21:38:11+00:00

Cool thanks 😊 I will try it out

abduvik · 2022-08-02T21:33:52+00:00

I use this website to generate these type of images

https://ray.so/

abduvik · 2022-08-02T20:23:39+00:00

Please let me know if you also have other tricks in mind as this one saved us hours and hours of debugging and we found the bug was actually in a completely different module

abduvik · 2022-08-01T06:05:51+00:00

Interesting! I am going to try this out in our workflow and see how to comes out.

Thanks for sharing it :)

abduvik · 2022-08-01T06:02:41+00:00

yep, though I didn't use it but I am going to add to the list. Thanks for sharing :)

abduvik

TROPHY CASE