Articles tagged “refactoring”

• Refactoring It is not un­usu­al to find a piece of code which has se­vere is­sues and can­not be main­tained as is. It can ac­tu­al­ly come from a less ex­pe­ri­enced col­league, a low qual­i­ty in­ter­net re­source, or even… your­self. In all those cas­es, the code re­quires…
  refactoring 12
• Comments classification This is a bad com­ment: int i = 0; i + 1; // adding 1 to i should work but dont work i dont know why!!!! print(i);For every good com­ment, I've seen hun­dreds of bad com­ments. They harm the code base and give the wrong im­pres­sion to the au­thor that he…
  quality 36 refactoring 12 featured 8
• Code duplication Be­gin­ners' code is al­ways an amaz­ing op­por­tu­ni­ty to re­move code du­pli­ca­tion, as well as ex­plain what code du­pli­ca­tion is to the orig­i­nal au­thor. I was re­view­ing a few thou­sand LOC, so I thought this is an op­por­tu­ni­ty to post an ex­am­ple and to show…
  refactoring 12
• Extensibility When mod­i­fy­ing a sys­tem (such as adding fea­tures), one should be con­cerned about the abil­i­ty of the sys­tem to be mod­i­fied. This im­plies the pres­ence of two ex­ten­si­bil­i­ty as­pects: ar­chi­tec­tur­al and qual­i­ty-cen­tered. I be­lieve it is es­sen­tial to…
  refactoring 12
• Aren't we misusing YAGNI too often? OK, I get it, I'm over-think­ing and over-en­gi­neer­ing this app. I should KISS, be­cause YAG­NI. Great. I should not at­tempt to solve prob­lems I don't have. I should not at­tempt to solve prob­lems I don't have. Or should I? De­vel­op­ment is filled with…
  refactoring 12 rant 34 short 50
• Simplifying systems by adding proper abstractions The orig­i­nal draft of Solange pro­ject de­fined a no­tion of pro­file and in­stance. Ac­cord­ing to the to­day's doc­u­men­ta­tion (re­vi­sion 1234): A pro­file is a gener­ic de­scrip­tion of a ma­chine, i.e. a set of con­fig­u­ra­tion items and op­er­a­tions which de­fine a…
  devops 2 short 50 refactoring 12
• Micro-services in a context of high complexity and low code quality One of the most prob­lem­at­ic things of a soft­ware de­vel­op­er is how to han­dle the in­creas­ing com­plex­i­ty of a giv­en code base and the de­creas­ing qual­i­ty of it. Code which, when orig­i­nal­ly writ­ten, was read­able and un­der­stand­able, looks com­plete­ly scary…
  short 50 productivity 36 quality 36 refactoring 12
• The greatness of TDD illustrated Dur­ing an in­ter­view, I was asked to solve the fol­low­ing prob­lem: A val­i­da­tion func­tion takes as in­put a string con­tain­ing paren­the­sis and square brack­ets. It should re­turn true if the clos­ing paren­the­sis and brack­ets are match­ing the open­ing ones, or…
  featured 8 refactoring 12 unit-testing 6
• Take risks, fail fast In many soft­ware de­vel­op­ment teams, the source code is sa­cred. Its sa­cred­ness is caused by two fac­tors: The code is the ul­ti­mate ex­pres­sion of the in­tel­lec­tu­al work of the de­vel­op­ers. If you have any­thing against the code, it means that you're…
  productivity 36 quality 36 refactoring 12 rant 34 requirements 3
• Unit testing methods which are calling static methods Dis­claimer: the ar­ti­cle be­low talks about meth­ods call­ing pub­lic sta­t­ic meth­ods from oth­er class­es. This ex­cludes the calls to pri­vate sta­t­ic meth­ods. Re­cent­ly, I wrote a rather un­pop­u­lar an­swer on Stack Ex­change about sta­t­ic meth­ods in a con­text of…
  rant 34 refactoring 12 unit-testing 6 design 2
• YAGNI principle in action Dis­cussing YAG­NI with col­leagues, I of­ten find my­self in a sit­u­a­tion where they give me a con­crete ex­am­ple where they were very hap­py to think about a giv­en fea­ture or as­pect be­fore it was re­al­ly need­ed. As those dis­cus­sions al­ways fol­low the same…
  rant 34 productivity 36 quality 36 refactoring 12 agile 10
• Trimming strings Reg­u­lar­ly, I find in­ter­est­ing ques­tions on Stack Over­flow, that look ba­sic at the first sight, but ap­pear to be not that sim­ple af­ter all. To­day, it was a ques­tion on the Russ­ian ver­sion of Stack…
  refactoring 12 short 50 javascript 3