Twitter | Pretraživanje | |
Pretraživanje Osvježi
Perforce Software 13 h
Can you do Git code reviews without pull requests? Find out.
Reply Retweet Označi sa "sviđa mi se"
PullRequest 18 h
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."
Reply Retweet Označi sa "sviđa mi se"
Jakub Niewczas 18 h
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.
Reply Retweet Označi sa "sviđa mi se"
Intesys 19 h
Ecco come utilizziamo Merge Request nei nostri progetti di sviluppo software per garantire la qualità del codice:
Reply Retweet Označi sa "sviđa mi se"
Codegrip 22 h
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.
Reply Retweet Označi sa "sviđa mi se"
Perforce Software 5. velj
Get tips for setting up an effective Git code review workflow.
Reply Retweet Označi sa "sviđa mi se"
Jakub Niewczas 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.
Reply Retweet Označi sa "sviđa mi se"
Victor Catalan 5. velj
Great Article "Code Review 101" by
Reply Retweet Označi sa "sviđa mi se"
Sienna Web Designs 4. velj
Manual finds 35 in 8 enclave
Reply Retweet Označi sa "sviđa mi se"
💀🕸 .☦- raZe -☦. 🕸💀 4. velj
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.
Reply Retweet Označi sa "sviđa mi se"
Ryan Challen 4. velj
Reply Retweet Označi sa "sviđa mi se"
Satyajeet ⏩ 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.
Reply Retweet Označi sa "sviđa mi se"
Darío Macchi 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
Reply Retweet Označi sa "sviđa mi se"
Viet Hoang 3. velj
development: an example of how to get "Automated Deployment" with and "Automated Code Review" with
Reply Retweet Označi sa "sviđa mi se"
Helena Jeret-Mäe 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?
Reply Retweet Označi sa "sviđa mi se"
Brian Rogers 31. sij
How many lines of code inside an "if" code block do you think is too many? Please RT.
Reply Retweet Označi sa "sviđa mi se"
CodingSans 30. sij
4+1 Code Review Tools and Linters to Help Your Team Write Better Code
Reply Retweet Označi sa "sviđa mi se"
refactor addict 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
Reply Retweet Označi sa "sviđa mi se"