Peter Pavlovich

CTO, Censinet

Peter Pavlovich
   

Peter is the CTO of Censinet, based in Boston, MA.

Before joining Censinet, Peter was the Chief Software Architect at Embue Technologies, an Apartment Building Intelligence platform provider based in Boston, MA. Before joining Embue, Peter was the Principal Architect for EnerNOC Labs, a dedicated R&D group within EnerNOC, a Global provider of Demand Response and Energy Inteligence software located in Boston, MA. Prior to EnerNOC, Peter was a Principal Cloud Engineer with Kronos Incorporated, a global provider of on-premise and cloud-based workforce management solutions. Before Kronos, Peter held the position of Technical Director with Brokat Technologies, a global provider of mobile payment solutions. Prior to that, Peter was a Sr. Architect with GemStone Systems, providing distributed, enterprise-ready data grid and object persistence solutions and J2EE application server technologies.

Peter has a Honors degree in pure mathematics from McMaster University in Hamilton, Ontario, Canada. He is a technology addict and evangelist and has led many grass-roots efforts to introduce leading edge, advanced technologies and development processes.

A lifetime learner, Peter thrives on digesting new technologies and sharing his discoveries with others. He has authored and delivered numerous technical seminars on a variety of topics including React, VueJS, Angular, Ruby on Rails, Grails, Git, Meteor, Flex, GWT and AOP.

To find out more about Peter, check out his LinkedIn profile: https://www.linkedin.com/in/peterpavlovich

Presentations

JavaScript Blueprints: Client-side architecture patterns

Tuesday, 1:30 PM EST

Client-side JavaScript can get out of control easily. This session explores practical architectural solutions targeted to make your client-side JS easier more reliable, easier to develop and more performant.

Front-end developers love their JavaScript. It is sleek, powerful and very cool. But how do you architect a strategy for dealing with the (tens of) thousands of lines of code your developers will eventually write not to mention the countless JavaScript libraries your developers want to add to your projects? How do you divvy up the code and organize things in a logical way so that you can find specific code easily? What about namespacing concerns? File management and dynamic loading? Writing libraries for use on both client and server? What tools are available to help you address some of these concerns?

Join us as we explore these and other JavaScript client-side architecture dilemmas.

JavaScript Blueprints: Server-side architecture patterns

Tuesday, 3:15 PM EST

Server-side JavaScript is everywhere these days! This session explores some practical architectural techniques and tools that can make your server-side JS easier to develop, test, manage and deploy.

Server-side JavaScript is part of almost every modern web app's tech stack. It is a powerful, versatile tool you can leverage to solve virtually every problem you can image. Its versatility and popularity guarantees that, once introduced to your organization, you will soon have a plethora of server-side JS applications to manage. This poses a number of problems for an enterprise architect: How do I maximize reuse across projects? How do I even enable reuse in JS? Are there best practices I should follow? How do I manager 3rd party libraries? Are there coding practices, patterns or standards I should adopt and champion across my teams? What about name spacing concerns? What about packaging and deployment? What if I write libraries for use on both client and server? What tools are available to help you address some of these concerns?

Join us as we explore these and other JavaScript server-side architecture conundrums.

Angular Architectures: A roadmap for the hearty traveller

Wednesday, 9:00 AM EST

There is no doubt that Angular is now mainstream. That made it easier for you to convince the powers-that-be to let you select Angular for your project. You've done a small but successful POC and now your 'big' project has been green lighted to kick off next month. Your team is jazzed but as you start to plan out the real work, you begin to realize that there are many aspects inherrent to large Angular projects that have no 'out of the box' answers.

Stack overflow can only contribute 'it depends' answers that leave you more confused than before you read them. And now the panic starts to seep in, killing your buzz. Never fear! In this session, we will explore a variety of ways to architect your project and structure your code. We will look at the pros and cons of each option and discuss when trigger points for choosing each.