cultofthecow

Speaking of my experience in Amsterdam.

1. Cars are just less practical and expensive. I personally avoid city center at all cost.

2. AC absence is not about sustainability at all. There was no need for them in this climate except a couple of summer weeks.

3. Never heard of people saying that. Constant queues at Schiphol. Government plans to extend and build another one IIRC

4. It’s just normal here to satisfy all of the food preferences.

5. 99% of the cafes has “normal milk”. Lactose intolerance, maybe fashion on oatmilk.. don’t known exact reason on why it’s not only the cow milk.

Twilio, voice app etc. But I was so lazy to do a proper marketing and sales.

However I had some ideas that I can share with you if you want:) For free ofc!

Wish you all the luck! Contrast with nice product! Super good!

I would love to the industry to have a higher entrance barrier.

I would love to be able to solve more with less.

I would love industry to deliver more value with a higher speed.

Progress is inevitable. So I would love to start adapting faster and be on top of it even if it will require me to leave my current role and maybe switch to another one.

I've seen too many people here in IT doing the things they don't like or coming to the job simply because "it pays bills". I've seen 25 yoe engineers who know literally nothing because they were doing literally nothing for the last 20 years. I've seen junior developers who barely know fundamentals and I'm speaking of some really dummy things. I hope industry will naturally heal itself even if it'll make me leave or switch.

Anyways I hope you're right to be honest. And let's see.

MeetingBar - simply does it's job. simple and effective. has inyourface functionality in place.

Arc - wanna jump off to Safari but I think Arc is still the best one so far.

Obsidian - I'm new to it but "file-first" approach looks good.

1Password - still nothing beats it.

KarabinerElements+goku - to have it configurable. have layers of keybinding to launch something. Like ".+i" will open iTrem2 and so on.

Ice - just landed my setup.

commenters are wrong and I know no one who were not able to find a job.

Current rates - is another question. They are not that high.

long story short: if you’re a good specialist, you will be good.

- linkedin profile looks weak. Elaborate on what were the duties in form of showing up your professional achievements. Like how you improved the product with your work. How you increased company revenue. Did this -> it lead to that. This approach shows your real impact (at least a sign of it). "reduced infra cost for 20%", "latency decreased which lead to more registrations", "hired and structured 2 team", etc..

- use recruiters. 99% of time their help will be useless but because there are a lot of them this 1% will cover the rest.

- don't spend your time on no-name-another-job-list-platform. it won't work. approach company recruiters directly, apply via linkein or connect with recruiters there.

- "I can do everything for 60k" might sound like a red flag. Avoid it during the conversation.

- Interview passing is a skill. You need a time and a volume of interviews to train it. Doable.

- don't listen to "oh yeah that's a terrible market I can't get a job as well we gonna die poor" comments. you don't know who is behind the comment. like I don't know who are you btw :)

Market is not that bad. It's totally ok. Approach it as a project. Code, code, code, read, watch related videos on youtube. Acquire some clarity that you know your shit.

I wish you all the luck, you will make it!

https://www.iamsterdam.com/en/live-work-study/living/officia...

Other than that - I haven't found anything useful among myriads of cv-ai-smart-ml-web3-bla-bla tools that are all over the internet these days.

I might only use Grammarly and ChatGPT for more or less adequate outreach.

Use and depend on abstractions maybe?

Whole hashtable? Or what?

You mock interface/api of “something” you depend on to model the behavior you might deal with within the part of code you test.

thats it. nothing else.

during unit test phase I want to make sure that this exact code works as a state machine given all the possible inputs/outputs and that it handles any possible situation any dependency can cause.

If you need to debug code BECAUSE of the tests and not WITH the tests then something is wrong with the architecture or approach.

tldr. mock dependencies. model behavior of the dependencies. make sure you can debug the code with the help of your unit tests on the very layer you’re working with at the moment.

1. You still need to update the fake object once you gonna add a new behaviour.

2. Fake object has a tendency to become logic heavy. Someone will add a stupid-not-needed-map to test some shit you don't need to test in this unit\layer.

3. You only need to mock the behaviour you depend on. If you've added new Method and you need to mock it despite the fact you're not using it in the code you're testing - its a bit weird and smelly. Consider rethink SOLID principles at least.

4. Go. Gen. Effectively you can automate mock generation. Debatable but it's cool.

Just. Keep. Things. Simple. Depend on what you need. Mock behaviour you need. Try to test flattened structure - do not test the layer below the one you're testing ATM (unit tests).

Ok.

As affected one, I can say with a full confidence - straight to the beach

and it's author: https://daniel.haxx.se

Some small real problem I faced before: test\validate idea by counting how many times website visitor clicked the certain button. So I automated it with google sheets and some custom script\backend.

Landing is still in progress... Don't kill me for the language skills, English is not my native)