“Senior Software Engineer Interview Questions” article published Rudolf Olah, April 30, 2019March 10, 2024 Arc.dev has published my article “Senior Software Engineer Interview Questions” Continue Reading
Getting Things Done with Process Design Rudolf Olah, March 19, 2019March 10, 2024 Process design is a way to examine business (and personal) processes for efficiency and effectiveness. It’s a way to get things done. Is there a way to split up that process so that it can be delegated to others so you can scale up? Continue Reading
Coaching as a Team Leader Rudolf Olah, February 2, 2019October 21, 2024 This article emphasizes the crucial role of a team leader as a coach and mentor… Continue Reading
Reactive Programming with JavaScript, Ruby and Python Rudolf Olah, April 26, 2018May 12, 2020 Reactive programming is a concept that is finally gaining some popularity among programmers. It makes… Continue Reading
Speeding up Ruby on Rails Tests and RSpec Rudolf Olah, April 6, 2018July 28, 2024 There comes a time in the life of every Ruby on Rails project where you… Continue Reading
GraphQL with MongoDB using Mongoose and Node.js Rudolf Olah, February 12, 2018May 12, 2020 As part of a prototype/exploratory project in March 2016, I explored how to build a… Continue Reading
PyCon Canada 2017: “Python as a Philosophy” Rudolf Olah, November 14, 2017December 8, 2023 I was in Montreal, Canada for the PyCon Canada 2017 conference and presented on the… Continue Reading
Quoted in “The Secrets Behind Great One-on-One Meetings”, an O’Reilly report Rudolf Olah, August 31, 2016March 10, 2024 I was quoted in the O’Reilly Media report, “The Secrets Behind Great One-on-One Meetings”. As an engineering manager, I appreciated it whenever my reports would bring a topic to the 1-on-1, whether it was a technical topic or a career or mentorship topic. Continue Reading
Cause & Effect Diagrams Rudolf Olah, June 9, 2016March 10, 2024 Cause and effect diagrams, also known as Ishikawa diagrams, are one of 7 basic tools of quality. Cause and effect diagrams are useful because they let you list out all the causes that you and/or your team can think of. Having a team think of possible causes is similar to the concept of peer review in software development projects. Where one person thinks of a few causes, another person will think of different causes. This gives a broader range of causes to investigate. Continue Reading
Using SEMAT Kernel for a Software Project Rudolf Olah, January 22, 2014March 10, 2024 At its core, SEMAT consists of three layers: customer, solution and endeavour. Each “alpha” component of each layer has a checklist to see which progress level it is at. Continue Reading