Skip to main content

Heartland Developers Conference 2015

I had the opportunity to attend the Heartland Developers Conference this year. I had a really good time. I got to learn from really smart people, catchup with friends, and meet some new people.

The biggest takeaway I had from this conference was how to evaluate which session to go to. With the first few sessions I attended, I tried to find topics that I already had familiarity with hopes of getting deeper understanding. I came to the conclusion that that was not a good approach. The sessions at conferences are not able to dig very deep into a topic. There just isn't enough time for the speakers to cover a lot of ground. So I changed my plan for which talks to attend and chose the ones on topics that I had no knowledge of. This worked out much better for me. I found a lot more new information and generally enjoyed the sessions more.

I will highlight some of the other items that I found interesting below.

Swagger is an open source abstraction for documenting your REST api with a JSON response. It is available for practically every platform.

HTTP2 is coming, already available on some platforms. Should help reduce overhead of web requests. Shrinks the size of headers. If a header value is unchanged, it does not need to be sent. The server will know if you request an HTML page that you will be requesting CSS and JS files next, and begin sending them before the client requests them. It will be able to do that through remembering how previous requests were handled, not by parsing the HTML file. The client can also tell the server if it has a cached version of a file and does not need it. Sounded like it will make some really nice improvements without breaking how things work currently.

Cory House gave a talk on "Owning the technology adoption curve." I really enjoy his talks, every session I have attended by him has been really great. He detailed the adoption curve, from early adopters through mainstream and to strategic laggards. Each spot had its positives and negatives. The biggest thing I took away from this session was, "Don't have a fixed mindset. You can learn anything if you work toward it." The example he gave to further explain this concept was, "Don't say I am shy and awkward. Say I need to work on my social skills." I think too often people assume that someone that is successful just has a natural gift, but they have worked hard to get as good as they are. If you know that you have a weakness or if you are not as good at something as you would like to be, realize that you can get better. It may not be easy to improve, but if you work at it you will get better.


Popular posts from this blog

Converting a Large AngularJS Application to TypeScript Part 1

I work on a project that uses AngularJS heavily. Recently we wondered if using a preprocesser like CoffeeScript or TypeScript for our JavaScript would be beneficial. If our team is going to switch languages, we would need to be able to convert existing code over without much pain and we would have to find enough value in switching that it would be worth the conversion. I had read an article that stated that because TypeScript is a SuperSet of JavaScript, you could convert a plain JavaScript file to TypeScript by changing the extension to .ts and not much else would need to change. I wanted to test out this claim, so I took a file that I was familiar with, an Angular Controller, and tried to convert it to TypeScript to see how much effort it would take and then try to figure out where we would benefit from using TypeScript. This is what the controller JavaScript file looked like to start out with: ( function () { 'use strict' ; angular .module( 'app'

Interns: Taking off the training wheels

My intern team has been working for several weeks now on our new website. We have already completed one deployment to production and are finalizing our second one. We started with a plan to release often adding small bits of functionality as we go and so far that plan has been working really well. We already feel like we have accomplished a lot because we have completed many of our project's requirements and should easily be able to complete the rest giving us time to do even more than just the original requirements. One of the things I have had some difficulty balancing has been how much to lead the interns and how much to let them figure out on their own. In deciding what our team process should be and how we should allocate our time, I think it was important for me to do more leading. I saw some deficiencies in how we were currently working and brought up some ideas for how we could address them. We had moved into spending all our time just working through stories and did not

My idea for Hearthstone to add more deck slots

Recently someone asked the Blizzard developers for more slots for decks in the game Hearthstone. The response was that they are talking about it and looking into it, but no decision has been made yet. One of the concerns over adding deck slots is that it could complicate the UI for Hearthstone and make it more difficult for new players to understand. I have what I think would be a good solution to add more deck slots without increasing the learning curve for the game much if at all. First I would take a look at the current selection screen for starting to play a game. It defaults to showing the decks that are custom built by the player if they have any custom decks, and there is an option to page over to the basic decks. This basic deck screen is perfect for how I would change this process. Instead of having 2 pages of decks, 1 for basic and 1 for custom, you would just see the select a Hero screen. Then once you selected the Hero you wanted, you would see all of the decks that