824 reputation
412
bio website schoolofficepro.com
location United States
age 41
visits member for 3 years, 9 months
seen Jun 23 at 19:13

School Office Pro.

We provide web based applications for schools to enable online registration, ecommerce, hr, surveys, mass email broadcasting and more.


Mar
3
comment What should I do when I've already waited too long between commits?
On a personal level I agree that you shouldn't do large commits unless you are radically changing a code base.. at which point you should have branched it anyway. However we're talking about a single programmer that has been working essentially disconnected and is now trying to get back to doing the right thing. In that case I believe one large commit is preferable.
Feb
27
answered What should I do when I've already waited too long between commits?
Feb
27
comment Able to read Code but struggling majorly to write it
Embrace your inner Nike and "just do it".
Jan
4
comment Bump version number in commercial software development?
Disagree that version matters most to developers. Most software companies happily increase the version number once a year in order to convince customers to "upgrade" whether they need to or not.
Jan
4
comment Date as software version number
Also, date based versions are no more "flat" than "2.1.3". Neither have meaning without context. For most VCS's pulling out a set of files by date is generally more reliable than pulling out by a label. For the simple reason that people sometimes forget to stamp a particular set of files with a version label while the VCS never forgets to date/time stamp the update.
Jan
4
comment Date as software version number
Having multiple releases a day doesn't equate to having a release problem. What it might indicate is that you have a large project, where several people/groups are constantly working to release updates. These might be fixes or simply enhancements.
Jan
4
comment Date as software version number
I'd argue that features often get pushed from one release to another and therefore any documentation given to a customer that "feature x will be in release 2" is likewise doomed to failure.
Jan
4
comment Date as software version number
We also have continuous deployment, and we use a major version + the date. It's simply the easiest way to keep track of what's going on. Quite frankly it's easier to query version control to pull out the source files for a given date than it is to constantly have to tag files and query that way.
Nov
22
asked Approach to algorithm for assignment of resources
Nov
22
awarded  Informed
Nov
7
awarded  Autobiographer
Sep
22
awarded  Yearling
Aug
5
comment Do we set the bar too high by requiring that code tests not suffer from buffer overflow?
@JoopEggen: I'm pretty sure "psychic" wasn't the word you were looking for. Otherwise they should have been able to read your mind... ;)
Aug
5
comment Do we set the bar too high by requiring that code tests not suffer from buffer overflow?
@MichaelShaw: If someone is writing an OS, but has yet to be taught the basic operations of the most common server type then it shows that his school was skipping large (and highly relevant) areas of his education. The question then becomes what else was skipped?
Aug
3
awarded  Nice Answer
Aug
2
revised Do we set the bar too high by requiring that code tests not suffer from buffer overflow?
added 543 characters in body
Aug
2
answered Do we set the bar too high by requiring that code tests not suffer from buffer overflow?
Feb
26
awarded  Constituent
Feb
21
answered idquantique .vs. rdrand
Feb
21
comment Is tracking Android OS.Buid/Manufacturer info a privacy issue?
@JimmyHoffa: The part about from an "ethical perspective" doesn't have to be answered by a lawyer and is certainly fair game here. My answer covers that perspective which is more open about information disclosure than any current law on the books regardless of country.