Jump to content
TrinityCore

Open Source related videos and articles


jackpoz
 Share

Recommended Posts

The sad thing is, the people who really need to take notice of this, don't realize they are the poisonous people, especially if they are the ones making a lot of commits, thinking that is all it takes to be a good contributor... Pay close attention to needing goals, and limiting the scope, which does not mean "everyone do whatever they want, willy nilly"

 

22:34 I have been saying a lot of this for years, especially at this point.

Link to comment
Share on other sites

  • 4 weeks later...
  • 2 months later...

http://blog.smartbear.com/programming/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/

 

"14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star"

 

for all the community members who are not top skilled developers and still want to help the project but don't know where to start :)

Link to comment
Share on other sites

  • 3 months later...
  • 2 months later...
  • 2 weeks later...

https://www.javacodegeeks.com/2015/07/a-few-valid-reasons-to-reject-a-bug-fix.html

Quote

Bug fixes are not features; they must be small and focused. It’s a very typical mistake for programmers to get carried away while fixing a bug and introduce some refactoring together with a fix. The result is that the patch gets rather big and difficult to understand. I’m not against refactoring; it’s a very important and positive thing for a project, but do it separately after the bug is fixed and merged.

No refactoring while fixing a bug!

 

Quote

Always fix one issue at a time — simple as that. No exceptions.

Combining several bug fixes into a single pull request is a very bad practice. No matter how simple the fix is, keep it separate from others.

  • Upvote 1
Link to comment
Share on other sites

  • 4 weeks later...
  • 1 month later...
  • 2 months later...
  • 1 month later...
  • 4 months later...
  • 2 months later...

https://medium.com/@richardeng/well-it-certainly-takes-a-lot-of-hutzpah-to-make-such-sweeping-declarations-about-software-acc6b519703f#.jw5vc0x6z

>Coding is NOT the same thing as programming. Programming is problem-solving.

>People often mistake coding for programming. They think that if they learn a programming language (such as JavaScript, Python or Ruby), they’ve learned how to program. That’s nonsense, of course. Learning a programming language without understanding how to solve a programming problem is pretty much worthless. It’s like learning Mandarin and not knowing how to express your thoughts effectively or eloquently.

>Make no mistake: problem-solving is difficult. Coding is relatively easy.

Really nice (comment about an) article that warns new developers about the long path they need to walk to be Programmers and not just Coders

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...