Skip to main content

Close
Get the best research tool on the web today,and free!
Connect with people with common interests!
Play Webslides

Tristan Rivoallan's Bookmarks tagged bestpractices   View Popular

You are here: Diigo Home > Tristan Rivoallan's Bookmarks

Expand All 1 - 9 of 9

Ten Commandments of Egoless Programming

What we need is a set of rules or guidelines to help developers keep themselves (their egos, actually) separate from their code. Hence our Ten Commandments for Egoless Programming, which you can also download in handy "stone tablet" format:

Tags: dev, bestpractices, clevermarks on 2008-06-16 -All Annotations (0) -About

more fromarticles.techrepublic.com.com

Conflict

Conflict is an open source project composed of two parts: Conflict clients and a Conflict server. A Conflict client is a transparent process running on the workstation of each developer. It stays in the background, reporting local file system changes to the Conflict server. When the Conflict server detects a conflict between two or more developers, each developer is notified. The Conflict project improves feedback and communication while encouraging developers to check in code frequently.

Tags: dev, tools, scm, bestpractices, clevermarks on 2008-05-30 and saved by2 people -All Annotations (0) -About

more fromconflict.sourceforge.net

Ben Ramsey » Blog Archive » HTTP Status: 100 Continue

The 100 Continue status code is an informational response that tells the client application it can continue sending the request. In short, the client can make an abbreviated request of the service to check whether or not it should continue making the full request. The service can then respond either “yes” (100 Continue) or “no” (417 Expectation Failed) with an explanation of why not. In RESTful Web Services, Richardson and Ruby refer to this as a “look-before-you-leap” (LBYL) request.

Tags: web services, dev, clevermarks, rest, bestpractices on 2008-04-23 -All Annotations (0) -About

more frombenramsey.com

Developing an accessible slider | Filament Group, Inc.

The solution we devised is based on the core principle of progressive enhancement: start with basic, functional markup and then layer on complexity, if supported. In most cases, coding for progressive enhancement allows us to build a single code base for both the basic and enhanced versions; we then apply additional CSS and Javascript to create the richer experience for capable browsers. But when we're developing the UI for a web application and creating widgets that capture data, we're often starting with form element markup that doesn't readily cooperate with CSS, or that doesn't have all the moving pieces necessary to create a more complex widget.

Tags: dev, tools, javascript, accessibility, bestpractices, clevermarks on 2008-04-17 and saved by5 people -All Annotations (0) -About

more fromwww.filamentgroup.com

Overview — Phusion Passenger (a.k.a. mod_rails)

Phusion Passenger — a.k.a. mod_rails — makes deployment of applications built on the revolutionary Ruby on Rails web framework a breeze. It follows the usual Ruby on Rails conventions, such as “Don’t-Repeat-Yourself”.

Tags: dev, rails, apache, tools, exploitation, bestpractices, clevermarks on 2008-04-16 and saved by2 people -All Annotations (0) -About

more fromwww.modrails.com

hartija - Google Code

To solve this problem I decided to make universal Cascading Style Sheets for web printing by uniting all best CSS printing practises into one.

Tags: dev, css, tools, bestpractices, clevermarks on 2008-04-16 and saved by17 people -All Annotations (0) -About

more fromcode.google.com

Mark's stream of verbiage: Improve reliability and maintainability by using stateless connections

MySQL application developers have some problems with connection state. There is a lot of state which can be used associated with a single connection

* Transactions (autocommit, uncommitted work, when a transaction was started, isolation level)
* Temporary tables
* Session variables which affect behaviour
* Other session variables

If you can avoid all of these, then you can benefit from transparent auto-reconnection and transparent connection reuse / pooling etc.

Tags: dev, mysql, documentation, clevermarks, bestpractices on 2008-04-14 -All Annotations (0) -About

more frommarksverbiage.blogspot.com

1 - 9 of 9
List 20 50 100

Notation: * = Private bookmark and comment| = Clipping [?] | = Public highlight [?]