nicolasd

Two reasons that come to my mind: 1. legal burden of hiring globally 2. while allowing remote work, the company might not be set up for asynchronous communication

I’ve raised similar concerns as well, especially with the same argument about non-development departments.

However, with the Ultimate plan you also get free guest users, which could serve well for most users who are not developers.

That's not true. "GraphQL requests" are _just_ POST requests with a JSON that contains "query" and "variables".

So it's not the request itself that is not debuggable, but maybe the query interpreter on your backend with the framework you're using.

I tried to follow the concept of minimalism a few years ago. For everyone else who is struggling with it: don't stress out because you can't live with one backpack. Yes, you can get rid of a lot of stuff and you should do it, but don't do it too extreme. I don't want to live without my music instruments or my sports (which requires a lot of gear) - don't fall into the trap as I did and feel bad for owning it.

Start small and collect all the stuff you didn't touch for more than 1 year - don't throw it away, just put it in the cellar and after a few months realising you don't need/want it give it away.

> but they definitely seem to be underpaying in general

Interesting that you say that. I can't speak for US area, because I live in Europe. Looking at the Spain salary, which is about 110k seems pretty good to me. Working as a senior frontend dev in my area (which has similar costs of living as Barcelona) gets you payed about 30-40% less than that.

How good is the "Blueprint for Phoenix Context" part? I am already working with phoenix/elixir on a daily basis and would be only interested in good examples with contexts.

Maybe in Switzerland - but not in Germany / Austria. If there are so many companies that do this, please tell me :)

When checking out a new branch or planning a new feature - ask yourself, if you would deploy it today and the customer sees it - will he notice it/benefit from it. Of course this does not work for all features/long-term things, but it helps to look at it from a customer perspective. First focus is: customer gets his job done (core features & UX) Second focus is: customer is happy using your product (these are all the other things that are nice to have + UI).

Thanks for the detailed answer and coming up with a property-based test that is not a "1+1=2" example :)

Serious question: How would you suggest to write a test that prevents this? You wouldn't make an assertion on clearTextPassword !== passwordHint. While developing I would think "Who will ever do that? That would be insane".

But yes, even if there is no test, this should have been caught in code review or latest when testing the OS.

Isn't a dealbreaker if you use it like I do and set a global touch bar configuration, which doesn't change. Only useful feature of the touchbar is Touch ID (which works very well). However, regarding your question about productivity: no it doesn't increase nor decrease with the touchbar (especially if you can work with caps lock being the ESC key in vim).

For VIM: I am using CAPS Lock now as ESC key, because there is no physical ESC Key with the touch bar anymore.

Generally: I configured my touch bar to match the old keyboard function keys layout & they never change, no matter if I switch the program. I just don't want to change my behaviour + can't deal with the fact that I can't quickly change volume/brightness + hit play/pause/forward/backwards keys.

How did you get from 10k to 350k in one year? Was it the SaaS products + consulting ?

> Interestingly, I still find a lot of value in Messenger. But they've split concerns so you can use that without reactivating your FB account.

Afaik when you deactivate your Facebook account, you have the option to keep the Messenger account, but just deactivate/delete the Facebook account.