Spend some time in front of a classroom and you will quickly recognize the main flaw with most educational technology products: they aren't made by teachers. Teaching is a remarkably distinct skill set. In a typical high school classroom a teacher's classroom tasks include but are not limited to simultaneously taking attendance, watching hallways, monitoring behavior, executing lessons, managing student actions, verifying student learning, differentiating student instruction, and providing students with feedback on their day's work. A teacher is responsible for these tasks and other for up to 7 50 minutes classes a day and as many as 200 students. There is a categorical difference in understanding these challenges via secondhand and firsthand accounts; there is simply no substitute for being in the classroom. It is this gap between knowing and truly understanding what a teacher goes through on a day to day basis that has allowed for the development of many ed-tech products that simply fail to fully address the needs of teachers.
Take for example the TI Nspire Navigator system. While clearly the product of extensive research into education, integrating proven tactics like interactive problems and system allowing instantaneous feedback from students, holes exist in the usability. The process of "beginning" a class, which allows students to "log in" and begin interacting, requires a button press. "Sending a file" requires a right click, a button press, and then two more redundant button presses within an unnecessary popup window. "Collecting a file" requires the same procedure, and grading the file and receive feedback requires a right click, a button press, and then navigating to an entirely different screen. The basic workflow is terribly inefficient and while button clicks may seem relatively easy these processes can add up to 5 minutes of work which is a precious amount of time in a 45 minute class period. Factor in older, slower computers that sometimes leg between button presses, and having to repeat all of these processes in every class period, and the clunky interface for what is otherwise a feature-rich and potentially useful platform makes the entire system practically inefficient to use. TI did it's research and hit all of the right features, so what went wrong? The answer is that the development process for the system was driven by engineers, not the teachers who would use the software on a day-to-day basis.
The solution to this problem is the Teacher-Innovator Model. Organizations like Teach for America, along with many other alternative certification and educational preparation program at colleges and universities, are creating a new generation of tech-savvy educators who use technology to improve their lives at every level and see the potential technology offers. Teacher-Innovators are those who have some experience with technology, perhaps an engineering background, and work with product development teams to build technologies that address the pain points that they experience daily in the classroom. By deploying beta technologies in their classrooms and those of their peers teaching similar subjects, Teacher-Innovators will be best positioned to develop the impactful, high value ed-tech solutions that will define tomorrow's classrooms. The best education technology products start in the classroom, and I am excited to be a part of this movement towards ground-up innovation.
Tuesday, July 30, 2013
Friday, June 28, 2013
The Magic is in the Data...Structures
I really wish I had started studying computer science earlier in my life. As someone who can be a little ADD at times I always found basic programming to be a little, er, dull at times. While I love building things and programming with a purpose (a proper end in mind), when I was 12 and had nothing more interesting to code than custom configurations for my hacked router firmware (there is a limit to how strong you can make your wireless router signal strength - like -10 dB or so) sitting in front of a computer screen and playing around with aimless code lost its appeal quickly. Besides, Bill Gates and his people had already programmed everything useful and productivity-enhancing, right? (Hint: wrong....this was before Apple's resurgence, facebook, Google becoming not just a search engine, etc.). That terrible lapse in judgment aside, I am now starting to see firsthand the real beauty and potential of our modern methods for organizing data and information.
I took a short break from this project to study for the LSAT yesterday (always a good way to keep your mind fresh) and noted the parallels between the LSAT's logical reasoning and the programming structures that I have been teaching myself. I recently wrapped my head around the linguistic conundrum of the syntax of "UNLESS" and was amused to see a discussion of PowerScores trademarked "Unless Equation." Between these various endeavors I was struck by a thought: I need to use data not just to automate redundant tasks in the lesson planning process, but also to leverage technology and data to enhance the culture of lesson planning.
As I began thinking about how to organize the data behind lessons in a structured and efficient way that melds with my new world of strings, hashes, and arrays, I realized that the data structures that any computer program forces information to conform could have a tremendous positive impact on the way that lessons are planned, organized, indexed, and shared. Oftentimes in education the process of planning a lesson can be a murky endeavor which yields two maladies that stand out to me: firstly, it can take new teachers a long time to master the art of lesson planning without grasping the science of planning and secondly, and most critically, it can be very difficult for teachers to collaborate and share elements in their lesson plans due to the stylistic difference amongst individuals.
Over the last few days I have been trying to distill lesson plans down to their most fundamental elements to fit within the parameters required by the databases that my project will rely on. By forcing myself to think in the realm of data structures, I feel like I now have a stronger grasp than I ever have before of how to plan and breakdown a lesson. Moreover I am very excited about seeing what I can do with that data - right now the possibilities seem limitless. I am having a lot of fun applying my basic coding skills and developing rudimentary algorithms for working with data (I might just be sorting now but it's a start...). I still have much to learn but I am developing the Didactic system from the ground up with data in mind - I think that is where the real magic will happen.
I took a short break from this project to study for the LSAT yesterday (always a good way to keep your mind fresh) and noted the parallels between the LSAT's logical reasoning and the programming structures that I have been teaching myself. I recently wrapped my head around the linguistic conundrum of the syntax of "UNLESS" and was amused to see a discussion of PowerScores trademarked "Unless Equation." Between these various endeavors I was struck by a thought: I need to use data not just to automate redundant tasks in the lesson planning process, but also to leverage technology and data to enhance the culture of lesson planning.
As I began thinking about how to organize the data behind lessons in a structured and efficient way that melds with my new world of strings, hashes, and arrays, I realized that the data structures that any computer program forces information to conform could have a tremendous positive impact on the way that lessons are planned, organized, indexed, and shared. Oftentimes in education the process of planning a lesson can be a murky endeavor which yields two maladies that stand out to me: firstly, it can take new teachers a long time to master the art of lesson planning without grasping the science of planning and secondly, and most critically, it can be very difficult for teachers to collaborate and share elements in their lesson plans due to the stylistic difference amongst individuals.
Over the last few days I have been trying to distill lesson plans down to their most fundamental elements to fit within the parameters required by the databases that my project will rely on. By forcing myself to think in the realm of data structures, I feel like I now have a stronger grasp than I ever have before of how to plan and breakdown a lesson. Moreover I am very excited about seeing what I can do with that data - right now the possibilities seem limitless. I am having a lot of fun applying my basic coding skills and developing rudimentary algorithms for working with data (I might just be sorting now but it's a start...). I still have much to learn but I am developing the Didactic system from the ground up with data in mind - I think that is where the real magic will happen.
Tuesday, June 25, 2013
Hooked on Codecademy
So, while beginning to work through the Rails tutorial I realized that it would be of benefit to me to learn some programming languages from the ground up. I've always been able to work through most types of code by guessing, checking, and googling; but, I figured that building up my programming knowledge from the ground up (i.e. via some online course) might be more a tenable path for building up the requisite skills for my project than my usual ad-hoc method of learning through experimentation with discrete functions.
So, what started off as as some casual online refresher courses turned into a sort of Codecademy addiction. There really is something to the "gamey" aspect of the site which involves earning points for each completed activity and badges for achieving various landmarks such as completing a section of earning a certain number of points (or, as I recently discovered, earning a certain number of points in a day). I have found myself vying to stay focused and awake long enough to earn just one more badge before finally passing out for the night.*
Proof of my Codecademy achievements as of 10 minutes ago (I've earned two more points since I started this blog post and took this screenshot).
*note to self: "gameyness" in education works.
So, what started off as as some casual online refresher courses turned into a sort of Codecademy addiction. There really is something to the "gamey" aspect of the site which involves earning points for each completed activity and badges for achieving various landmarks such as completing a section of earning a certain number of points (or, as I recently discovered, earning a certain number of points in a day). I have found myself vying to stay focused and awake long enough to earn just one more badge before finally passing out for the night.*
Proof of my Codecademy achievements as of 10 minutes ago (I've earned two more points since I started this blog post and took this screenshot).
*note to self: "gameyness" in education works.
Wednesday, June 19, 2013
Quick Update
Posting has been slow as I've been juggling a few things but have no fear - progress is being made.
More updates to come soon...
Thursday, June 6, 2013
Scores Are In
Well, the scores are in and my students did reasonably well. Overall nearly 80% of my students passed their Texas Geometry STAAR (State of Texas Assessment of Academic Readiness) test. Two of my students got Advanced (roughly correlates to more than 90% correct). I am proud of them.
Thanks to Nancy Yang for teaching me the basics of lesson planning. Soon, I hope that I will also be able to help new teachers effectively lesson plan - it really make a difference in the classroom.
Wearing Disappointment on Your Sleeve
Since not a lot has been happening on the tech side (I'm still running through codecademy tutorials every night but I have 5 more days of school before the summer and am trying to make the best of them before going into full development mode), I figured now would be a good time to reflect on a subject that is very pertinent to my life at present: how to motivate students. I suppose this is an essay of sorts.
A fly on the wall of a teacher lounge would hear discussion on a variety of subjects: work, life, stress, administration, unions, politics, and, of course, students. Of those the latter is invariably the most common; interactions with students in one way or another, the good, bad, ugly, and wonderful, are the principal elements of our occupation. In a socioeconomically disadvantaged setting in particular, much talk surrounds the questions of why and how; why do our students struggle and how can we help them? Sometimes this pair of questions is most easily answered in reverse order.
By witnessing how our actions positively impact our students, we gain insights into why our students are the way they are. The other day, as I was eating lunch, one of my teaching colleagues made a comment that struck me in response to my minor lamentations about a small group of students who had collectively failed to meet our class goals and seemed trapped in a cycle of apathy towards not only school, but their also their futures. Specifically, I mentioned a student I had who had demonstrated a clear aptitude for math and ability to succeed but simply refused to try on a day to day basis despite my constant motivation, parental involvement, and other attempts at support. Over the course of the year I had developed a strong relationship with said student but was never able to fully leverage it to keep him consistently driven to work. On this particular day, I traded my usual positive affirmation and words of encouragement, a seeming broken record at that particular moment, for a curt "do you even care?" Those words triggered a look on that student that I could best characterize as bewilderment. In turn, I was myself bewildered - perhaps even annoyed - after that we, not him, we, had been through over the year, how could he give me such a look?
My experienced colleague immediately understood what I could not. I may be paraphrasing a bit, as it was not until after the words had set in that I was struck by their significance, but my fellow teacher basically said, "look, sometimes you are the only person in these kids' lives to express disappointment in them. They need that." My words to that student were precisely the product of that sentiment: disappointment. To be clear, my past interactions with this student had encompassed a wide array of emotions ranging from pride, that one time he got the highest grade on an assignment excelling beyond his peers, to anger, after he would occasionally act up in class. My anger always elicited the common student response of initial obstinance followed by eventual apology and forgiveness; that was a scenario that I was accustomed to dealing with. This situation, however, was fundamentally different as I had faltered from the traditional teaching paradigm of infinite encouragement and positivity. My misstep was illuminating.
After realizing that what I had conveyed to that student was genuine disappointment, I began to suspect that my colleague was perhaps correct in identifying the value of disappointment. The bewilderment I saw was a sure sign that disappointment of that sort was an emotion my student was not comfortable facing. I don't mean to suggest definitively that nobody has ever properly cared for this student (since disappointment is a product of caring for someone - think about it, you can't be disappointed if you're ambivalent). Indeed, contrary to popular belief, many of my students are strongly cared by their parents, teachers, and communities alike. At the very least, however, this student did not expect disappointment from me as I had set no precedent for it. And disappointment, I would learn soon, can be a powerful motivational force.
Thinking back to my own life, emotionally tangible instances of the disappointment of others in me are amongst my most vivid memories. I will never the look on my father's face the day that I failed my first driving test or the painful silence of the drive back home with my father, rather than myself, at the wheel. Nor will I forget the tone of Mr. Ball's voice when he caught me using the band room computer when I wasn't supposed to be, or the way that Coach Ehrenhaft walked away from me after realizing that I had skipped cross country camp. While minor failings by objective estimation, I was consumed by that feeling of having failed another and will accordingly never forget those moments. We all fail ourselves at one point or another and learn to manage that feeling ourselves, but my experience suggests that failing someone else is almost categorically different.
The day after my incident with said student, he came to me during lunch to chat. His words were straightforward: "I'm sorry I haven't been doing my work, I will try to try harder next time." My response was simply, "You won't try to try - you will try and you will succeed and I know that you can, so do it." Only time will tell whether this student will find success, but I see a minor victory in having forced that student to think about his actions, whether on his own behalf or for others. The how - the motivating force - was disappointment. This conflicts with the notion of always being a positive force as disappointment is inherently negative. Still, had I given this student my usual pat on the back with words about how could do better and should work harder to prove himself, I'm sure that my words would not have a spurred a second thought. So we know the how; what about the why?
All teachers know that it is important to set high standards for students. The reality is that this is difficult when all of our students are performing at an objectively low level and we must positively affirm whatever successes that we see. I have heard that studies have found that A students at low performing schools actually perform, when data is normalized, at about the level of C students at average schools. While I know that there is no easy fix to this conundrum, I do believe that my students lack have an insufficient number of people who are disappointed in them. More significantly, students often fail to be disappointed in themselves. This now unique to low income areas and not even unique to students; for most people the path of least resistance is to accept ourselves as is rather than change who we are whether we are talking about America's most commonly failed New Year's Resolution of going to the gym regularly or my own personal failure to keep my desk clean. It is when others hold us accountable and vest their interests with us that we succeed in such endeavors. Accountability is a key to this; there should be rewards for exceeding expectations and disincentives for failing to meet them.
Nobody likes it when somebody is disappointed in them. While varying in significance depending on your relationship with whoever is disappointed in you, disappointing someone is universally bad and something that one would like to avoid. While positivity is a proven driver of student performance, we must step back at times and question accepting barely passing classes and tests as the standard bimodal measure of success. For all the times that we encourage our students, we perhaps need not avoid wearing our disappointment on our sleeves at the times when our students have not only failed ourselves, but failed us. Intrinsic motivation is ideal but if we as teachers must carry the emotional weight of concern for these students and use guilt to jump start their motivation, then the end does justify the means and disappointment can, and perhaps ought, to be a part of a truly productive student-teacher relationship.
A fly on the wall of a teacher lounge would hear discussion on a variety of subjects: work, life, stress, administration, unions, politics, and, of course, students. Of those the latter is invariably the most common; interactions with students in one way or another, the good, bad, ugly, and wonderful, are the principal elements of our occupation. In a socioeconomically disadvantaged setting in particular, much talk surrounds the questions of why and how; why do our students struggle and how can we help them? Sometimes this pair of questions is most easily answered in reverse order.
By witnessing how our actions positively impact our students, we gain insights into why our students are the way they are. The other day, as I was eating lunch, one of my teaching colleagues made a comment that struck me in response to my minor lamentations about a small group of students who had collectively failed to meet our class goals and seemed trapped in a cycle of apathy towards not only school, but their also their futures. Specifically, I mentioned a student I had who had demonstrated a clear aptitude for math and ability to succeed but simply refused to try on a day to day basis despite my constant motivation, parental involvement, and other attempts at support. Over the course of the year I had developed a strong relationship with said student but was never able to fully leverage it to keep him consistently driven to work. On this particular day, I traded my usual positive affirmation and words of encouragement, a seeming broken record at that particular moment, for a curt "do you even care?" Those words triggered a look on that student that I could best characterize as bewilderment. In turn, I was myself bewildered - perhaps even annoyed - after that we, not him, we, had been through over the year, how could he give me such a look?
My experienced colleague immediately understood what I could not. I may be paraphrasing a bit, as it was not until after the words had set in that I was struck by their significance, but my fellow teacher basically said, "look, sometimes you are the only person in these kids' lives to express disappointment in them. They need that." My words to that student were precisely the product of that sentiment: disappointment. To be clear, my past interactions with this student had encompassed a wide array of emotions ranging from pride, that one time he got the highest grade on an assignment excelling beyond his peers, to anger, after he would occasionally act up in class. My anger always elicited the common student response of initial obstinance followed by eventual apology and forgiveness; that was a scenario that I was accustomed to dealing with. This situation, however, was fundamentally different as I had faltered from the traditional teaching paradigm of infinite encouragement and positivity. My misstep was illuminating.
After realizing that what I had conveyed to that student was genuine disappointment, I began to suspect that my colleague was perhaps correct in identifying the value of disappointment. The bewilderment I saw was a sure sign that disappointment of that sort was an emotion my student was not comfortable facing. I don't mean to suggest definitively that nobody has ever properly cared for this student (since disappointment is a product of caring for someone - think about it, you can't be disappointed if you're ambivalent). Indeed, contrary to popular belief, many of my students are strongly cared by their parents, teachers, and communities alike. At the very least, however, this student did not expect disappointment from me as I had set no precedent for it. And disappointment, I would learn soon, can be a powerful motivational force.
Thinking back to my own life, emotionally tangible instances of the disappointment of others in me are amongst my most vivid memories. I will never the look on my father's face the day that I failed my first driving test or the painful silence of the drive back home with my father, rather than myself, at the wheel. Nor will I forget the tone of Mr. Ball's voice when he caught me using the band room computer when I wasn't supposed to be, or the way that Coach Ehrenhaft walked away from me after realizing that I had skipped cross country camp. While minor failings by objective estimation, I was consumed by that feeling of having failed another and will accordingly never forget those moments. We all fail ourselves at one point or another and learn to manage that feeling ourselves, but my experience suggests that failing someone else is almost categorically different.
The day after my incident with said student, he came to me during lunch to chat. His words were straightforward: "I'm sorry I haven't been doing my work, I will try to try harder next time." My response was simply, "You won't try to try - you will try and you will succeed and I know that you can, so do it." Only time will tell whether this student will find success, but I see a minor victory in having forced that student to think about his actions, whether on his own behalf or for others. The how - the motivating force - was disappointment. This conflicts with the notion of always being a positive force as disappointment is inherently negative. Still, had I given this student my usual pat on the back with words about how could do better and should work harder to prove himself, I'm sure that my words would not have a spurred a second thought. So we know the how; what about the why?
All teachers know that it is important to set high standards for students. The reality is that this is difficult when all of our students are performing at an objectively low level and we must positively affirm whatever successes that we see. I have heard that studies have found that A students at low performing schools actually perform, when data is normalized, at about the level of C students at average schools. While I know that there is no easy fix to this conundrum, I do believe that my students lack have an insufficient number of people who are disappointed in them. More significantly, students often fail to be disappointed in themselves. This now unique to low income areas and not even unique to students; for most people the path of least resistance is to accept ourselves as is rather than change who we are whether we are talking about America's most commonly failed New Year's Resolution of going to the gym regularly or my own personal failure to keep my desk clean. It is when others hold us accountable and vest their interests with us that we succeed in such endeavors. Accountability is a key to this; there should be rewards for exceeding expectations and disincentives for failing to meet them.
Nobody likes it when somebody is disappointed in them. While varying in significance depending on your relationship with whoever is disappointed in you, disappointing someone is universally bad and something that one would like to avoid. While positivity is a proven driver of student performance, we must step back at times and question accepting barely passing classes and tests as the standard bimodal measure of success. For all the times that we encourage our students, we perhaps need not avoid wearing our disappointment on our sleeves at the times when our students have not only failed ourselves, but failed us. Intrinsic motivation is ideal but if we as teachers must carry the emotional weight of concern for these students and use guilt to jump start their motivation, then the end does justify the means and disappointment can, and perhaps ought, to be a part of a truly productive student-teacher relationship.
Tuesday, May 28, 2013
Ruby on Rails: Here I Come
Quick Update:
After going through a number of basic coding tutorials and taking breaks by working on pencil and paper design-mock-ups, I'm now beginning to go through the Ruby on Rails tutorial which will hopefully teach me enough that I can start building my product. I've just barely gotten through the basic setup - I'm contemplating installing Ubuntu in VirtualBox and coding there to avoid the frustrations that might come from programming in Windows while following an OSX/unix-centric tutorial. I'll make that call tomorrow - now it is finally time to sleep.
After going through a number of basic coding tutorials and taking breaks by working on pencil and paper design-mock-ups, I'm now beginning to go through the Ruby on Rails tutorial which will hopefully teach me enough that I can start building my product. I've just barely gotten through the basic setup - I'm contemplating installing Ubuntu in VirtualBox and coding there to avoid the frustrations that might come from programming in Windows while following an OSX/unix-centric tutorial. I'll make that call tomorrow - now it is finally time to sleep.
Sunday, May 26, 2013
Coding 101
Note: Potentially useful information towards the end - musings at the beginning
Well, here I go. It has been a long time since I have tried to code something. Way back when (about 2002 when I was in 7th grade, I think?) I made a pretty awesome website for Smash Adams, a band composed of some of my friends in middle school. Anybody remember Macromedia Studio? Between Dreamweaver, Fireworks, and Flash, I was able to create something halfway decent, as my high school art teacher Mr. Rueckert would always say. I will never forget the checked background I made in fireworks (it had all sorts of fun gradients and stuff) or the 2.5 MB "picture gallery" I made in Flash that took an exceptionally long time to load even on the day's state of the art "faster than dsl" cable broadband connections (and let's just forget about 56k which still a veritable force back then). Really, when all was said and done I think I did a pretty good job for an 11 year old. I utilized frames effectively, built a cool navigational menu, and everything was fairly aesthetically pleasing for that time. While Dreamweaver made is so that I did not actually have to code the site, I did have to interface with the html fairly often when I dropped in plug-ins or borrowed free code for different functions so I did have some understanding of how coding worked.
So, where did I go from there? Well, I didn't build facebook. In fact, besides some straightforward websites that I made for later business ventures (some of which were fairly successful and others which were less so). I actually didn't learn much more at all about coding - I discovered automobiles and devoted my free time to wrenching on old cars that I bought/restored/repaired/re-sold. It was perhaps a shame in some ways given that it programmers seem to get paid, on average, much more than automobile mechanics. Still, I have no regrets and continue to love wrenching - I hope that some day I'll be to afford to have the free time to continue to pursue that interest as a hobby (maybe even open my own shop some day).
Fast forward to college in California and I developed a whole new set of interests. Silicon Valley was a potent influence even in sunny SoCal but I quite for the web/mobile startup bug. I think that I was a bit jaded, or perhaps, by the multitude of random and sometimes redundant "startups" that everyone seemed to have back in 2008. I've never been much of a conformist and doing what everyone else was doing was simply of little interest to me. Besides, the world of high finance was alluring. From investment banking to leveraged buyouts (pioneered by alumni of my alma mater), high finance was novel and intriguing to me given that I knew absolutely nil about it prior to college. My roommate of two years, Alex Berman (currently a Product Manager @ Intuit), made a dramatic switch from finance/NY to computer science/Silicon Valley but failed to string me along for the switch (I must give him a lot of credit for teaching me about finance and separately convincing me to overload my credits by taking the history class that drew me into my second college major and passion - history). To sum it all up, I did not take one computer science class and besides the occasional side projects that required a bit of programming (and of course learning LaTeX and stata for math/economics), I did not expand my coding knowledge much behind what I had acquired by age 12, which brings me to the present time.
Well, I now have to develop a product and don't really know how to code. Fortunately I learn fast and the internet has a wealth of information on how to code. I have been flying through lessons on codecademy (codecademy.com) and a trusted friend pointed me the way of codeschool's (codeschool.com) free weekend promo - look below, I knocked out about half of the HTML5 & CSS3 lesson in a little over an hour. So, I'm going to spend every waking hour of tomorrow on codeschool getting through as much as possible and a lot of time on codecademy filling in my basic knowledge gaps. Further, I'm going to push myself to marathon through railstutorial with the hope that by the end I'll be able to do much of the development for my product on my own. Wish me luck - I think I can do this.
P.S. I have been thinking about my UI design and I've been playing around with balsamiq for mock-ups but will also try easel.io before committing to one tool - I will update with my comparison of the two when I get a chance.
Well, here I go. It has been a long time since I have tried to code something. Way back when (about 2002 when I was in 7th grade, I think?) I made a pretty awesome website for Smash Adams, a band composed of some of my friends in middle school. Anybody remember Macromedia Studio? Between Dreamweaver, Fireworks, and Flash, I was able to create something halfway decent, as my high school art teacher Mr. Rueckert would always say. I will never forget the checked background I made in fireworks (it had all sorts of fun gradients and stuff) or the 2.5 MB "picture gallery" I made in Flash that took an exceptionally long time to load even on the day's state of the art "faster than dsl" cable broadband connections (and let's just forget about 56k which still a veritable force back then). Really, when all was said and done I think I did a pretty good job for an 11 year old. I utilized frames effectively, built a cool navigational menu, and everything was fairly aesthetically pleasing for that time. While Dreamweaver made is so that I did not actually have to code the site, I did have to interface with the html fairly often when I dropped in plug-ins or borrowed free code for different functions so I did have some understanding of how coding worked.
So, where did I go from there? Well, I didn't build facebook. In fact, besides some straightforward websites that I made for later business ventures (some of which were fairly successful and others which were less so). I actually didn't learn much more at all about coding - I discovered automobiles and devoted my free time to wrenching on old cars that I bought/restored/repaired/re-sold. It was perhaps a shame in some ways given that it programmers seem to get paid, on average, much more than automobile mechanics. Still, I have no regrets and continue to love wrenching - I hope that some day I'll be to afford to have the free time to continue to pursue that interest as a hobby (maybe even open my own shop some day).
Fast forward to college in California and I developed a whole new set of interests. Silicon Valley was a potent influence even in sunny SoCal but I quite for the web/mobile startup bug. I think that I was a bit jaded, or perhaps, by the multitude of random and sometimes redundant "startups" that everyone seemed to have back in 2008. I've never been much of a conformist and doing what everyone else was doing was simply of little interest to me. Besides, the world of high finance was alluring. From investment banking to leveraged buyouts (pioneered by alumni of my alma mater), high finance was novel and intriguing to me given that I knew absolutely nil about it prior to college. My roommate of two years, Alex Berman (currently a Product Manager @ Intuit), made a dramatic switch from finance/NY to computer science/Silicon Valley but failed to string me along for the switch (I must give him a lot of credit for teaching me about finance and separately convincing me to overload my credits by taking the history class that drew me into my second college major and passion - history). To sum it all up, I did not take one computer science class and besides the occasional side projects that required a bit of programming (and of course learning LaTeX and stata for math/economics), I did not expand my coding knowledge much behind what I had acquired by age 12, which brings me to the present time.
Well, I now have to develop a product and don't really know how to code. Fortunately I learn fast and the internet has a wealth of information on how to code. I have been flying through lessons on codecademy (codecademy.com) and a trusted friend pointed me the way of codeschool's (codeschool.com) free weekend promo - look below, I knocked out about half of the HTML5 & CSS3 lesson in a little over an hour. So, I'm going to spend every waking hour of tomorrow on codeschool getting through as much as possible and a lot of time on codecademy filling in my basic knowledge gaps. Further, I'm going to push myself to marathon through railstutorial with the hope that by the end I'll be able to do much of the development for my product on my own. Wish me luck - I think I can do this.
P.S. I have been thinking about my UI design and I've been playing around with balsamiq for mock-ups but will also try easel.io before committing to one tool - I will update with my comparison of the two when I get a chance.
Saturday, May 25, 2013
Introduction
Dear Friends, Family, and whoever else may be reading this,
I am writing this blog for three reasons: firstly, I would like to keep people about the progress that I am making on a journey that I am about to undertake; secondly, my experiences with Teach for America have taught me the value of reflection and writing these posts will be a perfect opportunity to stop and breathe amidst what is sure to be a challenging endeavor; and lastly, I need to hold myself accountable for making progress and I think that the watchful eyes of those who believe in me will do just that.
So, by now you are probably wondering what all of this is really about. In about two and a half weeks time, I will have just finished my first year of teaching math at Bryan Adams High School in Dallas as a Teach for America corps member. I was drawn to Teach for America by a yearning for engaging in a form of public service and a strong desire to challenge myself in new ways; TFA has delivered on all counts. Prior to TFA and during and before college, I was involved in a number of entrepreneurial ventures driven by natural tendency to build and create. Now that I finally have confidence in my abilities to teach and lead my students, which I can assure you did not come easily, I am fully ready to do what I do best and start a new project that I will be working on this summer and during my second year of teaching.
I was inspired about a week ago during a conversation I was having with an old friend from high school, Anirudha Balasubramanian, who is currently involved with some exciting projects himself. As I was updating him on my last year our conversation veered between my own experiences and exciting projects that others were working on. At one point, I mentioned some of the pain points of the lesson planning process that all math teachers creating TFA-style lessons face on a day to day basis, which was when it hit me: I could create an app or program that would ease, simplify, and streamline that process.
So here I am - this blog's title is a bit of a misnomer as I would not say that I have a startup of any sort yet. What I have is an idea for how to streamline and ease the lesson planning process for high school math teachers. As of one week ago, I have begun the early stages of designing and building this product and this blog will chronicle that journey. Here you will find my excitements, frustrations, disappointments, successes, and general the general musings I have along the way.
Happy Reading,
Prashant
I am writing this blog for three reasons: firstly, I would like to keep people about the progress that I am making on a journey that I am about to undertake; secondly, my experiences with Teach for America have taught me the value of reflection and writing these posts will be a perfect opportunity to stop and breathe amidst what is sure to be a challenging endeavor; and lastly, I need to hold myself accountable for making progress and I think that the watchful eyes of those who believe in me will do just that.
So, by now you are probably wondering what all of this is really about. In about two and a half weeks time, I will have just finished my first year of teaching math at Bryan Adams High School in Dallas as a Teach for America corps member. I was drawn to Teach for America by a yearning for engaging in a form of public service and a strong desire to challenge myself in new ways; TFA has delivered on all counts. Prior to TFA and during and before college, I was involved in a number of entrepreneurial ventures driven by natural tendency to build and create. Now that I finally have confidence in my abilities to teach and lead my students, which I can assure you did not come easily, I am fully ready to do what I do best and start a new project that I will be working on this summer and during my second year of teaching.
I was inspired about a week ago during a conversation I was having with an old friend from high school, Anirudha Balasubramanian, who is currently involved with some exciting projects himself. As I was updating him on my last year our conversation veered between my own experiences and exciting projects that others were working on. At one point, I mentioned some of the pain points of the lesson planning process that all math teachers creating TFA-style lessons face on a day to day basis, which was when it hit me: I could create an app or program that would ease, simplify, and streamline that process.
So here I am - this blog's title is a bit of a misnomer as I would not say that I have a startup of any sort yet. What I have is an idea for how to streamline and ease the lesson planning process for high school math teachers. As of one week ago, I have begun the early stages of designing and building this product and this blog will chronicle that journey. Here you will find my excitements, frustrations, disappointments, successes, and general the general musings I have along the way.
Happy Reading,
Prashant
Subscribe to:
Posts (Atom)