Comments for Adam Byrtek

Comment on Why it’s good to be lazy by Adam Byrtek - Functional programming in Python

Adam Byrtek - Functional programming in Python — Thu, 24 Apr 2008 06:30:58 +0000

[…] Update 2008-04-24: Slides are also available in English. […]

Comment on Trivial accessors and uniform access by Marcin Kaszyński

Marcin Kaszyński — Sun, 30 Mar 2008 18:12:00 +0000

There is a small bug in the Python version of Money: both getter and setter should use self._amount instead of self.amount.

What are the other problems with this approach?

Comment on Benchmarking HTTP performance by Adam Byrtek - Thinner Ruby deployment

Adam Byrtek - Thinner Ruby deployment — Mon, 10 Mar 2008 19:08:07 +0000

[…] the post on benchmarking HTTP performance I mentioned that according to my tests a cluster of Mongrels performs about 10-20% worse than the […]

Comment on Subversion Scripts for Finder by Adam Byrtek

Adam Byrtek — Wed, 27 Feb 2008 22:45:20 +0000

Thanks for your comments! I considered migrating my personal repositories to Git, but I’m quite happy with my current setup, so it’s still on my someday/maybe list. Anyway I still have to work with existing Subversion repositories, and Subversion is much more popular comparing to other version control systems, so it was a reasonable decision to prepare scripts supporting it.

Comment on Functional programming in Python by Rafał Zawadzki

Rafał Zawadzki — Wed, 27 Feb 2008 21:59:44 +0000

Ups - no comments, so - this one will be first ;)

Comment on Subversion Scripts for Finder by Jakub T

Jakub T — Tue, 26 Feb 2008 09:49:34 +0000

Since i started using git i started using version control for everything i do. Even if you don’t need dedicated server in subversion for your repository you need to first import and checkout your project that is a big PITA. In git everything is simple you just enter the work directory at the moment you decide that it’s important to have it versioned and you issue ‘git init’. Starting from that moment everything is versioned.
What is even more interesting - git is transparent and if you use subversion as your official vcs you can still use git locally to track all your small modifications and branching. Later on, using git extended options you will be able to commit all the changes to your central subversion repository. This makes the transition really smooth.

@Tomek:
I don’t know what’s the difference for end users if something is written in python/ruby/c….?

Comment on Subversion Scripts for Finder by Adam Byrtek

Adam Byrtek — Mon, 25 Feb 2008 20:57:23 +0000

@Tomek: Subversion also doesn’t need a dedicated server, it can work directly from a filesystem or through a ssh tunnel. I don’t claim that it is a better option, but certainly more popular, and there are many tools and plugins that support Subversion.

Comment on Subversion Scripts for Finder by Tomek Paczkowski

Tomek Paczkowski — Mon, 25 Feb 2008 20:49:32 +0000

I would argue about personal use of subversion, for that task I find bazaar better. It’s so simple to make it just work for version control. You don’t need to create separate repository just for keeping your files and you don’t need to have separate server for colaboration or storing files on external machine. Bazaar can work via ssh, ftp and others, including svn repo. It’s easier for me to use it, seems more intuitive. Did I mention it’s also written in Python?

Comment on Trivial accessors and uniform access by Tomek Paczkowski

Tomek Paczkowski — Sat, 09 Feb 2008 19:39:29 +0000

There is a good article about differences between Java and Python: Python Is Not Java by Phillip J. Eby. It’s surely reading-worth for Java programmers wanting to learn Python.

Comment on Trivial accessors and uniform access by Bartosz Bankowski

Bartosz Bankowski — Sat, 09 Feb 2008 19:07:05 +0000

It was an interesting article for me, as I didn’t know about the UAP before. However, I don’t agree with your assumptions:

> But in Java you have to introduce getters
> and setters from the very beginning, or it
> will bite you back in the future. It
> clearly contradicts with the DRY principle
> and a preference for evolutionary design,
> which discourages writing code that is
> useless right now, but may (or may not)
> be needed in the future.

You say that I have to create getters and setters from the very beginning, while
this is not true. I never do it. The very first time I create getter or setter is when I need to use it from my code.

Described behavior would not only be against the DRY rule, but also could lead to broken encapsulation.

> The whole problem boils down to the fact
> that in Java you can’t apply the Uniform
> Access Principle

Which problem? From my point of view, the problem is not in a language, but in a design.