Probably nowhere. A colleague of mine from work back in the early 2000s told me about the site when I was looking for a C++ ADO DB library. I searched CP and found an article that was nearly exactly what I was looking for. I've been a member ever since.

To "bear" a child is to give birth to said child. QED. :laugh: I'd missed the anagram reference so that's all I could think of. I was pretty sure it was wrong but that's the way the CCC bounces.

Argggg! I came up with bear=birth and dates=days but I couldn't figure out what red canals had to do with it. That in itself should have told me it was an anagram. C'est la vie. Nice clue though!

I didn't find it too difficult. It took me about 10 minutes to solve it. But, I didn't start till about 40 minutes ago. It was solved, and usually is, a couple hours before I've even read it. Central Daylight Time is about 6 hours earlier than your time. If I'm awake at 3 am my time it's usually because the coyotes are howling outside my bedroom window. I'm not advocating for changing the "official" start time of the CCC. I am trying to solve them, it's just that I'm starting late so there's no reason to respond if I do solve it (unless I have a pithy comment). :-D

I've been working on them. I'm quite out of practice I guess. Once I get my head back in that manner of thinking I'll start getting them again I'm sure.

Similar story. In my 8th grade shop class we did a fiberglass unit in which you could make a boomerang. After it was complete and graded I brought it home. Me and my 2 younger brothers went to a nearby field to test it out. My first throw it flew flat and level for about 40 or 50 yards when it suddenly bent up in the air circled about 90 degrees left and did a kamikaze run down at the 3 of us. It was like a drill Sargent yelled "INCOMING!". We leapt to the side and hit the dirt like it was a live grenade. It smacked into the ground about 10-15 feet from where we were. Try as we might we never were able to replicate that first throw. One of my brothers did keep practicing over the summer and was improving quite a bit until he hit a telephone pole and cracked it up.

Reaching for a goal of hyper_sonic_ speed (mach 5, or 5 times the speed of sound), they still have a ways to go to reach the speed of light. I think the headline is a bit hyperbolic.

That's the problem I've always had with agile. Like you, in the 36 years I was active I never had 100% access to a customer. I could call occasionally to ask questions and clarify requirements but they were generally busy doing their daily work. They had limited time for me. Once in a great while they'd come to the office but usually for training after development or for requirements/kickoff meetings beforehand. But sitting in on Dev meetings or generally being there during development - never, not once. Not even during my last 3 or 4 years when my company was actually trying to switch over to agile scrum. They had their own jobs to do and those jobs ranged much further than just running our software. Heck, we couldn't even get them to install beta versions to tell us what they liked or hated no matter how much we begged.

No. Just like every other successful solution, you tried the right one last. :laugh:

And, there was all that emotional trauma! :laugh:

My understanding is that you are the sole developer of this library. Furthermore, users of 1.0 are not paying you for maintenance/support. Even though it's really cool that you have users and you want to make life easy for them, enhancing maintainability is an important major change (and not just for you). I think you can absolve yourself of any guilt for not including any great new features for your users in 2.0. Ease of maintenance also helps your users. Bug fixes and future new features come quicker with fewer defects. Besides, if you're going to make a breaking change better to do it between versions 1 and 2 (more understandable/forgivable) rather than 6 and 7 (though, when it needs to happen, it needs to happen). As long as releasing 2.0 doesn't force 1.0 users to upgrade they can just stay with 1.0 until it behooves them to upgrade and deal with the breaking changes. If this is true I think you can release 2.0 when you are ready. It's okay to leave the bitmap tweaks, anti-aliasing and other stuff for a later point release. (We'll hope they won't also cause breaking changes.) You just need to document that 1.0 is as complete as it will get, new users should use 2.0, and upgrades will break existing code. 2.0 doco probably should mention it breaks existing 1.0 code as well as include some examples on how to perform those changes. Just the biggies, it doesn't need to be exhaustive. (Well duh, 'nuff said, I'm preaching to the choir here.) Just my 2 cents, take it for what it's worth. :)

Better get used to it if and when you make that move to the Great White North, eh. :-D

Wordle 1,163 4/6* 🟨⬜⬜🟨🟩 🟩⬜🟩⬜🟩 🟩🟨🟩🟨🟩 🟩🟩🟩🟩🟩 An argument can be made that I actually solved it in 3.

I like Gary Sinise. I used to watch that show back in the day. I think I saw that episode. I seem to remember my utter disbelief of that scene, but I could be wrong. There are so many CSI scenes that could have triggered that feeling. Can you even imagine the primordial scream if a manager told a sys admin, "I want you to write a GUI in VB to track an IP?" :laugh:

Quote:

... the uppety zealots that are immature and can't give straight answers to questions you ask online. Like "how dare you use a distro I don't like, etc."

Isn't that the truth. The bane of my Linux existence - especially early on.

Like you I made the switch to Linux (Ubuntu) when I purchased a new desktop for my home use back in 2015. It's still my primary (only) computer unless you want to count an Android phone and an Android tablet. My wife has a Win10 laptop but I only use it when she says, "Here, fix this [grawlix] POS."; "Yes, dear." My reasons track with yours: ease of updates and seems to use less resources. After all, it's still running after nearly 10 years and I haven't noticed it becoming sluggish (I did upgrade to an SSD a few years ago). I also do a bit of hobbyist coding. I do miss Visual Studio's tool integration but not that much - especially since retiring in 2018). Start long winded (somewhat related) story... I run everything in VMs so the Windows programs I use for which I can find no Linux replacement that I like I have a Win10 VM. I can't upgrade to Win 11 (no TPM 2.0) so I'll probably replace the whole PC towards the end of the year (Black Friday sales maybe? That's how I got this system.) When I bought the PC back in 2015 it had Windows 10 pre-installed. I dumped that and put Unbuntu and Oracle Virtual Box on it. I created a couple Linux VMs (my main daily use system, a Plex Server, a figure out Linux play system) and a Win 10 VM. When I spun up the Win 10 VM it of course said my system was not registered. That was when I discovered that MS no longer put a colored license key sticker on the installation CD. I called MS support and asked how I could find the key. They gave me a command to return it. It didn't work because Windows was newly installed on the VM and not the version that was pre-installed on the PC. So, I asked him, "If, let's say, I had taken a system backup (disk image) before I embarked on this VM adventure, could I restore said backup, run this command to record the key, and then come back to this VM to enter it?" He asked me, "And, you only mean to run Windows in this VM and not copy or replicate it elsewhere?" I replied, "Yes. I have no intention of making copies of Windows or this VM." To which he replied, "Then, Yes. This command will work for you." We both chuckled, that's what I did, and the rest, as they say, is history. I pretty much jumped in the deep end of the Linux pool and managed not to drown (though there have been bouts of emphatic cursing). But, I'm happy with how things have turned out and I haven't looked back.

It is indeed.

Yes I saw that. Not sure what went wrong. I've been unable to remedy it as yet.

I believe he is soliciting opinions on the following tool: [Understand^] I borked the link. Use Jeron1's below if you're interested.

Yeah. I thought the whole idea was: "It's electronic, there are no paper or shipping costs so Kindle will be much cheaper."