On 2/04/19 1:56 PM, Cameron Simpson wrote:
On 02Apr2019 13:14, DL Neil wrote:
On 2/04/19 11:57 AM, Cameron Simpson wrote:
On 29Mar2019 09:32, DL Neil wrote:
Do you 'keep' these, or perhaps next time you need something you've
'done before' do you remember when/where a technique was last
used
On Tue, Apr 2, 2019 at 1:21 PM DL Neil wrote:
> > Sometimes, I recollect and reference, which creates some very weird
> > interdependencies until I get around to refactoring...
>
> but some fairly hairy "technical debt" meantime?
>
>
> > https://github.com/Rosuav/MegaClip/blob/master/deviquotes.py
On 2/04/19 1:25 PM, Chris Angelico wrote:
On Tue, Apr 2, 2019 at 11:16 AM DL Neil wrote:
One of the points which intrigue me is that my colleagues don't keep
snippets/a library, preferring to remember (hah!) when/where they used
particular techniques in the past, and copying/duplicating, to fit
On 02Apr2019 13:14, DL Neil wrote:
On 2/04/19 11:57 AM, Cameron Simpson wrote:
On 29Mar2019 09:32, DL Neil wrote:
Do you 'keep' these, or perhaps next time you need something you've
'done before' do you remember when/where a technique was last
used/burrow into 'history'?
(else, code it from
On Tue, Apr 2, 2019 at 11:16 AM DL Neil wrote:
> One of the points which intrigue me is that my colleagues don't keep
> snippets/a library, preferring to remember (hah!) when/where they used
> particular techniques in the past, and copying/duplicating, to fit the
> new system's requirements. Am wo
Gidday Cameron,
Thanks for this - some thoughts below:-
On 2/04/19 11:57 AM, Cameron Simpson wrote:
On 29Mar2019 09:32, DL Neil wrote:
How do you keep, use, and maintain those handy snippets, functions,
classes... - units of code, which you employ over-and-over again?
Having coded 'stuff' o
On 29Mar2019 09:32, DL Neil wrote:
How do you keep, use, and maintain those handy snippets, functions,
classes... - units of code, which you employ over-and-over again?
Having coded 'stuff' once, most of us will keep units of code,
"utilities", which we expect will be useful in-future (DRY pri
DL Neil writes:
> How do you keep, use, and maintain those handy snippets, functions,
> classes... - units of code, which you employ over-and-over again?
Fun topic!
I have two methods:
First, in my scripts directory I have a file called
"python-cheatsheet.py" where I save small tips that I
think
On 2019-03-28, DL Neil wrote:
> How do you keep, use, and maintain those handy snippets,
> functions, classes... - units of code, which you employ
> over-and-over again?
>
> Having coded 'stuff' once, most of us will keep units of code,
> "utilities", which we expect will be useful in-future (DRY
+1
On Fri, Mar 29, 2019, 2:04 AM DL Neil
wrote:
> How do you keep, use, and maintain those handy snippets, functions,
> classes... - units of code, which you employ over-and-over again?
>
>
> Having coded 'stuff' once, most of us will keep units of code,
> "utilities", which we expect will be us
How do you keep, use, and maintain those handy snippets, functions,
classes... - units of code, which you employ over-and-over again?
Having coded 'stuff' once, most of us will keep units of code,
"utilities", which we expect will be useful in-future (DRY principle),
eg functions to rename fi
11 matches
Mail list logo
