Profile cover photo
Profile photo
Brian Johnson
11 followers
11 followers
About
Brian's posts

Post has attachment
I'm starting to see a pattern
What are design patterns and why are they important? According to Wikipedia a design pattern is a general reusable solution to a commonly occurring problem within a given context in software design. So, what does that mean to us and why should we care? Desi...

Post has attachment
Why time tracking may be hurting more than your productivity
If you work for a consultancy time tracking is obviously important because you need to accurately bill the client for the work that was done. I'm not going to address that here because I don't work for a consultancy. Some companies that are not consultancie...

Post has attachment
Hiring Software Engineers
We recently looked at our hiring process to attempt to determine what works and what doesn't. By "works" I mean what gives us insight into future performance. The first thing we realized was that we had no process. Step 1: Create a process The first thing w...

Post has attachment
S3 with strong consistency
We use S3 extensively here at Korrelate, but we frequently run into problems with it's eventual consistency model. We looked into working around it by using the US West region that has read-after-write consistency, but most of our infrastructure is on the U...

Post has attachment
S3 with read-after-write consistency
We use S3 extensively here at Korrelate, but we frequently run into problems with it's eventual consistency model. We looked into working around it by using the US West region that has read-after-write consistency, but most of our infrastructure is on the U...

Post has attachment
The Premortem
We are all familiar with the postmortem. When things go wrong, we want to understand why they went wrong so hopefully we can avoid them in the future. This works well for classes of failures that are due to things like infrastructure or procedural deficienc...

Post has attachment
You are bad at estimating
For the last 4 years or so at Korrelate we have been doing Scrum. We had 2 week sprints, estimated stories and planned based on those estimates. In that time we have learned one very important lesson: we are very bad at estimating. In retrospect, this shoul...

Post has attachment
Wait while more posts are being loaded