Professional programming resources(github.com)
github.com
Professional programming resources
https://github.com/charlax/professional-programming
26 comments
This resources list is sufficiently far away from a list of serious references (at least for the areas I am best versed, database) as to not even qualify as introductory.
Consider this entry:
Safe Operations For High Volume PostgreSQL -- (this is for PostgreSQL but works great for other db as well).
The editorial comment couldn't be more wrong in it's fundamental assumption as the article discusses implementation specific limitations of PostgreSQL and their implementation specific workarounds. This isn't on par with reading, for example, Oracle's SAME methodology (https://www.oracle.com/technetwork/database/performance/opt-...) which might be generalizable to other databases since the paper deals as much with storage in general as it does how Oracle makes use of that storage.
I would be wary of spending more time on this list based on the overall quality I've seen in this area.
Consider this entry:
Safe Operations For High Volume PostgreSQL -- (this is for PostgreSQL but works great for other db as well).
The editorial comment couldn't be more wrong in it's fundamental assumption as the article discusses implementation specific limitations of PostgreSQL and their implementation specific workarounds. This isn't on par with reading, for example, Oracle's SAME methodology (https://www.oracle.com/technetwork/database/performance/opt-...) which might be generalizable to other databases since the paper deals as much with storage in general as it does how Oracle makes use of that storage.
I would be wary of spending more time on this list based on the overall quality I've seen in this area.
1. The Psychology of Computer Programming, by Gerald Weinberg.
Yes, from 1971. The best discussion of professional programming and the difference with amateur programming is just one of the important topics.
2. Essentials Programming Languages by Daniel Friedman and Mitchell Wand.
The other side of learning programming languages. In addition to learning specific languages, it's useful to see what some basic features of proglangs are and how they work.
Yes, from 1971. The best discussion of professional programming and the difference with amateur programming is just one of the important topics.
2. Essentials Programming Languages by Daniel Friedman and Mitchell Wand.
The other side of learning programming languages. In addition to learning specific languages, it's useful to see what some basic features of proglangs are and how they work.
One of the problems that I feel we face these days is the challenge of discovery. Sites like HN, Reddit, Pinterest help to some degree, but I can't help but feel that they're just scatter-shot.
I miss the days of web directories. I really appreciate that the programming community is creating more and more of these curated lists ("awesome" lists), but I'm disappointed that other categories aren't as popular.
Perhaps there's room for an AwesomeAwesome, someday... A Wikipedia-like curation of worthwhile resources. I doubt it's feasible once a certain critical mass is achieved, what with gaming the system or disagreements about what should or shouldn't be included. Wikipedia can at least limit conflict somewhat by saying that something is or is not factual or backed by a reputable resource. To determine what should or should not be on a curated list is a lot more difficult.
Maybe a voting system could help. Or maybe that's too easy to game.
Anyone else miss web directories?
I miss the days of web directories. I really appreciate that the programming community is creating more and more of these curated lists ("awesome" lists), but I'm disappointed that other categories aren't as popular.
Perhaps there's room for an AwesomeAwesome, someday... A Wikipedia-like curation of worthwhile resources. I doubt it's feasible once a certain critical mass is achieved, what with gaming the system or disagreements about what should or shouldn't be included. Wikipedia can at least limit conflict somewhat by saying that something is or is not factual or backed by a reputable resource. To determine what should or should not be on a curated list is a lot more difficult.
Maybe a voting system could help. Or maybe that's too easy to game.
Anyone else miss web directories?
Great list, probably can be improved by a voting page, actually github should support simple polls, i.e. visitors can suggest their favorite votes without git-clone-PR steps.
Great list !
Nice list. Appreciate it. But I see there are a few amazing software books missing from the list such as:
- Clean Code (by "Uncle Bob")) [https://www.amazon.com/Clean-Code-Handbook-Software-Craftsma...]
- Design Patterns (by "Gang of 4") [https://www.amazon.com/Design-Patterns-Elements-Reusable-Obj...]
- Introduction to Algorithms (by "CLRS") [https://www.amazon.com/Introduction-Algorithms-3rd-MIT-Press...]
- Clean Code (by "Uncle Bob")) [https://www.amazon.com/Clean-Code-Handbook-Software-Craftsma...]
- Design Patterns (by "Gang of 4") [https://www.amazon.com/Design-Patterns-Elements-Reusable-Obj...]
- Introduction to Algorithms (by "CLRS") [https://www.amazon.com/Introduction-Algorithms-3rd-MIT-Press...]
A book about the design patterns is a good idea, the original book by then the gang of 4? I disagree, IMHO this book isn't well written, now the question is: is there a better book on this topic?
Head first is a much better option IMO https://www.amazon.com/Head-First-Design-Patterns-Brain-Frie...
[deleted]
Introduction to Algorithms might not be the best thing to start with. The name is very much misleading
Glad to see I'm not the only one who thinks this - it's one of the many areas I need to look at, and saw that recommended elsewhere... took a look on Amazon and got completely intimidated! If 1000+ pages is an introduction, what does the chapter and verse look like?
(I've started reading Grokking Algorithms this week, and it's been a much better introduction - I know it's not as in depth as some other books, but I'm making good progress with it and not drowning in complexity from the get go)
(I've started reading Grokking Algorithms this week, and it's been a much better introduction - I know it's not as in depth as some other books, but I'm making good progress with it and not drowning in complexity from the get go)
Don't let its size intimidate you. Introduction to Algorithms is quite approachable and its chapters are pretty well self-contained.
Thanks - I'll keep that in mind (although I'm old and attempting to retrain, and have found lots of things more difficult than everyone else appears to!)
This is awesome! I always love seeing curated lists.
Is there a way to contribute to this list? e.g. PR, Issue?
Is there a way to contribute to this list? e.g. PR, Issue?
There are four PRs in the linked repo, all merged, it's probably an acceptable route to contribute.
Here is a looong list in a similar vein, "Best websites a programmer should visit":
https://github.com/sdmg15/Best-websites-a-programmer-should-...
https://github.com/sdmg15/Best-websites-a-programmer-should-...
> Editors & IDE
mentions only Sublime and Vim...hardly professional.
mentions only Sublime and Vim...hardly professional.
Incomplete? Biased towards a certain style of editor? Sure.
"Hardly professional"? What's not professional about either of those?
"Hardly professional"? What's not professional about either of those?
That is seems more like a personal preference list than a comprehensive list used at work. It takes 5 mins to google IDE market share, e.g. check out the results of Stack Overflow surveys.
I think you misunderstood the point of the repo, then.
Personally, I could list off the top of my head several likely candidates for the top editors and IDEs, but I don't have anything useful to say about most of them, because I don't use them. I fully expect the author is in the exact same position.
You're absolutely right that the list is not comprehensive, and it's probably the author's own personal preferences. But if he uses mostly those editors, what's he to do? Just list off a few more editors/IDEs with no links to any useful resources, when the whole point of the repo is to have actual resources you can read? How would having a header saying "IntelliJ" or "XCode" or "Visual Studio" make that list better? How would just adding a random link for some blog post about any of those help, if the list's author can't vouch for their validity?
It's overall just best to put in what you know, and leave the rest to PRs.
Personally, I could list off the top of my head several likely candidates for the top editors and IDEs, but I don't have anything useful to say about most of them, because I don't use them. I fully expect the author is in the exact same position.
You're absolutely right that the list is not comprehensive, and it's probably the author's own personal preferences. But if he uses mostly those editors, what's he to do? Just list off a few more editors/IDEs with no links to any useful resources, when the whole point of the repo is to have actual resources you can read? How would having a header saying "IntelliJ" or "XCode" or "Visual Studio" make that list better? How would just adding a random link for some blog post about any of those help, if the list's author can't vouch for their validity?
It's overall just best to put in what you know, and leave the rest to PRs.
Then again, I'm just some random dude on the internet, so what do I know.