4 ms·

Whether you recognize it or not, you face a choice between: a) keeping your name on said repo, and b) substantially higher growth rate. When people do things fo

Whether you recognize it or not, you face a choice between: a) keeping your name on said repo, and b) substantially higher growth rate. When people do things for free, they don't do it so someone else can put their name on it. (It's irrelevant whether this was your "intention" -- I'm not saying, I'm just saying.)

goldenkey 13y ago
Well he also puts his name in the insertion sort file at the top named, wait for it.. "kennyledet_insertion_sort.c": // Kendrick Ledet 2013 As if git blame wasn't enough, let's stick our full names in every file prefixed with our name. People have got to know that I'm the one who created this sample algo code!! <waits for applause>
- kennyledet 13y ago
  > let's stick our full names in every file prefixed with our name. People have got to know that I'm the one who created this sample algo code!! I'm not exactly sure what you're getting at here, or why you're trying to be funny in what I wanted to be a relatively serious affair. The implementation as well as the comment were both written way before I even had the idea for this repository. Also, 1. Kennyledet just so happens to be my Github name. The full name comment at the top is not a listed convention. 2. The convention of putting your github username is actually a feature. Do you suggest just clumping everything together under one algo folder, where filenames could be similar and possibly conflict? :) Again, it's not about people discovering me, it's about making this popular on Github so more practicing programmers can share, discuss and learn new algorithms. Please think more logically here.. P.S., I know what git blame is. Don't try to undermine the point here. I wanted the file structure to be flat and adhere to those conventions for more reasons than you probably think I have. You're welcome to start your own repo and try and get it as active as this one has within 2 hours...Then I'll close mine. Thanks.
  - goldenkey 13y ago
    I'm gonna get on that repo, because that's what my criticism infers, creating my own repo. Yes.
kennyledet 13y ago
I don't think you read far enough in the README to see the conventions man. Please don't get the wrong idea. Clearly it's not about me. If you have a suggestion to keep things more "unbranded", let me know. I could just put it under an organization.

goldenkey 13y ago

Well he also puts his name in the insertion sort file at the top named, wait for it.. "kennyledet_insertion_sort.c": // Kendrick Ledet 2013 As if git blame wasn't enough, let's stick our full names in every file prefixed with our name. People have got to know that I'm the one who created this sample algo code!! <waits for applause>

kennyledet 13y ago
> let's stick our full names in every file prefixed with our name. People have got to know that I'm the one who created this sample algo code!! I'm not exactly sure what you're getting at here, or why you're trying to be funny in what I wanted to be a relatively serious affair. The implementation as well as the comment were both written way before I even had the idea for this repository. Also, 1. Kennyledet just so happens to be my Github name. The full name comment at the top is not a listed convention. 2. The convention of putting your github username is actually a feature. Do you suggest just clumping everything together under one algo folder, where filenames could be similar and possibly conflict? :) Again, it's not about people discovering me, it's about making this popular on Github so more practicing programmers can share, discuss and learn new algorithms. Please think more logically here.. P.S., I know what git blame is. Don't try to undermine the point here. I wanted the file structure to be flat and adhere to those conventions for more reasons than you probably think I have. You're welcome to start your own repo and try and get it as active as this one has within 2 hours...Then I'll close mine. Thanks.
- goldenkey 13y ago
  I'm gonna get on that repo, because that's what my criticism infers, creating my own repo. Yes.

kennyledet 13y ago

I don't think you read far enough in the README to see the conventions man. Please don't get the wrong idea. Clearly it's not about me. If you have a suggestion to keep things more "unbranded", let me know. I could just put it under an organization.