1. quotes
1.1. 5 Things
1.2. want it badly enough
1.3. difficult to be better
1.3.1. ...
1.4. Everything is impossible
1.5. Courageous enough
1.6. People who want to change the world
1.7. How to build a MVP
1.8. Dent in universe
1.9. experience
1.10. Sometimes you gotta run
1.11. Risk More than others think safe.
1.12. Life lived for Art is never a life wasted
1.13. The greats weren't great
2. CVGraphic Flow / Outline
2.1. **Who** is AR3?
2.1.1. Summary
2.1.2. Professional Pie
2.1.2.1. http://jsfiddle.net/alr3/wvkL44hm/4/
2.1.2.2. Tech
2.1.2.2.1. Ruby on Rails
2.1.2.2.2. Javascript
2.1.2.3. People
2.1.2.4. Process
2.1.2.5. Product
2.1.3. Outside of work?
2.1.3.1. http://jsfiddle.net/alr3/p3342mqk/2/
2.1.3.2. Personality
2.1.3.2.1. Might be worth having as it's own page
2.1.3.3. Naruto Shippudden
2.1.3.4. Poker
2.1.3.5. Reading
2.1.3.5.1. Rework
2.1.3.5.2. Entire Harry Potter Series
2.1.3.5.3. Linchpin
2.1.3.5.4. The Lean Startup
2.1.3.5.5. The Hunger Games Trilogy
2.1.3.5.6. The Entrepreneurial Rollercoaster
2.1.3.5.7. Pragmatic Programmer
2.1.3.5.8. Getting Real
2.1.3.5.9. The Divergent Series
2.1.3.5.10. Purple Cow
2.1.3.5.11. Poke The Box
2.1.3.5.12. Anything You Want
2.1.3.5.13. Start With Why
2.1.3.6. Fatherhood...not the sideline fatherhood
2.1.3.7. IndyHackers board
2.1.3.8. Indy.rb Co-Organizer / Presenter
2.1.4. 2 parts business, 2 parts tech, 1 part design, 3 parts servant leadership... with experience with the full product (and team) lifecycle
2.2. **Why** (What is AR3's Why...what drives him?)
2.2.1. This could be visualized with team on one side, and customers on the other??
2.2.2. People and their art.
2.2.2.1. inspire people to achieve their potential and deliver their art
2.2.2.2. empower and remove blockers for people trying to do their art
2.2.2.3. build tools that have an impact on those out there delivering their art
2.2.3. I want to help turn potential into real, usable, kinetic, shipped art
2.2.4. When your art is taking a digital solution to market, I have two philosophies...
2.2.4.1. Business = Impact + Sustainability
2.2.4.2. A successful project follows the rule of "The Hex" (an even more collaborative take on the agile manifesto), and brings all of the "Experience-Masters" to the table from the beginning
2.3. **Why** would you want an AR3?
2.3.1. The Hex
2.3.1.1. http://jsfiddle.net/22qdju47/2/
2.3.1.2. What is the Hex? After years of seeing project succeed and fail, The Hex is the AR3 take on what is necessary to build a great venture. A team of complimentarily focuses/skill sets that I like to refer to as the X-People. X for the different Experiences they will add to the success mix. Business experience = The folks that capture the essence of the problem that is being solved User Experience = Those that focus on the flow of the application from the users eyes. Visual Experience = True designers, artists, those with an eye to bring form to the function Application Experience = Engineers that write the business logic to make the app run Infrastructure Experience = Engineers that handle the servers and systems administration and security that house the app Quality Experience = Range of automated test engineers to Project Managers that ensure that quality is not just in the result, but in every step of the lifecycle
2.3.2. Can speak the language of...
2.3.2.1. Impact or the "Makers"
2.3.2.1.1. Fluent in the language of a large range technologists, from designers, to developers to infrastructure gurus
2.3.2.2. Sustainability or "the business"
2.3.2.2.1. Marketing
2.3.2.2.2. Finance
2.3.2.2.3. Business development
2.3.2.3. Technical Product Management blends the two worlds, and therefore must be able to speak the language of both
2.3.3. Technology leader focused on the people (team and customers), with a proven track record of delivering world-class solutions on-time and under budget, that has experience at the executive product strategy level. Ultimately, it is AR3's focus on the people that is the differentiator from his counter-parts. Your next question, may be How?...
2.4. **How** has AR3's track record of success been achieved?
2.4.1. ...in a word...People, specifically team
2.4.1.1. Been lucky enough to build, lead, and be a member of incredible teams throughout my career
2.4.1.1.1. Leadership
2.4.2. Agile
2.4.2.1. Hyper focus on working software as opposed to documentation (illusions of agreement)
2.4.2.2. Iterative, fast and continuous improvement
2.4.2.3. Building a culture of trust
2.4.2.3.1. frequency and automated tools make the failure blast radius small enough that team members don't feel like they have to be perfect...therefore they give more of themselves/their creativity/emotional labor
2.4.3. Creating a "Posture of We" between the technical and business areas
2.4.3.1. In many organizations the relationship between business and technology, specifically software is strained. I attribute this to a "toss the work over the wall" mentality, and have had great success in building a culture where everyone on the team will say "We delivered X", therefore creating a culture of collaboration instead of blame.
2.4.4. These have been hard, but fun lessons to learn over the many project, teams, and years of continually learning and adapting...
2.5. **What** has AR3 done, specifically?
2.5.1. ...companies/positions/projects has AR3 worked on, and in what capacity?
2.5.1.1. __Source__
2.5.1.2. Companies
2.5.1.2.1. Griffin Analytical Technologies
2.5.1.2.2. pan
2.5.1.2.3. Software Architects
2.5.1.2.4. UnitedHealthCare
2.5.1.2.5. ProTrans
2.5.1.2.6. Fusion Alliance
2.5.1.2.7. DeveloperTown
2.5.1.2.8. OurHealth
2.5.1.3. Entrepreneurship
2.5.1.3.1. iiiDGSolutions
2.5.1.3.2. New Us Movement
2.5.1.4. Roles
2.5.1.4.1. Jr. Software Engineering Consultant
2.5.1.4.2. Software Engineering Consultant
2.5.1.4.3. Sr. Software Engineering Consultant
2.5.1.4.4. Technical Team Lead
2.5.1.4.5. Software Systems Architect
2.5.1.4.6. Product Manager
2.5.1.4.7. Project Manager
2.5.1.4.8. Venture Technologist
2.5.2. ...has AR3 focused on/gained experience in over the year
2.5.2.1. http://jsfiddle.net/alr3/6u2wpLL0/4/
2.5.2.2. http://jsfiddle.net/alr3/ju0rqjpv/
2.5.2.3. Team Leadership
2.5.2.3.1. Organizational design
2.5.2.4. Process Leadership
2.5.2.4.1. Agile
2.5.2.4.2. Scrum master
2.5.2.5. Product Management
2.5.2.6. Executive/Strategic
2.5.3. Software Engineering
2.5.3.1. http://jsfiddle.net/alr3/9z018mv7/
2.5.3.2. Web UI
2.5.3.2.1. Javascript
2.5.3.2.2. CSS
2.5.3.2.3. HTML
2.5.3.3. Ruby
2.5.3.3.1. Rails
2.5.3.3.2. API
2.5.3.4. Mobile
2.5.3.4.1. Web (Responsive design)
2.5.3.4.2. Native Apps (using Titanium abstraction)
2.5.3.5. .Net
2.5.3.5.1. C#
2.5.3.5.2. VB
2.5.3.6. Other Languages
2.5.3.6.1. Java
2.5.3.6.2. PHP
2.5.4. Associations
2.5.4.1. IndyHackers
2.5.4.2. Indy.rb
3. CVGraphic SVG graphs
3.1. http://ar3.me/charts/professional/?width=900px&height=600px
3.2. http://ar3.me/charts/thought_shift/?width=900px&height=600px
3.3. http://ar3.me/charts/nonwork_life/?width=900px&height=600px
3.4. http://ar3.me/charts/software_history/?width=900px&height=600px
3.5. http://ar3.me/charts/hex_comparison/?width=900px&height=600px
4. Essays from "Next Adventure" Search Process
4.1. bp-spo
4.1.1. What’s the most interesting project you’ve worked on?
4.1.1.1. The most interesting project is a tough question, because I’ve had the good fortune to work on many different projects, teams, and ventures over the years. However, the portal rewrite project that I was tasked with at OurHealth was the most complete test. By that I mean, this project tested nearly every aspect of my experience up to this point. The goal was to build a team, define a process, design a product, instill an agile mindset in a traditionally heavily-waterfall-influenced industry/company, and do all of this with a deadline that could not be moved or missed without significant business impact (and the deadline was 7 months). We were able to accomplish an incredible amount of productivity, and ultimately went live with the first real client 7 days earlier than anticipated. The project was/is a portal and custom enterprise practice management system that supports all of the non-health-record operations. This includes, but is not limited to; the most sophisticated/customizable employer-based wellness incentive platform on the market, a back office work queueing system that integrates all of the operational “ToDo”’s into a role-aware and separated queue, all with an industry-best patient user experience. I played the role of product manager (I wrote and prioritized 90% of the stories), project manager (installed an agile methodology using stories, points and epics all managed using PivotalTracker), software team lead, and co-architect. Though the technical feat was incredible, the thing I am most proud of is the people; the internal team (how amazing they were in giving more than we could have asked of them to complete this task), how much praise the end-users/patient had for what we delivered, and how the platform was received by the internal OurHealth operations crew.
4.1.2. What’s your most despised agile anti-pattern?
4.1.2.1. I have been an agile evangelist for many years. In that time I’ve had to stand on a soap box and preach the ways of “true agile” more than a few times in my career. Which leads me to my top despised anti-pattern, in that the process itself must remain static and is not subject to any scrutiny or is so rigid that it misses on the opportunity for greater success. For me, true agile measures and learns from everything, including the tools and process itself. That last one is a bit amorphous, so a few others are; not having retrospectives, dictating velocity instead of measuring it, and ultimately really doing waterfall and calling it agile. Retrospectives are key…can’t learn if you don’t look at what worked, and what didn’t work. Not to mention it creates a strong team culture. To me, velocity is descriptive, not prescriptive. At the executive level, you have to forecast and resource plan; but trying to do that with overly precise velocity mandates just makes it so that the velocity is no longer measuring the effort/complexity, but team members are just trying to hit their numbers in any way possible, whether that is modifying the estimates or leaving certain crucial tasks out, like automated testing. Finally, given the buzz-wordiness of the agile ecosystem, many teams still do all of the requirements gathering up front, and use a gantt chart-style view of how a project will be completed, and during the ‘build’ phase, the tech team is micro-managed by having 2-4 week check-ins (that are not about working software, but instead making sure that ‘velocity’ is remaining at a high level), that are inappropriately called sprints. Stepping down from the soapbox now :-)
4.1.3. What are your favorite tools right now? Why?
4.1.3.1. My favorite tools are: PivotalTracker, Flowdock, BaseCamp, and SublimeText. PivotalTracker in it’s opinionated nature fits really well with how I like to run projects. It lends itself to getting to work, and not having to have a week long training on how work flows through the system. The only thing I wish was a little better is reporting (though I’ve toyed around with their API, and think many of my wants could be solved using this), and what environment a story is in (CI, QA, Staging, Production, etc). Love this tool. Flowdock, though seemingly being beat up a bit by the popularity surge of Slack, is still my favorite communication tool for a team. Ultimately, an interruption based environment is toxic to productivity, and Flowdock is perfect at pinging someone, and not necessarily needing a response at that moment. It also encourages a culture of transparency. BaseCamp is great when you have a lot of business folks involved, because in my experience, they seem to be intimidated by PivotalTracker. The simplicity of the todo’s and the calendar are extremely valuable. (Love the company and what they are about as well…ReWork is my all-time favorite book across all genres). Finally, SublimeText is an incredible tool to write code, modify csv’s, and just generally write with.
5. Thoughts
5.1. Blog posts / essays
5.1.1. My journey into Product-Thinking
5.1.2. Write-up on a recent project
5.1.3. My take on inertia in Business pursuits
5.2. Publications
5.2.1. UnfadingPursuit
5.2.1.1. A blog about my journey towards being the best I can be. My personal potential fulfillment journal. You will find my take on software venture delivery, my take on controversial topics, and just general stories about the journey...no the unfading pursuit for greatness.
5.2.2. PotentialRealization
5.2.2.1. A blog about how horrible our systems of making sure that each of us are fulfilling our potential. We have greatness in us, and if we are able to find the right environment magic happens.
5.2.3. Old UnfadingPursuit
5.2.3.1. Here is an old version of the UnfadingPursuit. I've since moved over to Medium, but my earlier writings are hosted here.
6. plain_ole_resume_v2
7. plain_ole_resume_v1
8. Contact AR3
8.1. [email protected]
8.2. https://www.linkedin.com/in/arthree
8.3. https://twitter.com/ar3_me
8.4. https://github.com/ar3
8.5. http://nownownow.com/p/841j
8.6. https://www.goodreads.com/user/show/45712166-andrew-robinson-iii
8.7. Misc Links
8.7.1. https://www.facebook.com/arthree
8.7.2. https://angel.co/ar3
8.7.3. http://stackexchange.com/users/319167/ar3
8.8. Unkept Links
8.8.1. http://andrewrobinsoniii.brandyourself.com/
8.8.2. https://about.me/alr3
8.8.3. https://www.producthunt.com/@ar3_me