Upgrade to Pro — share decks privately, control downloads, hide ads and more …

How to become a better software company technic...

How to become a better software company technically

I was in Kathmandu,Nepal for a week at the end of November and this time I talked about how to become a better software
company technically at YIPL done on 24-Nov-2014.

Generally the software scene in Nepal is good, a handful are working at big scale with hundreds of software engineers
and many are small with some developers. A thing I noticed talking with developers is that mostly is only about **making
things work**. The need to follow a proper release cycle with gitflow, or even follow a
defined issue flow and testing it in multiple environments is not felt.

Geshan Manandhar

November 24, 2014
Tweet

More Decks by Geshan Manandhar

Other Decks in Technology

Transcript

  1. WILL TO IMPROVE IS AN ATTITUDE NOT A ONE TIME

    JOB, REQUIRES LOTS OF PRACTICE AND PERSISTENCE.
  2. THINK OF 3 THINGS THAT YOU THINK WILL IMPROVE YIPL

    TECHNICALLY TELL ME THE NO. 1 IN YOU LIST
  3. PROCESS MANAGEMENT ISSUE FLOW Kanban based Supports scrum Best of

    both GITFLOW Check VCS best practices Simplified Full BOTH ARE INTERRELATED.
  4. SOFTWARE QUALITY QA TOOLS Follow by PHP-FIG - use ,

    and PSR standard CS Fixer Security Checker Codacy.com AUTOMATED TESTING with check for reference PHPUnit Mockery Jumph Possibility of using Behat CONTINUOUS INTEGRATION ( ) CI or GitLab CI Shippable.com
  5. SOFTWARE QUALITY LOGGING AND MONITORING Log activities with or GrayLog

    Logstash Monitor real-time with NewRelic COLLABORATION AND DOCUMENTATION Code Review Pair Programming Document Important Things
  6. AUTOMATION VIRTUALIZED ENVIRONMENT - Dev and Production Docker - generally

    dev Vagrant AUTOMATED DEPLOYMENT Capistrano GENERAL AUTOMATION When you push to GitLab, a notification is triggered in a bot room in Hipchat When you push to GitLab, it automatilly pushes to Bitbucket and runs the build Hipchat is notified about deployment start and progress
  7. RECAP We need processes to improve developer productivity It takes

    some time for following processes to become a habit. Reading and implementing best practices is one of the best practice. It's not only about the tools/technologies. It's also about how you use them. I am suggesting ideas that could help improve YIPL technically.