Explore >> Select a destination
|
You are here 
|
www.miketheman.net | ||
| | | | |
avelino.run
|
|
| | | | | I constantly hear people saying that to contribute to an Open Source project you need to be able to program very well, have a lot of knowledge, be able to handle code criticism, etc. I see the above statements as excuses and focus in the wrong place. In the last few months, I haven't had as much time to contribute to open source projects as I like (writing code), but that didn't stop me from contributing. Actually, the lack of priority (not lack of time) has made me contribute by reporting problems that I run into in the projects/software I use in my day-to-day life and this has been more work than writing code with a defined specification (issue that someone invested time detailing). | |
| | | | |
takeonrules.com
|
|
| | | | | The following article is specific to Software Services by Scientist.com ?? . While the specifics are for my day job, the general approach is something I find useful to share. In this playbook article we'll list the steps to take when upgrading. We'll also mention some of our conventions and how to build a checklist from those conventions. | |
| | | | |
ukiahsmith.com
|
|
| | | | | Go 1.11 introduced a new concept of Modules which brings first class support for managing dependency versions and enabling reproducible builds. Go previously had no notion of dependency versions, and it has been a long and arduous road to get where we are now. Modules do not just copy the style of other programming language's dependency tools, rather it introduces a few slightly different concepts intended to enable programming in the large. | |
| | | | |
sethmlarson.dev
|
|
| | | Python, open source, and the internet | ||
