My teammate and I have been dutifully plugging away at our Job Tracker application. I have the database up and running. I have the tables fleshed out. I have buttons looking very nice with rounded corners and a pinch of color to make it easy on the eyes. But as I begin to add jobs to the database I am starting to wonder if I need all of these attributes. I have an attribute for description, salary, follow-up, follow-up due date, job added date, job status, skill requirements, company name, job title…and it goes on and on. Do I need all of these? <\/p>\n\n\n\n
I am at a point now where I think to myself … I should have probably created more use cases. Instead, I created a wish list of information without thinking to myself how badly do I need it? How useful will I find it? If I have one hundred jobs to track, will I want to read paragraphs and long lists for each job? Will I avoid entering jobs if there are over 10 fields to enter, even if voluntary? <\/p>\n\n\n\n
I think a lot of database designers and programmers run across this problem of including too much. We don’t want to leave anything out because…what if they need it? But we also don’t want the user to find the app burdensome or overwhelming. There is usually a happy medium of enough information for the user to find the application helpful but not so much it sends them running for the hills. <\/p>\n\n\n\n
In my next sprint I plan to rethink some of the attributes. I might consider removing…well I can’t think of anything right now because I find them all essential, but surely I will find something. I hope!<\/p>\n","protected":false},"excerpt":{"rendered":"
My teammate and I have been dutifully plugging away at our Job Tracker application. I have the database up and running. I have the tables fleshed out. I have buttons looking very nice with rounded corners and a pinch of color to make it easy on the eyes. But as I begin to add jobs […]<\/p>\n","protected":false},"author":13176,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-23","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blogs.oregonstate.edu\/hollytlucas\/wp-json\/wp\/v2\/posts\/23","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.oregonstate.edu\/hollytlucas\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.oregonstate.edu\/hollytlucas\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/hollytlucas\/wp-json\/wp\/v2\/users\/13176"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/hollytlucas\/wp-json\/wp\/v2\/comments?post=23"}],"version-history":[{"count":1,"href":"https:\/\/blogs.oregonstate.edu\/hollytlucas\/wp-json\/wp\/v2\/posts\/23\/revisions"}],"predecessor-version":[{"id":24,"href":"https:\/\/blogs.oregonstate.edu\/hollytlucas\/wp-json\/wp\/v2\/posts\/23\/revisions\/24"}],"wp:attachment":[{"href":"https:\/\/blogs.oregonstate.edu\/hollytlucas\/wp-json\/wp\/v2\/media?parent=23"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/hollytlucas\/wp-json\/wp\/v2\/categories?post=23"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/hollytlucas\/wp-json\/wp\/v2\/tags?post=23"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}