Doesn't work for Sweden anyway, because people will think you're mad if you don't take at least three weeks in July/August, where there are no other public holidays.
Maybe a feature where I'm manually picking some days and it tries to figure out the best way to stretch the remaining nice would be useful.
You can reduce the number of days it places already, though. So if you assume you take 15 days in july just reduce the amount of days by 15. Don't get to visualize them, however, and its choices might overlap with yours, so not a perfect workaround.
I also would like the week to start on a monday, btw. Perhaps it could be tied to the country? When choosing norway, calender could shift to how it's displayed here.
And humans spent even more effort to navigate themselves. As they were getting to the birds, as they were observing the birds and as they were getting back from the birds. Everyone who is not blindly thumbling or being pushed by winds or water does some sort of navigation. Even if just relative to their surroundings.
I would argue that observing birds by eyes does not really help you teach a slab of silicone to distinguish birds. But if you feel that it does, then surelly all the walking, riding, sailing around humans did should also be counted to the navigation task.
We're talking about a collaboration tool here, and there is no jurisdiction that I know of where employing such tools, even when mandated by the employer, is unlawful; definitely not related to GDPR which is completely out of scope here.
Of course, as any tool can be used for bad things, so if, say, instead of the default sharing of just the development apps, the employee shares his browser, email client or instant messenger which he uses for personal purposes, you could argue it crosses the line into unlawful workplace surveillance, so it becomes a matter of setting correct policies. Sounds to me like an enterprise feature set you could charge for, as complement to the free tier.
This is a wild exaggeration. Again, GDPR is not relevant here and private communication on the employer's infrastructure generally caries no reasonable expectation of privacy, at least in the US, double more so when you are actively sharing that email with your team.
For any given data, it can be used as code, and vice versa. But for any given program, it should be very clear what's code and what's data.
If I send a Python file over SSH, it should most definitely be data for all software involved. And I for sure should be able to send a Python file via OpenSSH, not matter what either is licensed as.
Just say kilotons, or 1000 (metric) tons, if you're speaking to laypeople.
reply