A Report on process Assessment for open source projectsKiyoshi Ogawa
GCC, Linux, Apache, TOPPERS, and mruby projects are now assessed for benchmark. Before this activity, TOPPERS/ssp was assessed by SPA Nagoya Study Group members. Some reports are already uploaded to JAXA/IPA Wocs web.
360iDev Presentation this year:
As a contract iOS programmer, I spend about 80% of my time working with other people's iOS code - either working as a part of existing teams or taking over incomplete projects from developers who are no longer around. Along the way, I've gathered a list of the common mistakes I've seen people make, the open-source libraries I've seen people misuse the most, and the really simple code changes that can make huge differences in the reliability and performance of your apps. For each mistake or anti-pattern, I'll have an explanation of the issue with it, and at least one potential remedy or remediation that could be taken.
This talk will have a lot of specific code examples on a number of different topics and technologies, so hopefully everyone will learn something. And hopefully at least something will save you some time.
Note that this will be a very opinionated talk, and I'm quite likely to step on someone's pet pattern, so there may be fireworks.
A Report on process Assessment for open source projectsKiyoshi Ogawa
GCC, Linux, Apache, TOPPERS, and mruby projects are now assessed for benchmark. Before this activity, TOPPERS/ssp was assessed by SPA Nagoya Study Group members. Some reports are already uploaded to JAXA/IPA Wocs web.
360iDev Presentation this year:
As a contract iOS programmer, I spend about 80% of my time working with other people's iOS code - either working as a part of existing teams or taking over incomplete projects from developers who are no longer around. Along the way, I've gathered a list of the common mistakes I've seen people make, the open-source libraries I've seen people misuse the most, and the really simple code changes that can make huge differences in the reliability and performance of your apps. For each mistake or anti-pattern, I'll have an explanation of the issue with it, and at least one potential remedy or remediation that could be taken.
This talk will have a lot of specific code examples on a number of different topics and technologies, so hopefully everyone will learn something. And hopefully at least something will save you some time.
Note that this will be a very opinionated talk, and I'm quite likely to step on someone's pet pattern, so there may be fireworks.
Invited keynote on Software Symposium 2010 Japan. Talk about history of software engineering and the role of agile. Corrected recent words from Tom DeMarco, Ed Yourdon, Mary Poppendiec, Tom Gilb, Ivar Jacobson, ... and my thoughts.
Invited keynote on Software Symposium 2010 Japan. Talk about history of software engineering and the role of agile. Corrected recent words from Tom DeMarco, Ed Yourdon, Mary Poppendiec, Tom Gilb, Ivar Jacobson, ... and my thoughts.