Oof, I felt that. I recall reading, many years ago, some statistics on how CD-ROM discs filled to about 600-650 megs made them much more reliable than the ones pushed to theoretical maximums. This was about regular, retail data CDs, not (re)writables.
I have always felt the floppy was a great demonstrator of the concept: a 3.5 inch might be perfectly fine for everyday usage and storage, but the moment you're trying to carry some data in 1.44 meg [0] zip portions, you're bound to find out just how many defective discs you had the entire time.
[0]okay, it was 1.37 meg of data actually IIRC but still
The difference is providing a short succinct message that is either familiar or can be looked up as rg does here, vs vaguely saying invalid name without saying why.
It worsens the UX for no reason.
As a sibling comment said, the program already knows why the name was invalid. It would have cost nothing to surface the reason when reporting the error.
I'm not arguing that I think "Invalid name" is a good message here. I don't think it is. But if you're relying on either familiarity or the ability to look it up, then you're still relying on there being a manual to provide that information in the first place if it is not somehow included in the error message itself. As would be the case here with Bee and rg.
The equivalent of BeeBase’s error in your example would be simply “invalid regex”, which I’d say is still more useful as regex is widely understood and there are many tools that you can give regex to that will tell you what is wrong with it.
No, there's a specificity to "name" and "group" that makes them similar, which is one part of why I settled on this example. The other is that I expected the recipient to have experience with regex and find the example dumb, confirming my position that one can very well demand a basic knowledge of the tool that isn't immediately communicated by it.
Like knowledge of the regex language, or having spent ten minutes skimming through the tutorial part of a PDF manual.
In my experience, how to use a manual is a technique more widely understood than regex. Maybe this impression is wrong, I'd welcome something tangible pointing in another direction if it is.
The best advice I can give you: create maximum opportunity to regularly meet the same people, in a casual setting.
By that I mean join sports clubs, hobbies, church, reading clubs, volunteering, anything really.
Pick as many as you can handle.
Make sure you:
- get to know a lot of people, in a positive context
- be interested in them, get to know them. Let them in your life, get them to know you too.
- meet them regularly
- make sure it's a casual setting so nothing's forced.
Any person you get to know well (man or woman) is a gateway to someone else ("have you met my friend").
A large social network is key.
I read that you go on walks - get a dog too. This is awesome for starting conversation.
You don't need a dog to start conversation, but it's a very lazy way to get others to start conversation with you. Be the source, not a consumer of other people's initiative.
They're not really cars. They sell navigational, entertainment- and seat-heating solutions. These things are used a few hours each day. A better way to think of them is like a transportation solution that you rent. Even big unrelated companies rent things.
>> 2012. Right, this site must be dead. Let's move along.
To be honest, I love it when I see a fixed date. Some information is time-dependent. Maybe I do move along when I see 2012. no time wasted here. That's a feature!
This really brings back memories of programming RPG for the AS/400 in school, almost 30 years ago. Since we did not actually have access to an AS/400, all programming was done on printed pieces of paper.
The paper was formatted in numbered rows/columns, where for example a loop was created by putting the letter R in exactly column 5 and nowhere else (something like that, thankfully I've forgotten the details).
It all felt like one step above punched cards.
Our "programs" were never actually executed, our professor also did not have access to an AS/400.
Anyway, just saying, column and row based programs are a welcome trip down memory lane, let's keep it there.
This reminds me of the time I used Drupal for a hobby project of mine (10+ years ago).
I wanted to upgrade it to a new Drupal version, and one of the first steps was "Backup your database".
It'll be fine I thought.
After the upgrade I was presented with a brand new, empty system.
One of the final steps was: now get your backup and load the system with it.
Fun times. Also my last adventure with Drupal.
reply