I do not believe that it is possible to sell Agile to a company, they must come to the realization of what it entails themselves.
Doing a stand-up meeting (a.k.a daily scrum) meeting should be simple, so why are so many teams doing it wrong?
The goal is not to write code faster. The goal is to produce valuable, working, testing, remediated code faster.
As developers enter the work force, they quickly begin to realize that being paid to do a job is different than programming as a hobby. The following is a series of realizations (in no particular order) about working for a business and developing:
Being able to release faster, is not just about pushing code to production. I will cover how we got to the point where we could release Mule faster.
I have observed that the most unproductive day would be to have scattered meetings all throughout the day.
However you build your software system, creating a well-structured architecture isn't something that happens all by itself. You need to put time, effort and discipline into it.
On the application side, there are several singleton processes - for example cron configurations - that are usually run only once on the whole data set. For a certain category of singleton processes we can switch to a shard-like architecture that can scale first to multiple processes and when necessary to multiple servers.
This week we bring you a Dev of the Week with a twist: We're talking to Scott Westfall, our new Director of Engineering here at DZone.
Our organizations are crippled by separation. To be effective, we must repair these broken relationships within teams and within whole organizations.
I was asked recently to review The Professional Scrum Masters Handbook. As I read this book there were times that I shouted at it and I almost stopped reading in disgust around chapter four.
//Create a copy of original image to avoid any alteration
File.Copy(MyDir + "sample.tif", MyDir + "Testconct.tif", true);
//Create an instance of TiffImage and load the copied destination image
using (TiffImage image = (TiffImage)Aspose.Imaging.Image.Load(MyDir + "Testconct.tif"))
//Create an instance of TiffImage and load the source image
using (TiffImage image1 = (TiffImage)Aspose.Imaging.Image.Load(MyDir + "sample1.tif"))
// Create an instance of TIffFrame and copy active frame of source image
TiffFrame frame = TiffFrame.CopyFrame(image1.ActiveFrame);
// Add copied frame to destination image
// save the image with changes.
'Create a copy of original image to avoid any alteration
File.Copy(MyDir&"sample.tif", MyDir&"Testconct.tif", True)
'Create an instance of TiffImage and load the copied destination image
Using image As TiffImage = CType(Aspose.Imaging.Image.Load(MyDir&"Testconct.tif"), TiffImage)
'Create an instance of TiffImage and load the source image
Using image1 As TiffImage = CType(Aspose.Imaging.Image.Load(MyDir&"sample1.tif"), TiffImage)
' Create an instance of TIffFrame and copy active frame of source image
Dim frame As TiffFrame = TiffFrame.CopyFrame(image1.ActiveFrame)
' Add copied frame to destination image
save the image with changes.
Jeff Atwood's new keyboard, New Zealand's new software patent law, and a new concurrent Ruby web server are just some of the stories this week. Plus, get a list of Java algorithms from Princeton and see how you can send files across browsers with WebRTC.
Today I’m finding the courage to ignore hierarchy and artificial boundaries, and by doing so we have started to fix these destructive relationships.
I can see why measuring productivity is so seductive. If we could do it we could assess software much more easily and objectively than we can now. But false measures only make things worse. This is somewhere I think we have to admit to our ignorance.