Discover and read the best of Twitter Threads about #Refactoring
Most recents (4)
Hello hello London! 👋🏻 We’re at IET Savoy Place, London for DSS London 2022 by #YugaByteDB. It’s gonna be super interesting tech session starting at 2 pm today! Don’t miss my #Live #Tweets in this #thread! 🤩🧵
@Yugabyte #DSS22 #DistributedSQL #PraveenScience
@Yugabyte #DSS22 #DistributedSQL #PraveenScience
Yes, the setup is going on for the grand presentation of the #Tech #Track. The master is teaching the student here! #JustKidding Say hi to Julie Wise and Dave Roberts from #YugaByteDB! 👋🏻
@Yugabyte #DSS22 #DistributedSQL #PraveenScience
@Yugabyte #DSS22 #DistributedSQL #PraveenScience
We’ve got our Social Media / Content Director @rachel_pescador from #YugaByteDB here, who’s busy at work and got some cool #swag! 🤩
@Yugabyte #DSS22 #DistributedSQL #PraveenScience
@Yugabyte #DSS22 #DistributedSQL #PraveenScience
for that first iteration of the code, simple don't mean shortcut:
simple != easy
simple != hacky
simple != rushed
simple != poorly written
even the first cut, MVP, needs to be changeable, testable, clear, expressive, etc
#TDD #technicalDebt #refactoring
simple != easy
simple != hacky
simple != rushed
simple != poorly written
even the first cut, MVP, needs to be changeable, testable, clear, expressive, etc
#TDD #technicalDebt #refactoring
the "make it work" part (K.Beck) always gets mistaken to mean, hack at the code, squeeze, force-fit, finagle, the easiest and quickest thing that'll get the managers, customers, users off our back.
but we just end up on the wrong side of karma
2/3
but we just end up on the wrong side of karma
2/3
it just adds high interest technical debt, and need to refactor out:
- initial understanding, with deeper insight into the feature
- tightly coupled, low cohesion, incoherent, viscous, rigid, fragile, immobile code
#highInterestTechnicalDebt
#technicalDebt
3/3
- initial understanding, with deeper insight into the feature
- tightly coupled, low cohesion, incoherent, viscous, rigid, fragile, immobile code
#highInterestTechnicalDebt
#technicalDebt
3/3
sometimes the kind of refactoring that clears the way for easier extension, is not a refactoring toward this or that design pattern, but a refactoring to support a deeper conceptual understanding of a functional use case/ user scenario
#conceptualContours #ddDesign
#conceptualContours #ddDesign
oh you refactor refactor 😅
study and understand a user scenario or business process; then model and design their concepts
think of principles like high cohesion and low coupling, but in terms of concepts first, then classes and code mechanisms
#ddDesign #softwareDesign
think of principles like high cohesion and low coupling, but in terms of concepts first, then classes and code mechanisms
#ddDesign #softwareDesign
I'm only halfway through Bertrand Meyer's 2014 book, "Agile! The Good, the Hype and the Ugly", but it's already proven its worth as a lucid, unrestrained appraisal of #Agile principles and methodologies. Here are a few passages that resonated with me...
"#XP's insistence that [pair programming] should be the absolute rule [...] makes little sense conceptually, as it neglects the role of programmer personality (some excellent developers like to concentrate alone and will resent having to be paired) [...]"
"Starting any significant software project (anything beyond a couple of months and a couple of developers) without taking the time to write some basic document defining core requirements is professional malpractice."
