The joy of doing things the hard way

While rummaging around a while back I stumbled across a stack of old copies of The Delphi Magazine. And of course I started reminiscing.

When I was a lad

Did you know that information was once distributed on paper?!

That was back at a time in prehistory before the web. It took forever to solve a programming problem, especially for those of us without a network of programming friends.

What did we do before Stack Exchange? We struggled that's what. We browsed magazine back issues, we ordered library books and, more often than not, we never found an answer.

Back to first principles

But did that isolation have one advantage? If you were facing a problem you might just have to get creative and solve it yourself.

Of course, it probably meant reinventing the wheel. Your solution might be far from the commonly accepted solution. It might even be laughably sub-optimal. But if it worked, it was an achievement. It was creative.

I'm just wondering if we might have lost some of that? I know I now rush to the net every time I run into a problem, whereas before I'd sit and think (often in the bath) because that was the only option.

The joy of doing things the hard way

For years I disliked using code libraries, because writing my own solution was more interesting. Come to think of it, I'm still a bit like that. The joy for me isn't in finishing a project, it's in solving the problem (which could explain all those unfinished projects!). So the more help I get, the less rewarding the process.

But I do have the luxury of being an amateur - no deadlines, no boss, no profits at risk. Because it's a hobby I go where my interest takes me. I fully understand that professionals haven't got that luxury.

Don't get me wrong, I'm not being a Luddite and suggesting, as old farts tend to, that things were better in my day. They weren't. Far from it. It's just that we may have lost a little in return for the huge improvement in access to information. Maybe things were just a little more stimulating back then?




Comments

  1. Steve Jordi12:49 pm

    Another life changer was the introduction of newsgroup forums, before they were submerged by porn and illegal downloads. C, C++, Fortran, Pascal... dedicated forums, you had a blocking problem, asked a question, targeting only people focused on the same matters as you, and you usually got an answer within a few hours. People helping other people since they met the same pitfalls and wanted to share the experience. This was a major tool for developers! Gone was the time of swearing for weeks on a problem someone else already faced and solved. And helping others was so rewarding too. This was much better organized than StackOverflow IMHO.
    Newsgroups changed my life forever.

    ReplyDelete
    Replies
    1. Delphidabbler7:24 am

      I'd forgotten about that! Didn't use them much myself because I was a late adopter of the Internet (largely because our local providers ran on clockwork back then!)

      Delete
  2. Michael Riley5:43 pm

    Made me smile. I took magic lessons in a group setting when I was twelve. After watching the magician perform a trick I blurted out, "Hey! How did you do that?" The magician looked me square in the eyes and said, "Michael, if you really want to know how this trick is done you have to figure it out for yourself." That was my introduction to "problem solving".

    ReplyDelete
  3. Max7:32 am

    I, too, remember The Delphi Magazine and the joy of solving problems on my own. Many years ago before Delphi, I needed to solve for the internal rate of return of a series of irregular cash flows on my old Commodore 64. Only later did I realize that I had used the bisection method of finding an iterative solution. (Later, a friend shared an article from a chemical engineering magazine that introduced me to the secant method which usually converged so much faster on the old slow machine.)

    I recently asked the Bard AI to write a Delphi function using the secant method to solve for the internal rate of return given a series of irregular cash flows and fall back to the bisection method if the secant method did not converge on a solution. Bard returned perfectly acceptable code functions.

    At my advanced age (81), I wonder how future programmers will incorporate the tools that will be available in the future. Somehow, I doubt that old-fashioned research and problem solving will ever be totally obsolete though.

    ReplyDelete
  4. dummzeuch6:53 pm

    Even before the newsgroups became widely available outside universities there were other discussion channels: Mailboxes and later Fidonet. I used Fidonet a lot before I even got Internet access at home. Internet access at work was even later because companies tended to see it as a waste of money and employee time.

    ReplyDelete

Post a Comment

Comments are very welcome, but please don't comment here if:

1) You have a query about, or a bug report for, one of my programs or libraries. Most of my posts contain a link to the relevant repository where there will be an issue tracker you can use.

2) You have a query about any 3rd party programs I feature, please address them to the developer(s) - there will be a link in the post.

3) You're one of the tiny, tiny minority who are aggressive or abusive - in the bin you go and reported you will be!

Thanks

Popular posts from this blog

Initialising dynamic arrays

When writing some unit tests a while ago I found myself needing to initialise some dynamic arrays with test data. It would be nice if we could do something like this: var A : array of Integer ; begin A := ( 1 , 2 , 3 , 4 ) ; // !! WRONG end ; but we can't. So I decided to write some functions to initialise dynamic arrays to the contents of another array, be it a constant, a literal or another dynamic array. The result was a set of overloaded routines, one for each data type I needed to handle, for example for Integer and string arrays I had: function CloneArray ( const A : array of Integer ) : TIntegerDynArray ; overload ; var Idx : Integer ; begin SetLength ( Result , Length ( A ) ) ; for Idx := Low ( A ) to High ( A ) do Result [ Idx - Low ( A ) ] := A [ Idx ] ; end ; function CloneArray ( const A : array of string ) : TStringDynArray ; overload ; var Idx : Integer ; begin SetLength ( Result , Len...
Read more

Deleting elements from a dynamic array

In my blog " Initialising Dynamic Arrays " I mentioned I have been writing some unit tests that needed numerous repetative array initialisation operations. Well, one of the other common operations I found myself writing was the deletion of items from dynamic arrays. So I decided to find a generic way of doing this. Assuming we know the index of the item to be deleted we need the equivalent of Delphi's built-in Delete procedure for strings. If you read the previous post you won't be surprised to learn that I decided to further extend the Generics.Collections.TArray class by adding to the TArrayEx class I introduced there. My first attempt emulates Delphi's Delete procedure by deleting the array element in-place: i.e. it updates the array passed as a parameter. Unsurprisingly the method is called DeleteInPlace . Here's how it goes: type TArrayEx = class ( TArray ) public .. . class procedure DeleteInPlace < T > ( var A : ...
Read more

New String Property Editor Planned For RAD Studio 12 Yukon 🤞

Image
This blog post is based on a pre-release version of the RAD Studio software and it has been written with specific permission by Embarcadero. No feature is committed until the product GA release. It seems I'm getting very excited about multi-line strings of late. My previous post was about multi-line string literals for Delphi  and this time I'm talking about the new multi-line string property editor being slated for the RAD Studio 12 IDE. For more years than I care to remember, I've been frustrated by the inability to enter multi-line strings in the Delphi IDE object inspector. That meant having to resort to code to initialise some multi-line labels. So frustrated was I that I wrote a little property editor of my own ( stringpe ), way back in 2004. It's still around and on GitHub. Here's what it (sometimes) looks like: Yeah, I know this is Vista - I used an old screenshot Sometimes? Well it looked like that until it got installed on DPI aware Delphis, and then it sh...
Read more