methodology

UPDATE: example repository, https://github.com/so-gitdemo/so-gitdemorepo In the context of the github repo. How can I easily locate rev "b0430cee"? I know I can just look, but the real example that this repository mimics has a dozen committers and multiple other branches. Not quite as easy to use inspection. How can I find the branch creation revision when the branch has been merged multiple times? I am aware of this question: How to determine when a Git branch was created? The solution does not appear to work for a branch that has been merged multiple times. We typically merge bug fixes back

I've been pushing for continuous integration at my company since I joined 5 months ago, but having seen the type of applications we work on I'm starting to think that it might not be worth the effort of setting up each and every project for continuous integration. If you work in a development department where the average project takes 2-3 weeks and once it's deployed you seldom if ever have to worry about it, is continuous integration worth the hassle of setting it up? Probably depends on your process. If you have unit tests that cover your code, then continuous integration is worth every bit.

As a software engineer, I have a strong bias towards writing business logic in the application layer, while typically relying on the database for little more than CRUD (Create Retrieve Update and Delete) operations. On the other hand, I have run across applications (typically older ones) where a large amount of the business logic was written in stored procedures, so there are people out there that prefer to write business logic in the database layer. For the people that have and/or enjoy written/writing business logic in a stored procedure, what were/are your reasons for using this method? I

I've had some issues lately with PHP memory limits lately: Out of memory (allocated 22544384) (tried to allocate 232 bytes) These are quite the nuisance to debug since I'm not left with a lot of info about what caused the issue. Adding a shutdown function has helped register_shutdown_function('shutdown'); then, using error_get_last (); I can obtain information about the last error, in this case, the "Out of memory" fatal error, such as the line number, and the php file name. This is nice and all, but my php program is heavily object oriented. An error deep in the stack doesn't tell me much

In .NET, if a class contains a member that is a class object, should that member be exposed as a property or with a method? If all you are doing is exposing an object instance that is relevant to the state of the current object you should use a property. A method should be used when you have some logic that is doing more than accessing an in memory object and returning that value or when you are performing an action that has a broad affect on the state of the current object. You should use properties for anything that conceptually represents the object's state, so long as its retrieval isn't

How to create a rich user interface Windows application, example Photo Shop. I am looking for clean MVC tutorial for WinForms with C# somewhere. ( Not ASP.NET MVC.) Being new on the Windows Platform; most MSDN and internet tutorials basically puts everything into the Form class. Further Default events are handled inside of the form, instead of sending events to the control/model, which in it's turn changes the view's state. Or is the preferred methodology for Windows Applications something else? Derick Bailey (via Los Techies) has blogged some fantastic articles (and complete demo source code)