Introducing myself

Hi there,

It is my aim to write a series of articles based on my personal experience on programming from now on and, why not, maybe from my past as well, about coding and related activities.

The approach I'd like to take is about experiences, either good or bad ones. And about any interesting code snippet I may have come up or come across.

My linkedIn introduction

My name is Víctor Molero, 40yo, father of two children. I'm passionate about building (or refactoring) software to a high quality standard by using proven good practises.

My background is made up of a Computer Science Bachelor, 15+ years of experience working with a wide range of technologies and a special care to the detail on my day by day work.

LinkedIn profile: https://www.linkedin.com/in/vicjmt/?locale=en_US


Thanks

I'd like to thank Sandro Mancuso, whose book "The Software Craftman", enlighted me to start writing for the community to spread my (little) wisdom. Spreading the word for the benefit of the community, a professional trait, that we, coders, should promote and do actively. All these years I've been lazy to do it, maybe scared of whatever, maybe not confident enough, it's never late to start sharing (I guess and I hope).

Also, I have to mention Frederick Brooks and his "Mythical Man-Month" who coined the concept "tar pit" in terms of a software project. You guess why.

Apologies in advance for my crappy-sloppy English, please feel free to correct me and I'll fix it asap.

Víctor


Comments

  1. Darz Veider5 May 2017 at 16:34

    I find your lack of faith (in your english) disturbing....

    ReplyDelete
  2. Darz Veider5 May 2017 at 16:34

    No entiendo nada, pero está guay!

    ReplyDelete

Post a Comment

Popular posts from this blog

Bulk Inserts and the Performance Holy Grial (Part II)

Hi, Back to our topic ( see previous post ) about bulk inserts using PHP and Oracle OCI library, the first approach I'll explain today is as follows: Public method bulk_insert public function bulk_insert($common, $data) { try { $params = $this->prepareBulkInsertParams($common, $data); return $this->ociBulkInsert($params); } catch (Exception $e) { $this->logger->log(ERROR, $e->getMessage()); } } Neat, isn't it? At a first glance, a much clearer method is the result of a first refactor. Many of the code pieces have been extracted to a new method ( Extract method , Refactoring, K. Beck) alongside with new ones to give support to the PL/SQL batch insert syntax. Preparing the Parameters This method is just for extracting the incoming data and transform it into a more manageable array. private function prepareBulkInsertParams(array $common, array $data) : array { ext...
Keep reading

Legacy code concepts II: the Seam Model

Hi audience, According to my last post, there are some important concepts related to legacy code that it is worth writing down and, therefore, have a clearer picture. Sensing and separation were two of them, both concepts tightly related to breaking dependencies. Moving forward, in line with those, I’m going to write about the Seam Model, introduced by Michael C. Feathers in his book Working Effectively with Legacy Code . The Seam Model The Seam Model is a convenient name to represent the ways by which we can perform tests without producing code changes in order to get a class into a test harness. A Seam Quoting the author, “A seam is a place where you can alter behaviour in your program without editing that place” Important to highlight: alter behaviour without editing . So how can we change behaviour without changing the code? We can actually do it in different ways or manners so far: Seam types Preprocessing seam : used in languages that allow preprocessing, such as C+...
Keep reading

Bulk Inserts and the Performance Holy Grial (Part I)

Hello, I've been asked to improve a part of a model class which is causing some database issues. We use PHP and Oracle, so our legacy code is built using the OCI ( Oracle Client Interface) built-in library to take advantage as much as possible of the driver speed instead of using either the CodeIgniter abstracted database class or, simply, PDO ( PDO for Oracle ). Since we have to deal with bulk transactions under high load scenarios, database access optimization is a must. Massive rows have to be inserted prior to another batch of updates on them lately. Binding parameters in advance is a way of getting a performance improvement (read more on this topic here: https://blogs.oracle.com/sql/entry/improve_sql_query_performance_by ), in addition to avoid SQL injection attacks. So, here's is a snippet of what the bulk insert method looked like before any change: class TxnUser extends CI_Model { const OPEN = 1; const CLOSED = 0; [...] // Legacy meth...
Keep reading