recentpopularlog in

mcherm : debasishghosh   8

It's the familiarity model! - Ruminations of a Programmer
Sucinct code and incomprehensible code are the same thing; the difference is whether the programmer is familiar with the idiom.
programming  languagedesign  DebasishGhosh  via:DebasishGhosh 
february 2012 by mcherm
Ruminations of a Programmer: Why I don't like ActiveRecord for Domain Model Persistence
Having domain objects automatically persisted is nice. But having to extend some class to do it (ActiveRecord) is not so great. For one thing, it ties you down to just one persistence mechanism. Debasish Ghosh has a solution that's less intrusive (basically, it uses introspection).
database  DebasishGhosh  via:DebasishGhosh  programming  scala  activerecord  persistence 
february 2010 by mcherm
Your data model can speak different languages too: Ruminations of a Programmer
Some thoughts on non-traditional forms of data storage (anything other than a RDBMS), and why you might want them, especially if extreme scalability is an issue.
via:DebasishGhosh  DebasishGhosh  programming  scalability  database  modeling 
march 2009 by mcherm
Bloom Filters - optimizing network bandwidth: Ruminations of a Programmer
Another great idea: transfer a Bloom filter over the network and use it to pre-filter the data that's going to be merged together (perhaps when doing a map-reduce for instance). Then you can send a much smaller amount of data over the network to do the actual merge.
bloomfilter  programming  mapreduce  datastructures  via:DebasishGhosh  DebasishGhosh  concurrency 
march 2009 by mcherm
Ruminations of a Programmer: Design Patterns - The Cult to Blame ?
Another person responding to the "patterns are bad" meme. Debasish is close to my own position: that patterns are useful for the basics: a problem, one possible solution and a name for it; while the details of exactly how it is implemented in a particular language are less useful.
programming  patterns  DebasishGhosh 
november 2008 by mcherm
Java to Scala - Smaller Inheritance hierarchies with Structural Typing
A GREAT illustration of two good ideas in Scala: anonymous types (defined by having a certain method or methods) and implicit adapters. It demonstrates that these can avoid requiring classes to be related by inheritance when it's not wanted.
scala  languagedesign  oop  languages  DebasishGhosh 
june 2008 by mcherm

Copy this bookmark:

to read