Your manager says that he/she wants the digest of the commit you have just made before pushing the code to the repository. He/She will review it and tell more about it. You can probably zip your changed files and send him/her to review.

Git provides a nice alternate, the git patch files. How to do it:

1) git add

2) git commit -a

3) git format-patch -1

-1 says that you want to create a patch file containing all the git diffs) for the last commit at the project root.

-2 creates a patch file for 2 most recent commits and so on.

Now, he/she can just do

git apply <patch file path which you probably emailed>

That would create an exact same commit at his end and then she can see all the code that you have just written for a new critical feature/bug.

Multi-channel real-time data from distributed sources help in making right decisions. Coupled with the collaborative platform, having access to real-time data has significantly improved plant managers’ responsiveness to alert situations. Still, it requires enough human reasoning and experience to take the right decision if such a system is not adequately supported by proper analytic system. Data streams can be in temporal, spatial, or  dual mode. A real-time decision management system must incorporate advanced analytic system to correlate data streams from multiple channels and enable a quick and near-accurate predictive alerts in order to avert serious consequences.

Most software services and consulting companies are investing in COE to build and enhance capability in emerging technology stacks. COE is becoming a very important precursor for sales strategy and execution of revenue generating projects. I want to distinguish regular software delivery model from the COE model. Software delivery lifecycle process has evolved and matured over last several years. In contrast, COE delivery lifecycle is not fully explored yet. COE primarily undertakes tasks which are associated with emerging technology stacks or business processes- therefore, COE are invariably linked to research and exploration activities. COE delivers representative prototypes, proof of concepts, prescriptive architecture and best practices. How will you measure the ROI? In a business scenario, unless COE demonstrates clear ROI, the sustainability of COE becomes untenable. Success of COE critically depends on quick ROI (generally industry is not very patient!), and a good business case to support monetization in one form or the other.

COE Management Tips

• Strategy
  • Identify executive sponsorship toward success of COE goals
  • Sales driven – Monetization plan on successful execution of such use cases
• People/Process/Execution
  • Passionate team for COE
  • Fixed tenure
  • Short, incremental, and iterative release cycles
  • Regular Scrum like reviews
• ROI Demonstration

The evolution of Grails in last year has been significant. This is mostly positive. About 2 years back, I tried hard to push Grails as a development environment while I was engaging in discussions with several VP, Engineering or CTO. There were questions and concerns about scalability, performance, and productivity. I believe Grails has addressed all successfully over two years. The adoption rate is increasing. More enterprise Java programmers are being trained on Grails framework. The domain-driven programming features along with the power of plug-in repository and contemporary test/integration mechanisms open ways to build scalable applications in a shorter time cycle with higher quality guarantee. The Agile development methodology aligns well with Grails powered development lifecycle.