- Popular Post
ChrisStrykesAgain
-
Posts
3 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Gallery
Posts posted by ChrisStrykesAgain
-
-
On 11/28/2019 at 5:13 AM, drjdpowell said:
Note: if you have a Tools Network package, you can request assigned ranges of error codes for just your library. For example, "SQLite Library" errors start at 402860
Are these ranges published, per chance? If not, I think this proposed wiki page might be a good repo for those as well (if the authors are willing to divulge).
-
NI has established "user" error code ranges:
- -8999 through -8000
- 5000 through 9999
- 500,000 through 599,999.
Unfortunately, I can't count the number of "error 5xxx" constants that I've seen. We should stop that; it leads to confusion at best.
In an ideal world every developer or organization would have their own reserved error code ranges, but I accept that's not reasonable. That said, has anyone considered creating an informal list that organizations/individuals can publish their preferred error code ranges in? I think it might be useful. For example, if I'm at Company X and I see Company Y likes to use the range 501,000 to 501,999 then I'd probably choose not to use that range to avoid potential confusion to some extent.
It wouldn't be fail-safe or enforceable, but I think it would be valuable; is anyone else on board with the idea? If so, we'd need to decide on where to publish them, but the LabVIEW Wiki would be one obvious choice in my opinion.
User Personas and User Stories
in GCentral
Posted
As a user collaborating on an idea for un-created code, I want to be able to see what other users are thinking about as well.
For example, let's say, in the back of my mind, I have this idea for an open source barbecue thermometer that runs on a Raspberry Pi using LabVIEW. That said, I have several open source project ideas, all of which I find equally interesting, so I randomly pick one of them to start working on. But, maybe there's another community member that wants such a BBQ thermometer as well. If I knew that, I might choose to prioritize the project that someone else is interested in vs. another project that nobody (but me) cares about.
Similarly, let's say I have the idea, but don't have the bandwidth to really pull it off in any reasonable timeframe. Someone else sees the idea, however, and wants to help. Knowing that I'm not alone, I might choose to begin work on the idea.
Finally, let's say that I have this really cool idea, but I'm a software guy and it would probably require a custom Pi HAT. That's way outside my comfort zone, but maybe someone else is willing to help with that, and make the project a reality.
This could even allow for voting, similar to the kudos system on the NI Idea Exchange. Of course, there's no obligation to do anything if your idea gets a bunch of kudos, but it could be incentive and/or drive innovation by others.