Javier Neira (atreyu_bbb)'s Public Profile in the Diigo Community

I am interested in functional programming,artificial intelligence,history,philosophy,rock'n'roll.

Member since Feb 03, 2009, follows 4 people, 3 public groups, 2128 public bookmarks (2132 total).

More »

Tags

Recent Tags:	clojure(0), haskell(0), example(0), reference(0), code(0), java(0), programming(0), spanish(0), javascript(0), groovy(0), snippet(0), google(0), library(0), howto(0), review(0), go(0), goodness(0), analysis(0), lisp(0)
Top Tags:	clojure(368), java(338), programming(288), tutorial(225), reference(196), webdev(121), javascript(115), j2ee(114), analysis(111), ibm(108)

More »

Recent Bookmarks and Annotations

Don’t Delete – Just Don’t on 2009-11-20
- some important business semantics missing.
- As developers discuss the pertinence of using an IsDeleted column in the database to mark deletion, and the way this relates to reporting and auditing concerns is weighed, the core domain concepts rarely get a mention.
- 4 more annotations...
- - Should all previous orders containing that item just disappear?
  - We’ve been exposing users to entity-based interfaces with “create, read, update, delete” semantics in them for so long that they have started presenting us requirements using that same language, even though it’s an extremely poor fit.
  - his intent is to discontinue the product – not to delete it in any technical sense of the word.
  - Orders aren’t deleted – they’re cancelled. There may also be fees incurred if the order is canceled too late.
    
    Employees aren’t deleted – they’re fired (or possibly retired). A compensation package often needs to be handled.
    
    Jobs aren’t deleted – they’re filled (or their requisition is revoked).
Code, Coffee : weblog, Beta - "CRUD's Not The Answer" on 2009-11-20
- that deletion is rarely, if ever, a valid business state and
  that care should be taken in dealing with it.
- The idea
  that you can annotate a few entity classes and suddenly you have a
  model and business logic all taken care.
- 15 more annotations...
- - It's
    now common to expose EntityManagers to the web tier
  - Objects in a system have state that has dependencies.
  - A lot
    of this stems from the "active objects" or "naked objects" pattern,
    where objects are open books whose state can be mutated on the UI tier
    directly and those changes propagated directly. We tell ourselves that
    we can apply Hibernate validations (or validations in any other ORM
    framework) and that we'll guarantee valid business constraints thus,
    but it rarely works out that way.
  - We tell ourselves that
    we can apply Hibernate validations (or validations in any other ORM
    framework) and that we'll guarantee valid business constraints thus,
    but it rarely works out that way.
  - Prescribing the valid creation and
    destruction of an object is critical.
  - People "forget" how an object is
    created, or destroyed.
  - People "forget" how an object is
    created, or destroyed. They forget details.
  - Plus, as business evolves, object creation is often only part and
    parcel with a larger process. If a new customer is added to a
    database, and nobody does anything with it, did it really get added?
  - but the act of instantiating a Customer object
    and then issuing entityManager.persist( customer ) will
    rarely, if ever, be enough.
  - I've seen many projects
    build their models using only a GenericDao<T>
    variant. This is dangerous. Transitions from one state to another
    for an entity can often cost money.
  - I've seen many projects
    build their models using only a GenericDao<T>
    variant. This is dangerous
  - While the services approach isn't exactly code-generation
    friendly, it can pay off in the long run.
  - It's
    easier to build services that express every dependency as a method
    parameter.
  - There are several reasons why this works out.
  - In these methods, you can do sanity checks,
    care for business cases, handle the state of the various objects and
    not worry about having a transactional resource like an EntityManager or Hibernate Session open in the client thread
Comet - Wikipedia, la enciclopedia libre on 2009-11-20
- Dojo es el primer framework que implementa a Comet.
Ajaxian » Full Frontal ‘09: Simon Willison on Server-Side Javascript and Node.js on 2009-11-20
- The conventional model is straightforward request-response, where the server tries to respond and disconnect as quickly as possible. But … there’s also the event loop model. As in Comet; it’s generally considered to be more efficient, so why do web developers avoid it? Simon says traditional server-side languages aren’t designed to deal with event-driven programming. It’s more like “do A, do B, do C, exit”. Javascript, on the other hand, is well suited to do callback-driven event programming.
El sistemas operativo de Google y el regreso del terminal tonto | Error500 on 2009-11-20
Diario de Programación » Blog Archive » Sobre constructores, atributos y herencias. on 2009-11-20
Arragonán » Blog Archive » Testeando respuestas JSON con Grails on 2009-11-20
Real World Haskell on 2009-11-19
InfoQ: Clojars and Leiningen Automate Library and Dependency Management for Clojure on 2009-11-19
coatl's rubymacros at master - GitHub on 2009-11-19

More »

Bookmark Lists

More »

Groups

clojure-dev

17 members, 517 items

Group for developers interested in Clojure, and functional programming in general
Haskell

9 members, 61 items
javascript

69 members, 325 items