I think the current thinking is half nature and half nurture. So there is still a lot of room for self-development. There are probably half a dozen other professions I could have been good at though they lean towards the analytical. Besides, such beliefs tend to be self-limiting. Instead of “I’m no good at this”, a more fruitful approach is “What skills and knowledge do I need to acquire to master this?” Whether it’s worth the effort or if you really want to, is a different question.
Thanks for your vote of confidence. It would not be impossible. But…why do I find this interesting and not that? I think that is another side of the same question. I was never good at focusing on subjects which were not interesting.
And I did not say that genes were the whole picture, just that they seem to be a big piece of it.
Sounds reasonable. But I did make a concerted effort to get somewhere with VB, and I just did not get far with it. Some people are “polymaths”. Perhaps I could have designed mechanical devices instead of electronic ones. But somehow, software never seemed to “click” for me.
1 Like
Interesting discussion, although off-topic.
If have written Pros and cons of using a VCS (git etc.) with KiCad but it doesn’t actually prove why one should choose a vcs over some other, simpler revisioning method.
It is true that a KiCad user would need only about 1% of the features of a full blown modern VCS, and the most important features of a modern distributed system would never be used.
Personally I just find “invisible older versions” good for me. But it’s not an objective, neutral reason.
I would say that if you find the proposed reasons interesting and you have any possible reason to get familiar with a VCS, go ahead, but if you dislike the idea for starters and don’t have any other specific reason, go for a copy based system.
1 Like
What ESL means? Something like English Language. Google suggests that it is a kind of English Lessons.
It means English Second Language. That you are no native speaker.
That is it!!
It also means equivalent series inductance but I do not think that is what I intended here…if I remember correctly. (??)
I have a lot of respect for all of you who need to be multilingual for a variety of reasons. I know a few words of Spanish and also Mandarin but I am monolingual.
My first thought was Equivalent Serial Inductance 
We in Poland were compulsorily taught Russian. So there was a time when I knew Russian better than English. Even during my studies, I wrote a matrix rotation or FFT program on the basis of a Russian book on algorithms.
1 Like
I written previous post and than read it.
I’d appreciate any comments about my mistakes, but I can’t promise to fast avoid my typical mistakes. I learn such things rather slowly, very slowly.
Don’t worry about it, your writing is fine; I think of it as a little mental workout. I remember with amusement another poster’s request for a solar pastor which is readily understood from the latin origin of the word for shepherd or herdsman.
1 Like
I was going to say similar. Actually I sometimes find myself guilty of doing what I observe you doing…but I have no excuse. That is typing the wrong word when two words are pronounced similar. My only solution is careful proof-reading of what I write, but usually that only comes too late. 
When one is hungry, frites may be preferable to files. 
1 Like
Agree completely.
In fact, sometimes on this forum, I feel a little inferior being only monolingual.
1 Like
In Polish ‘Electronic shepherd’ = ‘Pastuch elektroniczny’.
But ‘ch’ you don’t read like you expect. Rather closer to single ‘h’.
1 Like
@Piotr
The definition of pastor as shepherd (or leader) of a flock has fallen into disuse outside religious groups.
Pastor, outside religion, is more generally thought of as “just a title” before a persons’ name.
When the thread asking about a solar pastor was posted, my immediate thought was “sun priest”… whatever is he writing about?
It took some time and thought and brainpower to realize “solar pastor” meant “solar powered electric fence energizer”.
Obviously, @retiredfeline , just as I, saw some humor in the differences of meanings and translations between languages.
I just stole the electronic shepherd saying and posted on twitter Thank you
great set of replies - extremely helpful …
tho - this leads me back to a few background questions I have about what the software 'expects" from Project Folders which I should ask about in a separate thread.
again, thanks all for providing such explicit details !!
1 Like
Thank you all who posted according to the op question. You convinced me to try out git for KiCad project (folder where kicad project is). I believe you are not adding other folders (like boms and orders) to the repository?
@retiredfeline (or others, it is too much noise in this thread, I may be missed some important post), could you share your open source repository to explore? I believe, long lived repository with many commits could be a good start to take best practices, not to make beginner mistakes.
As I imagine, using git in my “live” kicad project folder (What approach do you take to save revisions without going through GIT ?! - #8 by poco) could provide me a very fine grained version history. I should write my “version history” text not inside schematic sheet itself (this totally sucks when design has many subsheets, I just can’t write all history in the root sheet, I need to scroll through all sheets in resulting sch pdf just to grasp all sch changes from rev a to rev b, awfull 
) but as a commit list.
You can find my repos at https://github.com/retiredfeline
I woldn’t say my repos are good examples of long-lived projects. I usually finish off a project with one revision and leave it there. Also many of the projects there are software or firmware projects. Then too my boards are rather simple since I’m an amateur hacking for fun. But make whatever you will of them.
You can tell git to ignore certain directories and files from consideration in the repo. These are usually backup or temp files, and subdirectories that you don’t want to archive. This is done by including patterns in either .gitignore or .git/info/excludes, relative to the base directory of the repo. The difference is that normally .gitignore is also archived while .git/info/excludes isn’t so the latter is for exclusions you don’t want people to know about. I normally include the gerbers, in case somebody wants to use my boards as is.
Here’s an example of a .gitignore for some breakout boards imported from Eagle:
*-eagle-import.lib
*-eagle-import.dcm
*.kicad_pcb-bak
*.jpg
fp-info-cache
1 Like
Regarding, [quote=“BlackCoffee, post:24, topic:34189”]
Point being: A single Project Folder can contain as many PCB/Schematics as desired and all will have unique names (and, if desired, unique Netlist/etc… all properly named and labeled in the Sheet’s Legend).
[/quote]
This was very helpful. Not knowing how KiCad worked, the rules of the game, with files in the folder I would have no idea their might not be trouble working as you suggested.
While I very very VERY much like GIT for my firmware development your suggesting seams like it will give easier visibility to the versions (especially I want to keep schematics and PCBs of everything for which I have assemblies).
Thanks.
Wish someone might make a Youtube demonstrating the whole process.