FrustratedWithFormsDesigner

less info
35,085 reputation
588146
bio website
location
age
visits member for 3 years, 6 months
seen 1 hour ago

6h
revised Which license should I use in the program?
added 26 characters in body
8h
revised Should the commit history be used to convey critical information to developers?
added 1 character in body
8h
comment Should the commit history be used to convey critical information to developers?
@user119591: No, I wouldn't. If the problem happened two years ago and was still a problem today, it would be documented in a team wiki, and new developers would read about it there when they're setting up their workstation.
8h
comment Should the commit history be used to convey critical information to developers?
@Daenyth: I don't think email is the only place to document this, I think it's the best tool to send the initial notification of the problem to all people who might encounter it themselves if not immediately warned.
8h
revised Should the commit history be used to convey critical information to developers?
deleted 79 characters in body
1d
awarded  Nice Answer
1d
revised Should the commit history be used to convey critical information to developers?
added 128 characters in body
1d
comment Should the commit history be used to convey critical information to developers?
@BlueRaja-DannyPflughoeft: Email provides a simple and easy-to-use method to let everyone on the team know immediately that a problem has been discovered in using a specific version of a specific library and that this version should not be used. As stated, long-term documentation is best done in a team's wiki or some other sort of knowledge base.
1d
comment Avoiding Double POST
@PaulCroarkin: Have you been able to demonstrate that this can happen and will cause a problem in your system?
1d
revised Should the commit history be used to convey critical information to developers?
added 259 characters in body
1d
comment Should the commit history be used to convey critical information to developers?
@ABMagil: The information goes into a wiki. Developers who are new to the team are usually started of there, on some introductory pages. Then they come to specific individuals (who have made time available for helping the new dev) when they have specific questions (and they always do). For us, it would probably end up in the "Developer Setup Guide for ApplicationX" as NOTE: Do not use SDK vers. x.y.z because... but the initial communication should be an email.
1d
comment Avoiding Double POST
I'm guessing the implementation of the clients is out of your control?
1d
answered Should the commit history be used to convey critical information to developers?
2d
revised Encapsulation: Separate functions for separate variables, or return a table? [PHP]
added 259 characters in body
2d
answered Encapsulation: Separate functions for separate variables, or return a table? [PHP]
2d
answered Programming a promotions engine
2d
comment Object based programming paradigm
@RobertHarvey: So should this be reopened or should it have been closed with a different reason?
2d
comment Object based programming paradigm
This question appears to be off-topic because it is asking for general information that can be easily found online. If there is a more specific question that you have, please update your post to include it.
2d
comment Object based programming paradigm
It is a term that refers to "any programming language that uses the idea of encapsulating state and operations inside 'objects'". There are two subcategories: Class-based and Prototype-based. Source: en.wikipedia.org/wiki/… Also: en.wikipedia.org/wiki/Object-based_language
2d
revised Programming a promotions engine
added 2 characters in body