BLUE
Bbrow.codafofo.dev

É bem chato ter que re-organizar toda a pasta DTO, né? 😩 Uma boa dica é usar um padrão de nomeação consistente e categorizar as classes por feature. Isso ajuda a manter tudo organizado e fácil de encontrar. #bolhadev #backend #DDD #CleanCode

1
NCnubecolectiva.bsky.social

The 5 Best Clean Code Books in Spanish. Los 5 Mejores Libros de Clean Code en Español. 👉 blog.nubecolectiva.com/los-5-mejore...#devs#programar#frontendDev#backendDev#desarrollodesoftware#programación#100DaysOfCode#worldcode#developerlife#libros#cleancode#códigolimpio

Los 5 Mejores Libros de Clean Code en Español.
0
Hhanan.my.id

i just read about the #cleancode#programming#machine." is it true?

0
DDddoomen.bsky.social

One of the challenges in my job as a consultant (typically in the role of #LeadDeveloper#SoftwareArchitect#TestDrivenDevelopment#CleanCode#DRY, and...

1
GZgilzilberfeld.bsky.social

Anybody can write clean code on the first day, in a new code base. www.everydayunittesting.com/courses/clea...#cleancode#refactoring#software#solid#legacycode

0

If your unit tests are expensive to maintain, you can make your situation better by following this advice: www.petrikainulainen.net/programming/...#cleantests#cleancode#unittests

0
CBselmaohneh.bsky.social

Retries are crucial when working with actual hardware. While the naive implementation with loops can work fine, it often clutters the solution due to repeated duplication. Implementing policies is an effective way to clean up this mess. www.cellos.blog/how-to-imple...#software#cleancode#polly

How to implement Retries without Cluttering your Code
How to implement Retries without Cluttering your Code

Imperfection One important lesson I learned working as a software engineer in the production industry for many years:\nSome things don’t work on the first try.\nThe real-world hardware and correspondi...

0
DDddoomen.bsky.social

...looks like it was written by someone who cares. How do you tell? Just ask your colleagues... So, what do you do to write code that _doesn't_ need an explanation? #lessonslearned#softwaredevelopment#bestpractices#cleancode#coding#maintainability

0