How we code in pairs
At Friendsurance, we are doing extensive code reviews and unit testing of all code. On top of it, we started to experiment with pair programming.
At Friendsurance, we are doing extensive code reviews and unit testing of all code. On top of it, we started to experiment with pair programming.
I won’t be the first one to tell that 2016 was a hard year. Looking back though, I could accomplish almost everything I planned for the year. Without getting sentimental, I can think of the following wrap-up ;)
I’ve started my journey in algorithms and data structures more or less three months ago. I am not there, where I wish I’d be, however I am satisfied with the process. My goal is to learn, what I knew before and what I know is incomparable, this keep me going.
It’s not a secret that String objects in Java consume a lot of memory (just a reminder that each character eats two bytes, yay!). We use strings everywhere, which is kind of natural, sometimes (and often) there are also duplicate strings all over the application. In java several distinct instances of identical strings will be created. This is not ideal and definitely not what we want.
We want to keep our private artifacts private, making sure that only people with appropriate rights have an access to them. AWS S3 is a good candidate to consume and deploy such artifacts.