Hey,
Just wanted to drop a note here that I recently started a YouTube channel --
https://www.youtube.com/user/siddhartalists
In the videos I code short python programs exploring games, maths and so
on. Most of the code is quite short, under 50 lines, and the videos are
10-15 mins long each.
Wo
Hmm.. is this going the BCB Collectives way? Personally I think lets just
have a regular unconference and if someone wants to host a usergroup
meeting, they can put up a session on it and interested people will come.
--
Siddharta
On Fri, Mar 20, 2009 at 6:51 PM, abhinav sarkar wrote:
> +1 for th
On Fri, Jun 4, 2010 at 12:05 AM, Venkatraman S wrote:
> On Thu, Jun 3, 2010 at 11:20 PM, Noufal Ibrahim wrote:
>
> > What's the intention of the course? The structure of the course would
> > depend on that methinks. Is it to
> > - Give the students some programming skills so that they can use t
Yes you can, we do something like what you mentioned.
If both projects share the database, and are on the same domain (ie they
share the cookie) then you can login in one and be authenticated in the
other. Both projects need to be configured to use the same auth backend (its
like this by default)
Your apache config can be something like this
SetHandler python-program
PythonHandler django_project_1_frontend
PythonInterpreter django_project_1
PythonOption django.root /path1
SetEnv DJANGO_SETTINGS_MODULE apps.settings
PythonDebug On
PythonPath "['C:/Projects/tools
Refactoring just means changing the internals without adding/removing
functionality. The book is good, but refactoring can be applied in many
other contexts too. It has been happening long before the book came out. The
big insight in the book is not the refactoring patterns themselves. The big
ins
On Sun, Dec 5, 2010 at 4:07 PM, Anand Balachandran Pillai <
abpil...@gmail.com> wrote:
>
> That is re-architecting or re-designing depending on which side of the
> conference table you are - not re-factoring.
>
>
Err... Refactoring _is_ redesigning, that is the whole purpose of
refactoring.
The
Nice quote.
You hit the main point: Refactoring has always been done. Everyone does it.
The book just gives a taxonomy to common refactorings.
For what its worth, I think a taxonomy is very important. It is so much
easier to communicate a design by saying this is a factory, that object is
an obse
