Just a reminder that we're having a tech talk in Mountain View, CA this next week. If you have time, head over to the lds tech site and register so we know how many people to expect.
I'm moving out to Silicon Valley for an internship, and really wish I could come, but alas I'm not going to be out there in time.
Anyways, Joel came to my Computer Science class here at BYU and spoke to us and answered some questions about being a former Microsoftee and working for the church, and it was fantastic. Anyone in the area, who can make it out, please do it'll be worth it.
That aside, I had another question: While being careful with tithing funds is one of you're most important guiding principles, how do you combat the "just trying to save a buck" mentality that brings in questionable hardware and services? I find that tends to be the major source of failure among penny pinchers.
[Joel: I had a blast, visiting CS 404, Adam. Tecnology decisions have multiple variables which influence cost and we have to consider them all. If we "save a buck" in the short-term by buying cheap equipment or doing cheap implementations then we're not truly saving a buck. Being aware of those long-term trade-offs is the first step to making the appropriate decisions.]
I'm moving out to Silicon Valley for an internship, and really wish I could come, but alas I'm not going to be out there in time.
ReplyDeleteAnyways, Joel came to my Computer Science class here at BYU and spoke to us and answered some questions about being a former Microsoftee and working for the church, and it was fantastic. Anyone in the area, who can make it out, please do it'll be worth it.
That aside, I had another question: While being careful with tithing funds is one of you're most important guiding principles, how do you combat the "just trying to save a buck" mentality that brings in questionable hardware and services? I find that tends to be the major source of failure among penny pinchers.
[Joel: I had a blast, visiting CS 404, Adam. Tecnology decisions have multiple variables which influence cost and we have to consider them all. If we "save a buck" in the short-term by buying cheap equipment or doing cheap implementations then we're not truly saving a buck. Being aware of those long-term trade-offs is the first step to making the appropriate decisions.]
I was unable to make this TechTalk. I am curious how it went?
ReplyDelete[Joel: It was fun. There were around 40 people there. Some great discussions and questions.]