Skip to main content

Nebraska Code 2015

A year ago I started this blog after Nebraska Code Camp with a review of the sessions I attended. I want to just highlight the sessions I went to this year that I thought were good. This year I felt like I gained the most out of the sessions that were not targeted toward a specific language or tool, but rather the ones that would help me be a better person and become a better developer in general.

I have been listening to the .NET Rocks podcast for a few years now, so I was really excited to get to see Carl and Richard record an episode live. It was a lot of fun as well as educational to watch them work and see how they put together a show. The guys were smart and funny, they clearly have great chemistry and can seamlessly flow in any direction the conversation takes them.

I attended a session titled, "How to Learn: Grok it Faster". I really enjoyed this session. The speaker was Thuy Copeland, she did a really good job with her entire presentation. She recommended the book: 5 elements of effective thinking, by Edward B. Burger and Michael Starbird. The main pieces of information that I took away from this speech were:

  • Focus on Fundaments when practicing, if you want to learn how to type, practice typing with fingers on the home row rather than hunting and pecking.
  • The sweet spot for learning is when you are frustrated, you know what you want to do but are failing about 50% of the time. If you aren’t failing then you aren’t learning and if you are doing nothing but failing then you are accomplishing anything
  • When reading a technical manual, just read what you need to know right now. Look through the index for terms you need to know. Skim the first sentence of chapters and then paragraphs. If you end up reading an entire paragraph then you have found what you were looking for.
  • After you have learned something, try to recall it someplace that it would be out of context, like waiting in line at a grocery store. By remembering something in a different context you strengthen your memory and you will more easily be able to recall it in the future.
I also really enjoyed the session from Jen Homann about the science behind why we procrastinate and what you can do about it. This speech had a ton of great quotes, as well as a bunch of useful knowledge behind those quotes. Some of my favorites were:
  • "What you want for future you is not what future you will want". So if you need something done, do it now or it may never get done.
  • "Future you cannot be trusted"
As with everything I learn, breaking things into smaller pieces will help you accomplish your goals. If you have something too large to think you can accomplish you will put it off until you really can't accomplish it, sort of a self-fulfilling prophecy. When you don't know how to start something, start with finding a small piece that you can complete.

Always keep the big picture in mind. Whatever you want to accomplish does not have to be perfect for it to still be a success. Even a failure can be more progress than not starting at all.

Forgiveness is not for someone else, it is for you to get well and move on. If you fail at something, you need to be able to forgive yourself and forgive anyone else or anything that lead to that failure. Then you can grow and move on the next adventure. Practice self forgiveness, acknowledging what went wrong and accept responsibility for it. Be honest enough with yourself to change your behavior.

I feel like I will take a lot away from this conference and use the knowledge that I gained to make myself better. Nebraska Code Camp is a great place to meet new people and new ideas. Can't wait for next year.


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