Rezultati pretraživanja
  1. prije 11 sati

    Can you do Git code reviews without pull requests? Find out.

  2. prije 17 sati

    How Lyft Does Code Review "[Lyft] has infused its own personality into its code review process, which has resulted in a distinct culture that works for them."

  3. prije 17 sati

    Every decision will ripple across whole team, thats why unless you are a solo dev, software is not that much "soft" as you think.. Lets merge complete solutions.

  4. prije 18 sati

    Ecco come utilizziamo Merge Request nei nostri progetti di sviluppo software per garantire la qualità del codice:

  5. prije 20 sati

    Just released a code quality review of Fastjson, an open-source project by developers at . This video explains a few performances decreasing bugs and vulnerabilities.

  6. 5. velj

    Get tips for setting up an effective Git code review workflow.

  7. 5. velj

    Our job is to make things predictable and certain, keeping general level of confidence high. All TODO comments lower those values thats why I nearly always ask to remove them.

  8. 5. velj

    Great Article "Code Review 101" by

  9. 4. velj
  10. If I got paid for every hour I waited for someone to check and merge my Pull Request, I'd be a millionaire by now.

  11. 4. velj
  12. 3. velj

    Code Reviews are evil and let's all agree with it. It's not about how much code reviews you get, but what is pattern behind it and how can we improve on it in future.

  13. 3. velj

    Common dynamics to identify in the process. - Long-running PRs - Heroing - Over-helping - Over-engagement - Just one more thing - Knowledge silos - Self-merging PRs - Ramping up

  14. 3. velj
  15. 2. velj

    Quality and code review. Would you say code review is optional, skip it when in a hurry? Or do you think it's a safety measure to prevent quality issues downstream?

  16. 31. sij

    How many lines of code inside an "if" code block do you think is too many? Please RT.

  17. 30. sij

    4+1 Code Review Tools and Linters to Help Your Team Write Better Code

  18. 30. sij

    some developers have negative ideas about the or .... i dig em✊🏾🤓... tie em to pull requests.. it's a chance for knowledge exchange about the domain, and the code and best practices for coding, and a chance to do some knowledge crunching

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.