Roy Lambert wrote:

> lots of people no longer even bother trying to learn

Too true, but to an extent, also the right thing to do. Things change
so much nowadays that most of what you knew 5 years ago is irrelevant.
Heck, I don't use DBISAM any more except in code that is already
dependent on it - EDB is much better. In learning C# recently, I'd find
solutions to problems that were basically "magic" to me. Took further
learning to understand how it actually did it.

--

Matthew Jones

Matthew


>> lots of people no longer even bother trying to learn
>
>Too true, but to an extent, also the right thing to do.

I, being the awkward sod I am, must 173.79% disagree with you there.

>Things change
>so much nowadays that most of what you knew 5 years ago is irrelevant.
>Heck, I don't use DBISAM any more except in code that is already
>dependent on it - EDB is much better. In learning C# recently, I'd find
>solutions to problems that were basically "magic" to me. Took further
>learning to understand how it actually did it.

If you fully supported your position here the last sentence would not be there <vbg>

Roy

Roy Lambert wrote:

> >> lots of people no longer even bother trying to learn
> >
> > Too true, but to an extent, also the right thing to do.
>
> I, being the awkward sod I am, must 173.79% disagree with you there.

I both agree and disagree. 8-)

One of the things that a former boss used to hate was that I'd learn
everything about some technology, typically an interface or something,
then I'd create a wrapper library that made it easy to use in our code
to achieve the functions we needed, and then I'd forget it all within a
few weeks as I now only needed to know our interface. (Obviously I
don't forget everything, but some parameter detail of the internals was
no longer relevant as my wrapper took care of it.)

The skill is in knowing what you need to learn, and what you don't.
Rather like in Delphi where you can "outsource" some advanced stuff to
a component and never have to know how it works, or sometimes do it all
yourself because it is a core capability of your software.

--

Matthew Jones

Matthew

>> >> lots of people no longer even bother trying to learn
>> >
>> > Too true, but to an extent, also the right thing to do.
>>
>> I, being the awkward sod I am, must 173.79% disagree with you there.
>
>I both agree and disagree. 8-)

Good position to take

>One of the things that a former boss used to hate was that I'd learn
>everything about some technology, typically an interface or something,
>then I'd create a wrapper library that made it easy to use in our code
>to achieve the functions we needed, and then I'd forget it all within a
>few weeks as I now only needed to know our interface. (Obviously I
>don't forget everything, but some parameter detail of the internals was
>no longer relevant as my wrapper took care of it.)
>
>The skill is in knowing what you need to learn, and what you don't.
>Rather like in Delphi where you can "outsource" some advanced stuff to
>a component and never have to know how it works, or sometimes do it all
>yourself because it is a core capability of your software.

I suspect that we may be using learn in slightly different ways. What you're saying is that you do learn stuff then forget it when its no longer useful. I do that too. With my own code sometimes, or should that be often! What I'm complaining about is people who will not learn and want the answer spoon fed to them every time they encounter a problem.

The analogy in the recruitment world is those recruiters who will only use LinkedIn for candidate identification. If someone isn't on LinkedIn then, according to those recruiters, they don't exist.

Roy