Daugherty

I work at Daugherty Business Solutions at the Minneapolis / Saint Paul branch as a Software Engineer 2 and Consultant.


Work Updates

July: Week 69

  • Built an intermediate API to fetch data from GitHub API v3 and decorate incoming data with custom data fields for use in a dashboard app.
  • Enhanced a ReSTful API by using the DTO pattern to decouple domain entities and exposed interfaces to clients and reducing complexity of circular data references.
  • Refined an existing Vue based application…
    • added more aesthetically pleasing designs for searching, filtering and increased usability by reducing visual noise.
    • added Google Analytics tracking for pageviews and application specific events to track usage and monitor goals of the application
  • Started exploring react native application development.
  • Conducted technical interviews for frontend software engineers.

June: Week 64

  • Built a Vue CLI template to help bootstrap Vue based prototypes with out of box branding, theming, basic layout components, utilities and more.
  • Assisted the presentation of the charting demo to a consortium of interested business unit leaders to demonstrate business potential and viability as a product.
  • Built and demonstrated an alternative version of a solution using the capabilities of a reference blockchain implementation for marketing purposes that could increase brand coherence, trust and value.

May: Week 59

  • Worked on a Vue based user interface to display scatter and radar charts with data sourced from uploaded CSV files and transformed in the Java API layer dynamically based on incoming type of data that helped prove business need and viability.
  • Participated in Daugherty’s private HackerX event, speaking to more than eighteen potential candidates over the course of the night.

April: Week 54

  • Worked on a supply chain resource tracking tool, using the capabilities of a reference blockchain implementation, to demonstrate the value of a decentralized system such that multiple entities can have a stake in the system, and can be ensured that the manipulation of the data after entry is non-trivial.
  • Attended my third business unit meeting, and gave a brief demo of some our team’s project work.

March: Week 52

  • Presented at the Daugherty Office, a presentation on Vue that explained the basics of Vue with a workshop, and explored some of the more complex topics in the Vue ecosystem, like routing, state management and the tooling.

March: Week 51

  • Attended a local HackerX recruiting event with the Daugherty team, spoke during our introduction on stage, and briefly talked to more than sixteen attendees.
  • Participated in a discovery project for multiple large business units to determine if the consolidation of business logic and user experience among thier respective existing systems could be provided by a single portal user interface.

Late February: Week 49

  • Completed a Progressive Web App for the prototype project, built with built with Vue, Vue Router, Vuex, Webpack, Bulma and more, featuring…
    • desktop and mobile responsive design
    • offline assets through AppCache
    • offline data with periodic refreshing
    • connection aware conditional flows
  • Conducted additional technical interviews for new software engineering candidates.

February: Week 44

  • Began a new engagement at a client site, and starting the requirements gathering phase of a prototype application that will digitize existing paper forms regarding safety procedures.

January: Week 43

  • Debuted a short Vue talk about Vue CLI and using Vue Components at JavaScriptMN, the regional monthly JavaScript meetup event.
  • Presented a copycat presentation for various Dev Center and client site developers at the first Dev Center + Client Site developers collaboration day.

January 1st, 2017: Week 39

  • It’s a new year!
  • Explored the internals of Spring and conditional beans by creating an implementation of “interior authorization”, to intercept incoming JWTs in request headers of internal services in a microservice architecture app, and inflate Spring Security information using the intercepted JWT.

December: Week 35

  • As a side project between engagements, developed with the team a practical asset to our physical Dev Center space: a simple database-less websockets Spring Boot backend and Vue frontend web app that shows on the wall-mounted Dev Center screens whether or not important managers are in the office, busy or available.

November: Week 32

  • Participated in team development on an internal project focused on extracting data from git repositories and showing the activity of the development team in an easy to read at-a-glance format, using a polyglot microservice backend architecture, and an AngularJS frontend.
  • Began the on-boarding process to help development on a project management organization application that would transform the existing workflow with a modern and robust interface, primarily based on a Spring Boot microservice backend architecture, and an Angular frontend.

October: Week 28

  • Developed an extension to a previous project that would significantly enhance audit logging in the web application leveraging AspectJ to perform unobtrusive uniform capture of per user data — user keys, usernames, permission templates, inherited roles, etc., Filebeat and Logstash for moving log data and processing transformations and Elastic Search for dynamically handling user action queries on the audit dataset.
  • Attended my second business unit meeting, and I even received an awesome award.

September: Week 23

  • Worked on a 5 week engagement adding new functionality within the constraints of an existing legacy web based application built with Google Web Toolkit, IBM DB2 and Spring 3.
  • Attended the University of Minnesota CSE Job Fair to recruit soon-to-graduate students.

August: Week 21

  • Nearing the end of a 15 sprint engagement spanning over the last few months, finished building various major features with the help of a great team, primarily with customized Spring Security implementations…
    • including sponsored users with inherited permissions.
    • dynamically switching between sets of application defined permissions.
    • dynamically generated forms for customizable authorization.
    • two types of registration flow enabling automated and manual registration.
  • We moved office spaces again – with the opening of the new and recently remodeled Daugherty Dev Center 2.0.
  • After the mid-year review, I was promoted! From Software Engineer 1 and Associate Consultant, to Software Engineer 2 and Consultant!

July: Week 14

  • Built various command line utilities for the team using npm, gulp, browserify, sass and more, to compile the growing dependencies needed to build a Knockout.js based client side application, and made reusable Knockout.js components.
  • Based on the outdated preconfigured virtual machine a previous team member created, I created an up-to-date Xubuntu 16.04 virtual machine image preloaded with our development stack: IntelliJ Community, MySQL, Java and more.
  • Over the last few weeks, I acted as the leader of the Accelerator 2.0 program — the training program Daugherty uses to on-board new hires, hosting an example project for a great group of three recent college graduates that was essentially a Twitter clone, using the a common stack, Java, Spring, MySQL and Knockout.

Late May: Week 9

  • I worked on a backend service layer for the foundation of an Account Management RESTful API.
  • In conjunction with the backend layer, I created components of the client side consuming application written in Knockout.js.

Early May: Week 5

  • Daugherty had their bi-annual business unit meeting, where our founder, Ron Daugherty, spoke.
  • I have left my Kitchen quarters, and now work in a team of now 12 on a greenfield project established in January.

March 28th, 2016: Week 1

  • Daugherty’s recruiter team found me at the UMN CSE Career Fair, allegedly — though I have no recollection of that event.
  • I went through three interviews, one on UMN campus with a Daugherty recruiter, and two in person at the office, first with a regular software engineer, a manager and another recruiter, and the second with a senior application architect.
  • I am consultant № 101 at this branch!
  • I work in the Kitchen.
  • Here are some photos from my first week at Daugherty.

Two final notes:
  1. If you have an interest in Daugherty, let me know. Apparently, you can get a referral, and we all win.
  2. So we are all clear, all thoughts are my own, especially the good thoughts, and do not represent Daugherty.