Build software like you build houses

Interfaces facilitate visibility.

Software is the only engineering practice that doesn't allow runtime visibility to end-user.

If this were true for construction, it would mean your builder would have to live with you for you to even guess what the problem is.

https://vimeo.com/221049715

https://github.com/stripe/veneur

Comments

Microservices Design Patterns

functional decomposition or domain-driven design well-defined interfaces explicitly published interface single responsibility principle potentially polyglot http://blog.arungupta.me/microservice-design-patterns/ http://blog.arungupta.me/microservices-monoliths-noops/ https://go.forrester.com/blogs/13-11-20-mobile_needs_a_four_tier_engagement_platform/ three-tier architecture — presentation, application, data vs. 4 tier -- client, delivery, aggregation, services

JSON stores and Aggregation for system logs and audit trail. Stop logging with format strings!

This first article explains why you might want to store logs and BI data in a machine readable format. https://journal.paul.querna.org/articles/2011/12/26/log-for-machines-in-json/ The second two get at how you might do that and be able to transition/re-purpose your existing relational stores into a cloud based scalable framework. http://docs.mongodb.org/ecosystem/tutorial/use-aggregation-framework-with-java-driver/ http://www.bityota.com/3-steps-to-analytics-on-mongodb/ Logging might present a relatively low profile target for schema-less implementation and give you a chance to expose your organization to an important technology for modern web development. With your foot in the door you might convince them to add usage auditing and before you know it you are doing up front analysis on usage in front of your next project.

homebrew, git

IN PROGRESS - Steps to contribute a cask to homebrew. Also a good way to stay in touch with git use if you don't have it at work. https://github.com/caskroom/homebrew-cask/blob/master/CONTRIBUTING.md#getting-set-up-to-contribute 1: Fork the repository in GitHub with the Fork button. create or login into your github account use the Fork button at https://github.com/caskroom/homebrew-cask A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project. Most commonly, forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea. Now get a 'remote' local copy of the fork you must have git installed comes pre-installed on later osx versions can switch to most current with homebrew - $brew install git $ github_user= ' <my-github-username> ' $ cd " $( brew --repository ) ...

yak butter recipe

Search This Blog