Skip to main content

Code Retreat Cluj-Napoca - 19/05/2012

Sambata, 19.05.2012, a avut loc in Cluj-Napoca o nou sesiune de Code Retreat.Au fost aproape 9 ore de programare si fun, unde am avut parte din plin de TDD si pair programming.
Problema care am incercato sa o rezolvam de fiecare data a fost cea clasica, Game of Life (a lui Conway's). O problema simpla, care in varianta clasica nu pune nici un fel de probleme. Desii acesta a fost al doilea Code Retreat organizat, unde s-a rezolvat aceiasi problema, nu am simtit ca este ceva monoton. La fiecare runda am descoperit ceva nou, ceva care partenerul il facea diferit, de la TDD, la scurtaturi sau ceva legat de mediul de programare.
Cand incepi sa scrii teste, cel mai greu sa primul test, nu stii cum sa incepi sau mai bine zis cu ce. Care e primul test care trebui scris, a.i. sa fie consistent si nici sa nu te aberezi.
Asa cum se obisnuieste, ultima sesiune e destul mai speaciala, apar reguli mai ciudate. De data asta am ales ca sa fim intr-un mediu in care fiecare celula sa fie hexagonala (in loc de opt vecini sa aibe doar 6). Se obtine un fel de fagure, iar impreuna cu coechipierul meu din runda respectiva am reusit aproape sa terminam problema in aceasta runda. Din pacate nu a mai fost TDD, eram curiosi sa vedem daca am gasit algoritmul bun.
A fost o sambata destul de productiva. Mai jos gasiti doua poze de la acest eveniment.

Comments

  1. Apropos, o chestie legată de stilul de scris. Mare mare atenție la cratimă. Și la felul în care scrii. Este o recomandare negativă pentru tine faptul că scrii constant cu greșeli. :) Just a friendly warning.

    ReplyDelete
  2. As zice ca a fost interesant focus-ul pe TDD - desi, TDD-ul in ziua de azi e ca sexul la adolescenti - multi spun ca fac TDD, foarte putini developeri practica TDD cu adevarat, in proiecte reale (acelasi lucru se poate spune despre Scrum).

    ReplyDelete
    Replies
    1. TDD o fi ca sexul la adolescenți dar tot mi se pare masturbare intelectuală. Cînd zic asta mă refer chiar la TDD, adică Test Driven pur. No such thing. Pur și simplu e impractic să o faci.
      Cît despre Scrum, developerii ar vrea, da' nu-i lasă oamenii cu bani să-și facă de bani. Eventual, dacă se poate, sprinturi de o zi :D

      Delete
    2. [offtopic si fara legatura cu code retreat]
      Eu ma refeream un pic la altceva - daca s-ar folosi TDD macar pentru o parte din aplicatie, tot ar fi mare lucru - inca vad foarte multe proiecte unde nu exista unit teste, unde testele sunt adaugate la mult timp dupa ce un feature e terminat, proiecte la care exista mentalitatea ca un tester trebuie sa scrie integration tests (nici nu se stie ce e ala un unit test prepriuzis) - deci macar daca ar fi test-driven _development_, nu design, tot ar fi ceva..

      Legat de Scrum, problema in multe firme e ca multi developeri nici nu stiu ce e ala Scrum mai in detaliu, iar managerii zic ca fac scrum ca sa dea bine la marketing (multi high-level managers stiu despre scrum doar ceva de genul "chestia asta agile cu iteratii mai dese decat 4-5 luni si stand-up meetings").. :)

      La asta contribuie si multi 'evanghelisti' agile, care exemplifica totul cu probleme de jucarie care se preteaza la TDD, dar multi developeri raman in ceata cand e vorba sa dezvolte o aplicatie complexa in stilul asta.

      Delete
    3. din punctul meu de vedere nu exista tdd pur sau impur. exista doar tdd! dezvolti in maniera tdd sau nu. ca nu iti place sau ca nu iti iasa sau ca nu peste tot poti sa aplici e foarte diferit de "No such thing" sau "masturbare intelectuala" sau "Pur si simplu e impractic".

      Delete
    4. Vrei să-mi zici că tu practici TDD, adică scrii unit teste care să treacă prin toate branch-urile posibile ale tuturor funcțiilor?

      Delete
  3. Ma tem ca unii au promovat ideea de "TDD pur" in sensul de (technical) design al aplicatiei care ia forma doar in urma scrierii testelor, dupa refactoring, ceea ce e rar intalnit in aplicatii complexe - mai intotdeauna programatorul se gandeste un pic in avans la un oarecare technical design, chiar daca dupa aceea design-ul va evolua.

    ReplyDelete

Post a Comment

Popular posts from this blog

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...