saturnflyer

9 ms·

1. 31.▲
   Simplifying JS function arguments for recursion with this(saturnflyer.com)

   1 points by saturnflyer 14y ago|0 comments
2. 32.▲
   Ruby delegate.rb secrets(saturnflyer.com)

   32 points by saturnflyer 14y ago|2 comments
3. 33.▲
   by saturnflyer 14y ago

   Code Triage is great! I hope this gets more attention and signups.
4. 34.▲
   Automated web testing is hard(arrgyle.com)

   1 points by saturnflyer 14y ago|1 comments
5. 35.▲
   by saturnflyer 14y ago

   The article is about writing better code. My guess is that the PHP developers who do want to write better code would probably take the advice. Is your point that nobody should ever suggest that PHP developers write better code?
6. 36.▲
   by saturnflyer 14y ago

   He says: "Working with others to get patches accepted and bugs closed is a crucial skill in writing good code" This article does not tell people to patch Apache. The point, as for as I can tell, is to explore the projects you use so you can
7. 37.▲
   by saturnflyer 14y ago

   does that make this a bad idea?
8. 38.▲
   Cascade - custom design toolkits for startups(cascade.io)

   15 points by saturnflyer 14y ago|4 comments
9. 39.▲
   by saturnflyer 14y ago

   I suspect buying the book might yield some info like that.
10. 40.▲
    by saturnflyer 14y ago

    I'm glad to see this here. I've been a beta user and it's really helped me get a good view of how far into the future money will take me.
11. 41.▲
    by saturnflyer 14y ago

    Thanks! There was a signup form there originally, now it's a link to my main page about the book at http://clean-ruby.com
12. 42.▲
    by saturnflyer 14y ago

    I actually have customers on that product. But they're unfocused and unrelated. How do you add features when the customer needs aren't clear? You don't. You just kill it.
13. 43.▲
    by saturnflyer 14y ago

    This is why I made the point about killing my other "product". I had nowhere to go with it. Perhaps I didn't say it well enough, but my initial plan was to build something but the problem wasn't marketing, it was that nobody wanted it. My b
14. 44.▲
    by saturnflyer 14y ago

    Thanks! I didn't anticipate this kind of traffic. I'm working on it.
15. 45.▲
    by saturnflyer 14y ago

    Less than an hour of billing and they've got new techniques and better understanding of application architecture. It's also the answer to life the universe and everything.
16. 46.▲
    by saturnflyer 14y ago

    This is a really good question. I actually avoided recording this because I didn't want to depress myself during the writing. I spent a LOT of time on this. It does, however, come from real-world work. My client projects have been successfu
17. 47.▲
    by saturnflyer 14y ago

    Thanks. It's hard work, for sure, but all the knowledge and experience behind it is there. Impostor syndrome must be overcome.
18. 48.▲
    by saturnflyer 14y ago

    good point. I'll verify the citation and update it.
19. 49.▲
    by saturnflyer 14y ago

    Thanks for clarifying. I had most of it written before posting and had forgotten the code samples. My copy of Design Patterns is packed up for a move. I've update it to refer to C++. Actually, people have visited, but few have stayed to rea
20. 50.▲
    by saturnflyer 14y ago

    I'm planning to follow up in another post, but Gunther Kniesel coined the term "consultation" ( http://javalab.cs.uni-bonn.de/research/darwin/delegation.htm... ) and I've used a generic "attendant" term to refer to the other object. Here's
21. 51.▲
    by saturnflyer 14y ago

    I never said delegation should be redefined. In fact I'm pointing out that the GoF did the redefining. In the history of Object-oriented programming "delegation" means what it was described to be. I never said that any particular implemen
22. 52.▲
    by saturnflyer 14y ago

    In programming terms, he did. I appreciate that it is an English language word and was initially what I thought it meant. But when he applied the term he meant it specifically. Otherwise, we already have a term for this: forwarding. So why
23. 53.▲
    by saturnflyer 14y ago

    Lieberman invented this term. It did not exist prior to his work. I have confirmed this with Lieberman himself as well as Jim Coplien and David Ungar. The Design Patterns book sought to clarify our language yet it has this error. I'm seekin
24. 54.▲
    by saturnflyer 14y ago

    I'm the author. I'm not redefining delegation. I'm pointing out that the Gang of Four, who cited Henry Lieberman who created the term, described it incorrectly. You can read the citations in the Design Patterns book and see exactly what the
25. 55.▲
    Deep dive into Rails/Rack parameter parsing(codefol.io)

    1 points by saturnflyer 14y ago|0 comments
26. 56.▲
    Functional Programming for the Object-Oriented Programmer by Brian Marick(leanpub.com)

    80 points by saturnflyer 14y ago|28 comments
27. 57.▲
    Striving for Civility in the Ruby and Rails Community(richkilmer.blogs.com)

    1 points by saturnflyer 14y ago|0 comments
28. 58.▲
    by saturnflyer 14y ago

    Really!? So PHP simplifies all this for you, huh?
29. 59.▲
    How To Preserve Idioms In Ruby Subclassing(saturnflyer.com)

    1 points by saturnflyer 15y ago|0 comments
30. 60.▲
    by saturnflyer 15y ago

    I had the benefit of working with rpwilcox in one of the trenches where I know I learned a lot. Very interested to read about his other experiences and learn more.