calebhicks

The payback period begins when you get paid at a qualifying job, and pauses if your work does. (ie. Lose your job, or decide to move and takes a month or two to land new gig, etc)

The five year payment window clock starts on graduation. So if you don’t get a qualifying job within 5 years of finishing class, you pay nothing.

The LDS Church builds temples in an area _after_ there is a large enough group of members in the surrounding area to ensure the temple will get used.

There are very specific numbers used to determine where temples should be built. It is only an endorsement that there were enough nearby members to justify building one, not that members should move there.

This venture has nothing to do with the Mormon (LDS) Church other than the fact this guy is a member.

The leadership of the Church will not acknowledge or encourage the project in any official capacity, and will definitely not 'dispatch' members to live there.

The only exception being if there are actually 20k people, there may be a single pair of missionaries assigned to visit every now and then.

This post is directly addressed to the tech industry in Utah, but the ideas are universal.

It makes the argument for investing in junior tech talent. Thought it'd make for great discussion here on HN.

What is the right balance between investing in senior level developers, and investing in junior talent?

I love working in an industry where it's about what you can make or build on your own, not necessarily what your degree says.

As a past junior high teacher, I'm really excited about the new ideas around practical education.

Great question. I've been in public education for 4 years, and am transitioning to working at an iOS/Javascript bootcamp.

My experience from both has given me a firm belief that the best learning happens when the learner and teacher understand what the learner should know, and what they actually know, and helps bridge that gap.

If you can scale that, do it. If you can't, you're losing an essential element of what makes your program great.

I don't disagree. In fact, I agree completely with the author of the linked post. The symptoms he writes about are very real, and very damaging.

I just think it's hard to expect every teacher (even fresh ones, 4-6 years out of high school themselves), to remember these specific causes of what made high school a subpar learning environment.

Remembering that it was awful isn't the same as remembering, or appropriately identifying, why.

I'm in my 4th year of teaching, yet I graduated from high school 10 years ago. How well do you remember your daily schedule from 10 years ago? Do you remember what made you restless? What made you tired? What made you stop paying attention? And were you so meta cognizant that you recognized the source of that restlessness?

Doubt it.

It is rare for teachers to have the time to truly consider the student's perspective in their class, and the context of how that fits into the entire school day experience.

EDIT: I should note that I read this article a few days ago. The entire staff at my school held a discussion on how to make school better in that regard. This blog post alone will at minimum affect the 1400 students at our school, but given the number of places I've seen it shared, it will have a much larger impact than that. Always a good reminder.

The Big Nerd Ranch books are fantastic. Definitely check them out. I know they'll get something out for Swift sometime soon, but the iOS programming one would be a great foundation even with Objective-C as the sample code.

Some of the bootcamps will do financing. I'm against financing things that depreciate, but if you can get a decent job out of, it's not a terrible option.

Great question. I really love what I do at the junior high. I teach business and teen entrepreneurship. I love going into work in the morning.

But I loved my experience this summer. I love the thrill of writing, building, and seeing my code work. The creator's high.

My current plan is to take a year off from teaching next year and pursue an entry-level development job with a good local company. I'm only 27, so while I'm not sure development is the full-time career path I want to take, I definitely want to try it out. In the end, it will boil down to whether I enjoy waking up and going to work as much as I do now.