Tuesday, February 1, 2011
Using SysCache as secondary cache in NHibernate - Lorenz Cuno Klopfenstein - Klopfenstein.net
Using SysCache as secondary cache in NHibernate - Lorenz Cuno Klopfenstein - Klopfenstein.net: "query regions: a query region is a partition of the whole cache that can keep a certain subset of the entities managed by NHibernate, using individual priorities (the likelihood that an object of that region evicts another already cached object of a lower priority region) and expiration values (the time in seconds after which an object is automatically evicted from the cache and this will be fetched again from the database)."
Tuesday, January 25, 2011
Agile Charts
Agile Charts: "What about Microsoft Project?
Software development guru Joel Spolsky puts it this way:
“The trouble with Microsoft Project is that it assumes that you want to spend a lot of time worrying about dependencies… I’ve found that with software, the dependencies are so obvious that it’s just not worth the effort to formally keep track of them.” [see also: critical path in agile projects]
Joel continues:
“Another problem with Project is that it assumes that you’re going to want to be able to press a little button and “rebalance” the schedule… For software, this just doesn’t make sense [in practice]… The bottom line is that Project is designed for building office buildings, not software.”
Joel is a former Microsoft employee, who worked on both Excel and Project. He’s not alone in his views. Chris Peters, Microsoft’s Vice President in charge of Office, also said that Microsoft Project is more appropriate for managing the design of airplanes and buildings, rather than software. [1]
- Sent using Google Toolbar"
Software development guru Joel Spolsky puts it this way:
“The trouble with Microsoft Project is that it assumes that you want to spend a lot of time worrying about dependencies… I’ve found that with software, the dependencies are so obvious that it’s just not worth the effort to formally keep track of them.” [see also: critical path in agile projects]
Joel continues:
“Another problem with Project is that it assumes that you’re going to want to be able to press a little button and “rebalance” the schedule… For software, this just doesn’t make sense [in practice]… The bottom line is that Project is designed for building office buildings, not software.”
Joel is a former Microsoft employee, who worked on both Excel and Project. He’s not alone in his views. Chris Peters, Microsoft’s Vice President in charge of Office, also said that Microsoft Project is more appropriate for managing the design of airplanes and buildings, rather than software. [1]
- Sent using Google Toolbar"
Tuesday, October 26, 2010
Moving from Subversion to Mercurial - how to adapt the workflow and staging/integration systems? - Stack Overflow
Moving from Subversion to Mercurial - how to adapt the workflow and staging/integration systems? - Stack Overflow: "We got all psyched about from from svn to hg and as the development workflow is more or less flushed out, here remains the most difficult part - staging and integration system."
Mercurial hg, am I doing it right? - Stack Overflow
Mercurial hg, am I doing it right? - Stack Overflow: "Remember, merging is coding too -- the person doing the merge is making choices about what should and shouldn't be. The QA people might be capable of it, but it's the developer's job. Also, why do it twice? The usual handoff for this is something like 'QA, pull revision 897a9d9f9a7 and test please -- the developers'. If you want to get fancy you can have a tag like 'readyforQA' that the developers move along the 'default' branch as they go (in this example they'd hg tag after their steps 3 and 5 and let QA know there's new stuff to pull.
The one piece of advice I'd give you is don't try to over-engineer the process. DVCSs lead to a sort-of haphazard way of working, that's a little scary at first, but tends to work out. YOu'll find sub-teams and pairs of folks have clones you never knew about and in the end so long as you have a few firm rules like 'nothing goes to production without first passing through QA' the rest sort of works itself out."
The one piece of advice I'd give you is don't try to over-engineer the process. DVCSs lead to a sort-of haphazard way of working, that's a little scary at first, but tends to work out. YOu'll find sub-teams and pairs of folks have clones you never knew about and in the end so long as you have a few firm rules like 'nothing goes to production without first passing through QA' the rest sort of works itself out."
Thursday, August 26, 2010
Solid principles
Check out this SlideShare Presentation:
Solid principles
View more presentations from dkandalov.
Subscribe to:
Posts (Atom)