That would be my one major drawback against starting up here in Norway. I've seen calculations of how companies like Facebook would fare if they started up in Norway, and it wasn't pretty. You pay tax on the value of your shares, even if the company isn't making money...
However, for start-ups that aren't looking to have hundreds of millions of users/customers before breaking even, it is still worth a shot!
If you ask a Norwegian: "Did you hear what Erna said yesterday?", everyone will know who you're talking about. That's just the kind of country Norway is ;)
This doesn't sound unthinkable in other countries. I'm from Norway, where the maximum prison sentence is 21 years, with a third of that often being deducted for good behavior, leaving 14 years.
I can see your point, but I would never pay for a product like this without a free demo version.
These Visual Studio extensions often have the side effect of taking up way too much of the computers resources. Without having a fully functioning (time limited?) version of the product on my machine, working with a large VS solution, I will just move on and probably have forgotten about this by tomorrow...
With a free version available, I would have tested it and if it works as well as in the video, I'd most likely pay for it and recommend it to colleagues by the end of the day.
Many projects are small, and even big projects tend to be split into many smaller projects. In those cases, it is vital that everyone on the team can do anyone elses job if they have to. You tend to get one role most of the time, but you need to be able to understand the whole project.
I would recommend looking into "old fashioned", established companies who do their own development. I've worked with banks a few times, and they seem to often still do the "database department", "back end department" and "front end department" thing. I'm sure there are other areas too, but that's the only one I've had experience with.
I think you make a good point. In a similar situation (I wasn't personally involved), I know the consultant charged 20 % of the normal rate for being "on duty" and charged the normal rate for every begun half hour of active service. Had it been me, I would have used a similar model.
With micro service architecture being one of the big buzz words at the moment, I see this as a great way to separate individual micro services (with some clever routing in front). Using Nano would make these services separate and easy to update without affecting eachother. Continous delivery FTW :-)
Perhaps I'm missing something here, but where's the guarantee that these ID's are unique? As far as I can tell, an ID is made up of a timestamp and a random number, generated by the JavaScript enginge - and typically seeded with the current time.
Wouldn't that give relatively good chances that for a system with many users, two users would actually generate the same ID?