WELP NOW EVERYONE ALREADY KNOWS SINCE I USED THE CC FIELD TO FIND THE ADDRESS AND YINZ ALSO KNOW PGHRB NEEDS SPEAKERS.
Go apply for Andrew's job, people.
This has been your Carol Is An Idiot Moment Of The Day. Thank you and good night.
You received this message because you are subscribed to the Google Groups "Pittsburgh Ruby Users Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubypgh+u...@googlegroups.com.
To post to this group, send email to rub...@googlegroups.com.
Visit this group at http://groups.google.com/group/rubypgh.
For more options, visit https://groups.google.com/d/optout.
Also, I'll totally give my service building talk in the next available slot as long as it's not February. :)
You've learned about Service Oriented Architecture. You want to use it. You know the benefits to testing speeds, to team velocity, and page load (why do in sequence what can be done in parallel?).
Problem is, you're tearing your hair out trying to figure out how to actually pull those services out of your monorail.
This talk isn't about the overview. This isn't about the metrics to determine what should be pulled out into a service.
This talk isn't even about optimizing the service you pull out. This talk is a step-by-step approach about how to successfully pull that service,
embedded in your app, out so it can be the best little service it can be, and you can get back to that velocity that your managers keep saying "we used to be able to do".