Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cover sound programming practices #109

Open
ghost opened this issue Mar 8, 2013 · 3 comments
Open

Cover sound programming practices #109

ghost opened this issue Mar 8, 2013 · 3 comments

Comments

@ghost
Copy link

ghost commented Mar 8, 2013

This is more than just scripting/hacking to get a solution done. There's a difference in mindset and goals between writing code to automate something quickly and writing code for the business's main application.

@unpixie
Copy link
Contributor

unpixie commented Mar 8, 2013

modularity, reusable code, security (input validation for starters), supportability/readability, if you write anything that touches infrastructure... assume it may stick around for years and others will have to support it, fix it, troubleshoot problems it touches...

@miketheman
Copy link
Member

@apeiron please take a gander at the recently-merged programming 101 topic, some stuff might be covered there, some may not.

I don't think it's appropriate to rewrite a "CS fundamentals for programmers" here, but open to hearing about some of the ideas you might have in mind.

@miketheman
Copy link
Member

Bump.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants