professional-programming
Pycco
| professional-programming | Pycco | |
|---|---|---|
| 14 | 3 | |
| 45,308 | 840 | |
| - | 0.1% | |
| 7.9 | 0.0 | |
| 4 days ago | 11 months ago | |
| Python | Python | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
professional-programming
-
A collection of learning resources for curious software engineers
The inclusion of the perspective section: https://github.com/charlax/professional-programming?tab=read... I think is really smart. Same for personal productivity. Two things that can dramatically change how and what you end up studying and doing with your time / life.
I did a coding bootcamp and yeah the frontend knowledge they taught was useful, but I could have learned that online for free. Looking back, the far more valuable thing I learned was how to discipline myself and my time - that was the first time in my life I was truly disciplined and mindful in how I spent my time. I also got perspective I'd never seen before: there was some folks in my cohort that were in their 30s and 40s and undergoing career change, and I learned two things from them: First, don't stress too much, your life has much more flexibility than you might expect (this truth is borne out, they all have perfectly successful careers in their new lives as engineers), and second, make a great use of the time you have.
Bog-standard advice we all know, but to witness it firsthand from people living it and sharing it is different. The shared article in the github is incredible: https://www.theguardian.com/commentisfree/2020/sep/07/termin...
I often wonder why I don't see more of these sorts of articles. From watching a family member slowly die of cancer, and from reading books like "When Breath Becomes Air," I'm guessing it's some combination of exhaustion, disability, and a new set of priorities that doesn't really involve death blogging. Still, I find these kinds of writings more poignant than most things I read.
- Professional Programming – Learning resources for software engineers
-
How long did it take you to code by second nature?
Also this repo helps https://github.com/charlax/professional-programming
- Professional Programming
-
5 GitHub Repositories every Developer should know
1. Professional Programming
-
Open Source Repositories
Professional Programming. As reported, The goal of this page is to make you a more proficient developer. If you have excellent resources, you can try to open a PR and include them here. But in any csae, I wanted to include this because it seems super interesting.
- These GitHub repositories contain so much knowledge you can use to become a better developer.
- Professional-programming: A collection of full-stack resources for programmers
Pycco
- Pycco – quick-and-dirty, hundred-line-long, literate-programming docu generator
- Alternative to Pygments
-
Lisp.py
Thanks for the link! I think in that case it was made with https://pycco-docs.github.io/pycco/
What are some alternatives?
cs-video-courses - List of Computer Science courses with video lectures.
sphinx - The Sphinx documentation generator
pck3r - This program created for novice in linux and can handle almost things in ubuntu and all distributions based on debian(package manager : "apt")...
MkDocs - Project documentation with Markdown.
Basic-Algorithms - Basic algorithms and data structures written in different programming languages
pdoc - API Documentation for Python Projects
dexy
Python Cheatsheet - All-inclusive Python cheatsheet
every-programmer-should-know - A collection of (mostly) technical things every software developer should know about
wtfpython - What the f*ck Python? 😱
rdm - Our regulatory documentation manager. Streamlines 62304, 14971, and 510(k) documentation for software projects.
cheat.sh - the only cheat sheet you need