pambeesly8

This is amazing, thank you so much.

Am I right to understand that currently there are only 4 works available to explore?

The JS viewer is amazing. From the description:

  >you can switch between high-resolution visible, infrared photography, and infrared reflectography images

Can someone explain why infrared and reflectography scans would be interesting?

I was really hoping for more advice on letting the team members appreciate code reviews, and not take it too personally.

We've just recently introduced code reviews on our 3-4 person team. We're working in a particular environment, and most people have no production level experience in that environment. These people have gotten used to _just getting it to work_. We've clearly stated that we will be going with Google's style guide, but we can always divert, as long as everyone is in agreement. When pointing out that the changes are not according to the style agreed (frankly, it's not so much about style, as it is about using patterns from other programming languages, that are not applicable), the response is:

- it works

- I don't think you understood what this does (note: no comments or attempt to explain)

- In the future, please do not waste more time with pull requests. Desktop sharing and a call is the most efficient way to work in remote teams.

It's getting more and more hard to keep an open mind and not take things personally. We're at a point now, where there's a intermediary person refactoring the code.

Does anyone have any practical advice on people understand the importance of structure code, and to limit the _personal factor_?