Having lived and breathed project management for the past 20 years at various clientele sites, I've come to believe that many of the principles of martial arts can be applied directly to project management.  In this blog, I will discuss how I was able to use these principles to successfully navigate a client environment from day one.

In Part 1 of this series, we covered the basics of creating a JMH project and getting it to run, proposed a small benchmark, and showed what the implementation would look like. In Part 2, we looked at how to configure JMH, how it works, and why certain parameters are necessary. In this last part, we'll focus on how not to write a benchmark for JMH and why some precautions are necessary. This may be the most important part of the three, as it'll give you insights into some quirks of the JVM.

In last week's blog, we discussed the basics of creating a JMH project and getting it to run. We also proposed a small benchmark and showed what the implementation would look like. Today, we'll be looking into how to configure JMH, how it works, and why certain parameters are necessary. (Be sure to join us next week for tips on how not to create benchmarks!)

You have an application running. It's doing pretty well, except for the fact that it's somewhat slow. You have identified the bottleneck, and now you're trying to come up with the ideal solution. There are a myriad of mechanisms you could try, but you don't want to deploy each one of your attempts to the development environment and then check the performance there. And running the application locally might not be the ideal solution either. So, what do you do? 

(The following article is property of Avenue Code, LLC, and was originally published with permission at TotalRetail on August 28, 2018.) 

Heather Craig, head of retail experience at thredUP, talks with us about the rapid growth the consignment shop is achieving by building on a unique business model with customer-oriented technologies and a spin on a physical retail presence.

In our last article, we talked about Prototype Inheritance in Javascript. Today, we’ll take a look at the different ways to create objects in JavaScript and the resulting prototype chain for each method.

JavaScript uses a prototypal inheritance model, and this can be a little confusing for developers coming from class-based languages such as Java or C++. Prototype inheritance is simple but yet a powerful model. In this post, we are going to talk a little bit about it and how it is built in JS. If you haven't used a prototypical model before, don't be intimidated - we'll break it down!