well-described task is at least half of the story behind its successful implementation. Some other success factors are hidden in what happens to the task further down the road and especially in how the necessary feedback is provided and processed in the task implementation.
With Ruby on Rails as our primary backend technology, we have developed a set of practices for testing our applications. Our goal was to maximize the efficiency of writing tests that cover the most critical parts of the software built.
The most popular approach to testing React components is to use either Mocha+Chai+Enzyme or Jest+Enzyme. In this article, we will describe our React components testing practices with Jest+Enzyme which are also applicable to Mocha+Chai.
CoderDojo Poland is a volunteer initiative dedicated to teaching young people about programming. It was first started in 2013 and is present in many cities across the country. CoderDojo Poland is an autonomic part of the global organization CoderDojo Global.
Once a month, the Selleo community gathers together to take part in an internal day, which we call Haxorz. Haxorz main purpose is to spread knowledge through workshops and presentations delivered straight from our developers, practising presentation skills while having a bit of a break from coding and spending time with colleagues.
PayPal is known for being the most popular payment service available out there. In 2010 with the launch of Stripe the choice stopped being so obvious. Although solutions like Amazon Pay, Apple Pay or Google Pay are emerging day by day, for many companies the choice is still between PayPal and Stripe.
A 360-degree feedback is a process through which feedback from an employee’s subordinates, colleagues, and supervisor(s), as well as a self-evaluation by the employee themselves, is gathered. This is what the Wikipedia can tell you…
Naming things in programming may not be hard (a matter of imagination), but it is definitely hard to do it right. Also, it turns out to be very unclear what “right” means in each and every context. It doesn’t change the fact that in 8 out of 10 PRs I review, I provide a feedback related to naming, be it naming of classes, methods, fields, variables… you name it
