• Hey Guest. Check out your NeoGAF Wrapped 2025 results here!

GAF Devs Thread - a thread about programmer's rants

Status
Not open for further replies.
I'm still in school, graduating this semester, but I absolutely hate how stupid I feel when I'm working on a project and trying to fix.

One example was that I was doing a lexical analyzer in Java for my compiler design class, and for some reason it was having trouble recognizing spaces.
zer in Java for my compiler design class, and for some reason it was having trouble recognizing newlines. I looked all over for what the issue was.I checked, checked, and checked again, and I was sure my code was correct. I googled for a bit, and finally one StackOverflow question I found was my exact problem: Apparently Windows newline character comes out as "rn" instead of just n. There was about to be a hole in my monitor after that.

Edit: Swype hates mobile GAF and screwed up my post, I'll have to fix it later.
 
I honestly think this is part of the problem. It's not an obvious consequence, but your software is implicitly telling the user "Hey, I think you want to work with this" when they really don't. What are the odds that the user cares about the first record? There should be no selection on initialization.

It's such a tiny little detail, but it might have made a world of a difference. If the user had to specifically choose which record to overwrite, I bet they wouldn't have done it.

Agreed. But it's no self-developed tool, it's Microsoft Access. I can't change this behavior.

Wow, haha. When you save, I hope it pops up a message that says "Are you sure you want to overwrite/change this record?" or something like that. And the save button better be labeled something that makes it clear you're not creating a new record, but editing one.

No, there's no confirmation. And I bet I would receive complaints if I added one, as it's a common use case for the users to often go through their many records to add some small piece of information.


Can't always blame the user!

Of course not. I rarely do this. But in this case, her alarm bells should have tingled when there was already data in the form. Also, in her position she certainly has worked with many Access files before.


This. Sorry but it seems like a poorly designed tool.

This is also true. As mentioned above, it's an MS Access tool, and it was developed by some consulting company. The usability/UX is terrible, and the actual source code ist just awful. Refactoring it was a pain in the ass, and I'm not even fully done with it.

With reference to Robert Martin's Clean Code mentioned on the previous page, I try to leave the code cleaner than the way I found it, but there's still so much to do. I would love to do a complete UX overhaul, but it seems that's the last thing my superiors care about..
 
Status
Not open for further replies.
Top Bottom