While developing a new project is like rolling on a green field for you, maintaining it is a potential dark twisted nightmare for someone else. Here's a list of guidelines we've found, written and gathered that (we think) works really well with most JavaScript projects here at hive. If you want to share a best practice, or think one of these guidelines should be removed, feel free to share it with us.
Found from: http://javascriptweekly.com
"RSJS makes JavaScript easy to maintain in a typical web application. It’s written for the typical conventional web app in mind: a collection of HTML pages that occasionally need a bit of JavaScript to make things work."
Anti-patterns addressed:
In a nutshell:
Some practical tips:
<meta>
tags:
function getMeta (name) {
return $('meta[property=' + JSON.stringify(name) + ']').attr('content')
}
Upsource provides a unified friendly UI for exploring and monitoring all your Git, GitHub, Mercurial, Perforce and/or Subversion repositories from a central location.,Search commit history by commit message, commit ID, author, reviewer, branch, git tag, time span, filename, or path.,Upsource supports creating, reviewing and merging GitHub pull requests.
Combining static model checking with dynamic enforcement using the Statecall Policy Language - Madhavapeddy 2009 We know that getting distributed systems right is hard, and subtle, 'deep' bugs can lurk in both algorithms and implementations. Can we do better than informal reasoning coupled with some unit and integration tests? Evidence suggests we have to do…
You are probably not using the best solution at the moment, and guess what, that's fine.
(video of these slides available here http://fsharpforfunandprofit.com/fppatterns/) In object-oriented development, we are all familiar with design patterns su…
L'actualité du Logiciel Libre et de Linux, sur un site francophone contributif géré par une équipe bénévole par et pour des libristes enthousiastes
libfaketime modifies the system time for a single application
Ensure that all your new code is fully covered, and see coverage trends emerge. Works with any CI service. Always free for open source.
reddit: the front page of the internet
Talk about Continuous Delivery and Testing. Held at HiQ april 2014.
A tutorial to the use of the RAII idiom; a simple, eloquent and efficient way to deal with many situations where there is a risk of “leaking” memory or handles, failing to release file locks, etc.
Encore un exemple de code spaghetti : Toyota
/~colmmacc/ - An Irishman’s Fiery
"Code Reviews Are More Important Than TDD" Dr. Venkat Subramaniam Don't get me wrong: Test Driven Development is great and it helps with a lot of things: Good quality, maintainable functionality, repeatable tests and much more. We did a survey at conferences that showed us that around 70% of all developer teams are practicing some kind of…
I have a feeling too many people get it wrong so let me stress: I do enjoy jUnit a lot, thanks guys for sharing! Yet, I don’t like @Test(expected) feature of jUnit. In my TDD classes I simply teach to avoid using it. I admit the feature can potentially make few tests cleaner. However, it…
Codage en langage C