Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1etYP9-0005iv-9Z for pgadmin-hackers@arkaria.postgresql.org; Wed, 07 Mar 2018 12:42:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1etYP8-0002DQ-30 for pgadmin-hackers@arkaria.postgresql.org; Wed, 07 Mar 2018 12:42:46 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1etYP7-0002DG-Pz for pgadmin-hackers@lists.postgresql.org; Wed, 07 Mar 2018 12:42:45 +0000 Received: from mail-wr0-x242.google.com ([2a00:1450:400c:c0c::242]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1etYP4-0005sK-SO for pgadmin-hackers@postgresql.org; Wed, 07 Mar 2018 12:42:44 +0000 Received: by mail-wr0-x242.google.com with SMTP id o76so2020082wrb.7 for ; Wed, 07 Mar 2018 04:42:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=qkG1sHiqUzwdwedlnheQDcG+Oj8Probfp3cJsGC8QJg=; b=opbOmBsgix01Fg64omSCkMS51Z8F56HtAMs+iBQKXMmoXvjFjPQqxZKoniCNyTLqIx HX2ENXb06VwzAONFrfpRLVLUQgwX17Gcu1pB9JFX2vMIXqy9ROR6PaISzKAbm5Qz5ZaH Jh6lwbfAH3gpT5yYBDJ1vk2I+Wh6M3sr3X19QkPnm2VgOIrVrrsUj/ZkL8jUQqbT9ocn WaGxz6mW/VEBXxJ3pqeOTTrUlCUzE5Xmo4S7ekdlSaYpumKTnt4G2OO44enfZ3jwa0VO +Tf3kD+N0u34MC2LIjMR+iOMfBiK3GROLQVz1wyIwop41dbRhK94+sQJ30bY9Yd4VNLS WkzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=qkG1sHiqUzwdwedlnheQDcG+Oj8Probfp3cJsGC8QJg=; b=Sbjy/L1gpVDxuCYTzdnozuuP3DuyuBQG/O3DQVnwpbBl8b4gyXzdGm8r2/+kjaKJGs /EyHiw1JLy9tept4KeWrLs5YcsCAFT6vftXyTQHM7gVSoKIDKnm3ALaI4JCR3JaJM5BU ZMYXyMUUFO61sbwQbulK64/yU9gBfquV2zGXEe6sx/mTPbdBF3iGc3N0Gwrhs/amWfqE bi7R9gLHtyx5j10mjaG1WtqqTovAyBYIr7IrHxA6Yo29KCTrqp7onBZHsxk6B+9QTFtE Tqhjn1zfYRZHqxGLsvYx7ore/i9GDMpWTmUF0mMuQHJerzIEutExSsXgjVnBqlB137Ms pYSw== X-Gm-Message-State: APf1xPCjDvx0r/gfUi3LzkQU0IzToA4KdtNRPgDCexi+Q4uBo2GBKBxR q8JUvIuM1iw4epItTscD14OhA8dWpI9qZVKGxzs8VA== X-Google-Smtp-Source: AG47ELvpfst6rcHQmK2JEsdKEgJeMO+uXTbQ2dS6uxDYSFXx6s1K1Q33uPZQenUXgbAxELiolqBgsvGdtmbKKqQ0Zh8= X-Received: by 10.223.184.230 with SMTP id c35mr17860306wrg.190.1520426561042; Wed, 07 Mar 2018 04:42:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.109.7 with HTTP; Wed, 7 Mar 2018 04:42:40 -0800 (PST) In-Reply-To: References: From: Dave Page Date: Wed, 7 Mar 2018 12:42:40 +0000 Message-ID: Subject: Re: [pgAdmin4][RM#2989] To fix the issue in Table node To: Joao De Almeida Pereira Cc: Murtuza Zabuawala , pgadmin-hackers Content-Type: multipart/alternative; boundary="f403045fab6c141a290566d1e567" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --f403045fab6c141a290566d1e567 Content-Type: text/plain; charset="UTF-8" Hi On Tue, Mar 6, 2018 at 4:06 PM, Joao De Almeida Pereira < jdealmeidapereira@pivotal.io> wrote: > Hi Murtuza, > > The code change works, and I passed the patches through our pipeline and > everything is green. > Personally I would love this bug fixes to have refactored the function > into smaller chunk and made it more readable so that the next time someone > need to check out a problem in the same area it is easier. I understand > that without a good test coverage it is hard to have confidence while > refactoring, but we need to start somewhere. > Are you planning to look into this Murtuza? > > @Hackers > Here is a video that I saw some time ago about refactoring existing code > and code complexity that is very interesting > https://www.youtube.com/watch?v=8bZh5LMaSmE > In this video Sandi Metz does the Gilded Rose Kata in a talk in RailsConf > 2014, and with it tries to demonstrate that code can be refactored and with > that it make the code much more simpler. But the journey is not always > simple and the complexity will increase before it get simpler. It is a good > example of something that we can try with our code. > Nice! -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company --f403045fab6c141a290566d1e567 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi

On Tue, Mar 6, 2018 at 4:06 PM, Joao De Almeida Pereira <= jdealmeidapereira@pivotal.io> wrote:
Hi Murtuza,

The code change w= orks, and I passed the patches through our pipeline and everything is green= .
Personally I would love this bug fixes to have refactored the f= unction into smaller chunk and made it more readable so that the next time = someone need to check out a problem in the same area it is easier. I unders= tand that without a good test coverage it is hard to have confidence while = refactoring, but we need to start somewhere.
<= br>
Are you planning to look into this Murtuza?
=C2=A0<= /div>

@H= ackers
Here is a video that I saw some time ago about refactoring= existing code and code complexity that is very interesting
In this vi= deo Sandi Metz does the Gilded Rose Kata in a talk in RailsConf 2014, and w= ith it tries to demonstrate that code can be refactored and with that it ma= ke the code much more simpler. But the journey is not always simple and the= complexity will increase before it get simpler. It is a good example of so= mething that we can try with our code.

Nice!=C2=A0

--
--f403045fab6c141a290566d1e567--