Showing posts with label programming in real life. Show all posts
Showing posts with label programming in real life. Show all posts

Monday, June 9, 2014

Georgia Tech - Two More Weeks Down!

So last night I finished module 3 in my AI for Robotics course that I am taking as a part of Georgia Tech's Online MS in Computer Science. Things have somewhat settled down into a routine, with my various classmates working through the course at their own speed. Due to a complete lack of time in pretty much my entire life right now I'm simply trying to keep abreast of the weeks as they are due according to the schedule provided at the start of the term. Problem sets are due each Wednesday, and are submitted through Udacity's software. An instructor then goes through and ports these into something called T-Square, which I understand to be Georgia Tech's grading system. I could be wrong, though.

Assumed background knowledge

One of the things I'm noticing is that the course is starting to assume some background knowledge that not a lot of students may have. This is unavoidable in pretty much any course, as I have found out too often during my stints as a college professor. However, there are some ways this could be mitigated. For example, this is my first course at Georgia Tech, and my understanding is that it is targeted towards the end of the program. I took it because I found the subject interesting, but I could see where this might be causing me some trouble.

One example is that the course makes some decent use of techniques from Linear Algebra. I have a healthy grounding in this thanks to my time at DePaul and a few years spent in the pixel mines, but more often than not this type of math is an elective - at best - for computer science undergraduates. The problem is that there wasn't much in the course description that indicated that this type of math would be used. Statistical analysis is also featured heavily in the course, and while there are ample resources available for coming up to speed most students have no idea that they will need to do so before the course starts. I had around a month before classes began where I could have been preparing myself, but as it was I kind of walked into the course blind.

Interesting Problem Sets

One of the things I do find interesting is that the problem sets at the end of each lecture are actually not a significant portion of the grade. In fact, they're worth 3 points each (compared to a total upwards of 70 points for the two projects), and are graded on a pass-fail basis. To quote the professor, they essentially serve as a kind of "attendance check." That's all well and good, but if I am putting forth effort towards these assignments I'd like to see just a little bit more credit given for my efforts. Not much I can do about that, though, and I can definitely see the instructor's point.

One thing I do like about these problem sets is the use of automated grading. At first it's used in a fragile manner, along the lines of "Does the program output include this string," but the most recent assignment used statistical analysis in its grading to determine if the provided code was correct. It's pretty rewarding to see code that you wrote indicated as correct against an arbitrary data set with around 95% of accuracy.

Moving Forward

One thing I'm kind of leery of is wondering when the lack of prerequisite knowledge is going to bite me. I'm worried about the week 4 subject material, as it depends a lot upon dynamic programming and some aspects of machine learning - to the point where I'm reading chapters from a ML textbook in order to increase my knowledge base. It leads to one of the things I've been most concerned about, which is adequately scheduling time to devote to my courses.

So far the coursework takes me between 2-4 hours a week - a surprisingly low amount. However, I know that this is not the case for other courses, such as Machine Learning which can demand upwards of 40 hours of additional time each week, and in many cases I'm waiting for the other shoe to drop. I suppose at this point all I can do is wait and see, and hope it doesn't get too bad.

I'll try to provide these posts more frequently but, as I mentioned above, life happens :-/

Thursday, May 22, 2014

Georgia Tech OMSCS - Week 1 Recap

I know, it's only Thursday!

So I just finished my first "week" of class for Georgia Tech, and I wanted to get some of my thoughts down on virtual paper. I'd like to chronicle my adventure semi-frequently in this manner, so please bear with me if this isn't your cup of tea.

Some Background

So one of the things I'm willing to admit right off the bat is that I was pretty nervous. Given my prior trials and tribulations trying to even get into the program, I had no idea what to expect. I remember some of the experience of getting my MS the first time around, and some of the courses I took as an undergrad, but I wasn't sure how this experience would compare. What is an education like at a top-10 institution? Would I be able to measure up to the bar and finally put some of my constant inferiority complex to rest?

Well, we'll have to wait a while for the answer to that last one. I'm not very confident by nature, even though I know I have a modicum of programming and communication skills. I'm always looking for ways to "prove" myself, so to speak, and I tend to take on more than I can handle as a result. I am not sure that that personality trait will ever truly go away, and honestly this Georgia Tech experience stems from that whole complex - I had had a couple of bad interview experiences with companies that rhyme with Moogle and Bamazon, and was trying to figure out how to bolster my knowledge and not feel like I was incompetent. I guess this way I'll be able to point at a fancy piece of paper and say "Well, I was good enough for that".

Provided I am actually up to the task, that is.

The experience so far

Anyway, enough navel-gazing. I'm taking CS-8803 - AI for Robotics - and so far the experience has been pretty good. On the one hand the course is delivered almost entirely via lecture. I have mixed feelings about this, and feel another digression is in order. I know that there are different ways people learn, and that some people feel that they learn best visually. I also, though, have taught several classes where the student claims to only learn well visually but, if you really got down to it, what they really wanted was a step-by-step guide on how to do an assignment rather than a lecture that builds the foundations for a concept that they then apply themselves. In other words, they were (in my eyes) using the "I'm a visual learner" mantra as an excuse rather than a legitimate gripe. If you couple this with my NOT being a visual learner (I want nothing more than a big textbook to work through), I tend to be skeptical of the approach to begin with.

I have to say, though, I was pleasantly surprised. Aside from minor frustrations the lectures do a decent job of presenting the material. The way a module works is that a video of the lecture plays up to the point of a "quiz," which in a classroom setting would be the instructor asking a question of the class, and stops to allow you to input an answer into a form that is then checked for correctness. Once the answer is entered (or skipped, if you get stuck) the lecture continues until the next quiz. The lectures themselves vary widely, using video recordings in some cases, recorded whiteboard sessions in others, and still others with the professor simply talking to the students. Of most use to me were the intermittent programming quizzes - the instructor would explain a concept, then say "Ok, now you try to write a function that does this," and suddenly you're presented with a minimal Python IDE to develop code in, along with a test run and evaluation button to determine if your code is correct. It's obvious that a lot of thought went into these lectures, and it comes through in the design of the course.

Frustrations

My frustrations with the course so far are two-fold. First is that the course is programmed in Python - a language I had a passing familiarity with, but which is subject to its own quirks. If the course was in C++ or Ruby I'd have no trouble, but as it is I am learning the language as I go along. On the one hand that's good - I'll have another language under my belt when I finish the class - but it is also frustrating and increases the time I spend on assignments. I'm not sure there's any way around this, though.

The second frustration is with the video-based learning. It is extremely challenging to reference material in a video, particularly when programming. Programming is a lot about copy-and-paste, and you can't paste from a video. I have had this argument with any number of people, and I remain unconvinced - for these type of topics you can provide a video if you like, but the most useful thing to a professional programmer is a text version that allows you to 1: keep it open in a browser next to your IDE for reference, 2: allows you to review without having to hunt through a video, and 3: allows you to learn without needing to break your concentration for audio and visual stimuli. To me this is reminiscent of a problem I had at Enova, which is that for some reason the IT department thought it was a good idea to do all of their internal support tutorials as videos. Videos are an extremely poor choice when adding a VPN key, or when you want to save the information for future reference. If OMSCS is going to be mostly video-based, I suspect I'll be lamenting this for a while to come. But then again, I was able to complete the first week's assignment and understand the material (with one exception, as Bayes rule is still kicking my ass for some reason), so I guess the point is moot.

Communication

The course also has a separate message board on piazza.com, which is used to speak with your fellow classmates and ask questions of the instructor and TA. This is a great feature, I think, and has helped me a couple times. Most of the people in the course are active on the boards and very willing to help, and it is also helpful to see that some people have the same questions I do. Where I've had trouble in the course I've quickly been able to get a response on the message board, as both my fellow students and the instructors are active there.

Self-direction

One of the things I really like at the moment, but could see myself coming to dislike, is that the course is largely self-directed. If I had the time to spare, I could push through the entire course as quickly as possible. While the lectures are organized into "Lessons" that represent a week's worth of work, there is nothing preventing you from moving ahead as you work. On the plus side, this means that I was able to finish the first week's assignment well over a week before it was due, which is great as I maintain a far too busy schedule to begin with. However, I can see this causing problems near the end of the term as if we are looking at a time-based submission and grading process, I won't be receiving feedback on my submissions until they are officially "due". So for example, if I was to power through module 2 right now I wouldn't see any feedback until June 4 at the earliest, by which time the assignment will likely be out-of-mind.

I suppose time will tell on how successful this approach is for me. For now I like that I can work ahead when I have some spare time!

Evaluating my own teaching experience

Another thing the OMSCS experience is allowing me to do is evaluate my own teaching, and see what is effective. I teach college courses online for a couple universities, and seeing how this course is conducted provides some interesting contrasts. From the start, it's obvious that more effort went into the Udacity course design than goes into the courses I typically teach - which has been a constant frustration point for me as, with one exception, I often don't get to design my courses so that they have the material I feel is necessary. However, a lot of the assignments in the class I'm taking now are "did it or not" evaluations - you get points for completing the activity, but no partial points are awarded. I don't know what grading will be like yet (doesn't happen until next week), but I think "all or nothing" assignments are a disservice to the student and fail to recognize that it IS possible to half-understand something.

Conclusion

To sum up, I'm very much in a wait-and-see pattern right now. Some of my frustrations with the format may be exclusively due to this course's design - I've already heard that some of the other courses handle things a lot differently - while others may be due to the format. I guess my opinion will continue to evolve as I run through the experience. I know that's kind of a weak close to this lengthy post, but to be honest that's about how I feel right now - not very strongly on the "good" or "bad" spectrum, just "different."

I do think it will be interesting to come back and read this after I have a few more classes under my belt. So stay tuned, I guess.

Wednesday, January 29, 2014

Concrete Coding Corner - Agile Estimation


In the last concrete coding corner post, I spent a lot of time talking about goals and metrics and how they relate to non-concrete endeavors such as writing and programming. One thing I deliberately left out was the obvious. Sure, I can develop any number of metrics to tell me how much progress I am making, but what do I do to tell how much progress is left?



In the business world (where most of my experiences in this area lie), companies are run on quarterly budgets that take into account resource allocation and potential projects. These projects usually have some sort of figure attached to them that represents a Return On Investment, or ROI. The goal then is to have ROI be as high as possible, while the resource allocation budget to produce that ROI needs to be as low as possible. For manufacturing processes, there are a number of factors that play into this – designers, prototyping, manufacturing, material resources, and so on. Physical costs, such as the base metal required to manufacture the body of a vehicle, are pretty much fixed. You can potentially swing a one-time decrease through intense negotiation, but you introduce yourself to potential shortfalls in quality to meet the new price. Not to mention that negotiating those kinds of reductions can be an extremely time-consuming and exhausting process.



The other aspect of any project is the, for lack of a better word, “flexible” cost. This is the cost for more ephemeral tasks, such as programming or architecture, where you cannot necessarily know how long the task will take before you begin. A project manager or product owner looks at their cost reduction options and sees this, thinking to themselves “Getting Joe to work a bit harder for a while will get this done faster, and be easier than reducing physical costs. Let's do that!” Without data to back up assertions that the goals imposed as a result are not achievable through reasonable effort, the programmer is left in the lurch – they have no power to change the situation, and thus often end up working long hours to meet the seemingly arbitrary goals.



The Problem
The primary problem with the “just work more” approach is obvious to anyone who has done creative work for any length of time – creative work is exhausting. Performing that kind of work for any length of time can feel very much like running a marathon, conflating the mental and physical worlds into a conglomeration of perceived Herculean effort. After X number of hours, with X being different for every individual, it is simply not possible to produce at the same quality level as it was possible before X hours had elapsed.



The practical upshot of this is that quality of output for creative endeavors decreases as the time spent on that task in a session increases. This is the central point that is missed when attempting to procure more effort out of employees who derive their primary work product from the expense of mental effort – longer hours means more bugs and issues, which means longer hours to fix them. It's an infinite loop of increasing required effort, which often ends up costing more to complete than if the employee had been allowed to go at their own pace.



Note that the video game industry is horrible in this regard. Long hours (60-80 hour weeks or more) are the norm in that industry as projects move towards the completed stage. Project managers in the game industry are often constrained by hard dates – such as the holiday season – that they have no way to negotiate around, and so when you cannot manipulate your end date the only thing remaining is to attempt to manipulate the amount of effort performed each week. In many cases, this results in months of extremely long hours, where programmers and artists are pushed relentlessly to meet deadlines that are forever seeming farther away. Additionally, the cumulative exhaustion of weeks of long hours seeps in, resulting in the remaining amount of work increasing despite the longer hours as bugs introduced into the system by a tired programmer required effort to fix.



Having spent time in the game industry, I wish I could say that the above was an apocryphal example, but examples abound throughout the industry, and things rarely seem to improve. The marketing and funding realities of the industry make this a problem that is tricky to solve. Some companies have large enough cash reserves that they can simply ignore the calendar and say “It'll be done when it's done,” but most others need the infusion of cash provided by a completed project to continue to do things like pay rent, electricity, and employees (often in that order).



Analyzing the issue
The game industry has a situation that arises from external constraints, but it also is a byproduct of creative work – there is no way to know how long a task is going to take before it is started. Sure, you can have a ballpark. For example, I've written two books so far, and each took about 30 days for the final draft. Given that, it's reasonable to assume that if I were to write a third book, it would also take about 30 days for the final draft.



Except when it doesn't.



This is the most frustrating thing about programming to non-programmers. Two tasks can seem extremely similar, but one may take five minutes while another would take a week. The reasons why are numerous – fractured code bases, incompatible patterns, and so on – but ultimately there is no obvious reason that a layman can point to and say “Oh, that's why that took so long!” This problem, when repeated multiple times over the course of a project, can sour the relationship between a project manager and a programmer, taking what was originally a productive and respectful interaction process and making it confrontational. It is usually not the result of any intentional slight by the programmer or intentional misinterpretation by the PM, but instead it's an issue of trust.



Every time a programmer claims that a task will take longer than originally expected, or that they have been delayed, the PM has no choice but to assume that the delays are intentional as they have no insight whatsoever into the development process. This may not be an overt assumption, but it certainly occurs on some subconscious level and factors into decision making and interactions. This injects stress and discord into the process, which builds up over the course of a project and results in negative perceptions. A project could be on the most efficient possible track to completion, making strides that no other team could possibly make with the same material, but once the perception is soured that effort will never be seen as sufficient.



Addressing the Problem
The problem, as we've already mentioned, is that the PM has no way to know when a given task will be completed. The frustrating thing is that oftentimes, neither does the programmer. Sure a programmer can make an educated guess, but there are always factors outside of their control that play into the end result. Thus, the first approach to addressing the problem is to rely solely upon the guesses of the programmer. The programmer takes a look at a task before he begins, and gives an estimate of the effort required to complete that task. As a project manager is concerned with dates and timelines, they often push for time-based estimates (“It will take four hours”), and many programmers agree to the system.



Problem Solved, Right?
Once a unit associated with time has been decided upon, everything very quickly goes to hell. If a task that should “only take four hours” suddenly takes 40, then there is a perceived deficit. A project manager looking at a project plan sees the extra 36 hours of effort and is forced to conclude that “The project is now 36 hours behind.” This amount grows or shrinks as effort continues, and the perception of the project manager changes each time. If a task takes less time than expected, then the programmer is “making good progress” and the project is “on track.” If a task takes more, then the programmer is “introducing delays” and the project is “delayed.”



Notice the attribution of effort here. This all ties back to the choice of time as a base unit. Once you are estimating in terms of hours, the natural human tendency is to start watching the clock. We've been trained to pay close attention to time periods – 8 hours of work, 1 hour for lunch, 30 minutes to commute, and so on – that we subconsciously monitor the amount of time taken. When something takes longer than stated, it is frustrating and unsettling. By tying the estimates of a programming task into this time-based system on a granular level, we introduce the same predilections and perceptions into the evaluation of progress. It removes the ability to look at a task objectively and say “we are making X amount of progress.” Instead, everything is cast in terms of time. Time elapsed, time remaining, time behind, and when looking at the time associated with a project subjective judgments are added into the project status. Choosing an estimate in terms of time has resulted in looking at the project at a micro level, removing the ability to see the forest through the trees. The subjective perceptions of “late” and “early” that have been pounded in to us from our youngest years come into play, and color our perception of the project's progress.



Aggregate Data
One of the reasons behind this is that it is far too easy to look at a project as a series of finite tasks. Once these tasks have a discrete time associated with them, it is far too easy to take each task as an element in isolation. Good project managers, though, recognize that each task is only part of a larger whole. They strive to look at a project in aggregate – that is, as a combination of all of the tasks. They see the four hour task taking 40 hours, but then realize that the project is still 25% completed with one quarter of the budgeted time elapsed.



Thus, we see the path to our solution. An individual four hour task may run long, and may result in a delay. But on average, four hour tasks will typically take four hours. Some may be shorter, some much longer, as that is the nature of creative endeavors. However, looked at over a span of time, it is possible to develop a translation. If the average of all “four hour” tasks is 4.5 hours, that gives us a reliable predictive measure. We now know that if the programmer estimates a task at 4 hours, it will take 4.5 hours on average. This allows us to adjust our estimates and determine where the project actually lies.



A Problem of Units
At its core, with this translation table we've improved upon the primary concern – developing accurate estimates of project effort. However, we haven't addressed the soft factors of the issue. By associating progress with hours of effort, we are still tapping into that primal clock-watching urge, and thus still adding in the subjective judgements that go along with it. This is the problem with any time-based estimate system – it is tied to a known and familiar system, and even though it may operate on a varying scale, there is a subconscious perception of variation that permeates the project, regardless of the intentions. Because “hours” was chosen as the unit, this is tied back to real world elapsed time, and we end up with a slightly improved version of the same problem.

As it is, we now actually have the seeds of a potential solution. We've identified that looking at effort in aggregate provides us with more accurate estimates of project completion. We've also identified that expressing estimates in terms of time introduces needless subjective judgments into the process. We finally know that despite our best efforts, we do eventually have deadlines to meet – we cannot continue to just work forever.




A Different Approach
What we are really doing when estimating a task is building a view of the entire project. A project is the sum of its parts, and having broken a project down into constituent tasks it thus follows that a project's total effort is the sum of the efforts of all of its tasks (it is more complicated than that, but usually the point holds well enough). So by adding up all of the estimates associated with a project, we can determine a total estimate for the entire project. In a time-based system, this is expressed in terms of hours and days.



However, at this point we are working simply with numbers. We've established that due to the nature of creative work estimates are by definition non-concrete. So instead, we apply analytics to find out what “four hours” actually means in terms of calendar time. At this point, we're simply doing number analysis – averaging numbers together to produce a measure in terms of time. Since we have the same units on both sides of the equation, it follows that when these values on either side of the equation differ, then one of the choices of units is thus incorrect. It should be obvious that 4.5 hours does not equal 4 hours, so one of those figures must not really be “hours” as we know them.



Let's instead refer to the right side of that equation as points. Instead of 4.5 hours = 4 hours, we have 4.5 hours = 4 points. By removing the hours from the right hand side of that equation, we've suddenly addressed the subjective issue with our measurement system so far – we took away the time base in order to find the actual value, and as a result hit upon a number system that allows us to assign arbitrary values to tasks that develop meaning as a project progresses.



Building upon this gives us a more reliable means of estimation. Instead of assigning an hour estimate to each task, we assign a point value. The point value is indicative of the general effort required to complete the task, just as the estimate in hours was, but by removing the time value we remove subjective expectations. We assign higher numbers to challenging tasks, and lower numbers to easier tasks, knowing that on average the effort expended for each classification of task will average out to the same amount of effort, even if one specific task takes longer than another.



Tying it All Together
As we noted earlier, deadlines are inescapable. We cannot simply work forever. Thus, status reporting becomes a matter of determining how much longer the project will take to complete. We have a method of assigning difficulty to our tasks by giving them point values, and the point values are arbitrary units and thus remove all subjective judgments and perceptions. So our task at this point is to tie these points back into time periods.



This is actually what we were hoping to accomplish with our original estimation scheme – determine the amount of time it will take to complete a project. We simply hit upon the wrong units, and thus added a lot of extra cruft to our project plan. By trying to tie points back to hours, we become too granular – the points completed per hour varies far too much from task to task to give a worthwhile measurement. So the only option is to expand our averaging time window. This becomes an arbitrary choice, but I've seen the most success with week-long and two-week-long periods, known in the agile methodology as “Sprints”. You add up the points completed during each sprint, then keep a running average of the efforts completed. In doing so you tie the point values back into time values while also accounting for the aggregate variance of the data. For example – if I have a project that is has 170 units remaining, and I have been averaging 17 points completed per one-week sprint, I can say with a fair degree of confidence that there are 10 weeks remaining in the project.



This 17 number – the average point value completed during a sprint – is known as “velocity.” A project's velocity is used to relate the overall project duration back to the time required to complete it. By increasing the unit of measurement and divesting our estimates from subjective measures, we've introduced a more reliable system of estimation – simply divide points remaining by velocity. What this does is twofold. First, it gives you a quick and dirty estimate of the time remaining in a project that, over several weeks, tends to become very accurate as the amount of data to measure increases.



The second thing that it gives you is the ability to say no. Take, for example, a project that is starting to trend towards long hours. If you archive your data properly, you can point to previous examples where such an approach only made matters worse. Instead of “well, that will be pretty hard on the team,” you can instead say “We tried this before, and added 50 points of work while only achieving 47 from the increase in face time. How do you think it will be different this time around?” By looking at the point value of each task to be completed, some negotiation can take place and instead of giving subjective measurements and impressions, you can provide specific feedback with actionable data. Of course in some cases this won't do a damn bit of good, as the project deadlines may be particularly unforgiving, but in aggregate this approach should produce an environment that is collaborative and built upon a reliable history, as opposed to a relationship founded on distrust and fostered in a confrontational environment.



What does this mean for writing?

Ultimately, this method obtained from programming can be applied to any creative endeavor that can be assigned a subjective judgment of “easy” or “hard.” Simply break a project down into constituent tasks, then assign a point value to each task representing its difficulty. Of course after a certain point the tasks become repetitive – how many ways can “Write this scene!” be phrased, after all? However, one thing I have found when applying this approach to my own efforts is in support of my previous post on metrics – once you start putting your mind to measuring your progress in a more objective manner, you are able to get a better feel for how things are actually going with the project. While you may or may not have deadlines to work towards, and you may or may not have people waiting on your progress, the concrete proof of your progress is often enough to help you break through any bumps on the road, and stave off periods of despair over how long a given project is taking.

Monday, June 10, 2013

On Workshops and Wetware



This past Friday I attended a workshop presented by April Eberhardt and Susan Bearman entitled “Pathways to Publication.”  It was a very interesting workshop, presenting the “current” view of the ever-changing publication landscape as lived by two professionals. There was quite an eclectic group gathered in the conference room of Chicago’s University Center, representing essentially all stages of the production process and most of the phases of a literary career.

I have to say that while I had discovered a lot of the subject material on my own, I still found both the presentation and discussion useful. If you have an opportunity to attend a talk by one of these two women, I highly recommend the opportunity – they are both enthusiastic about their subjects, and energetic and engaging in delivery. Susan is an author as well as a marketing communications specialist, and April an agent with a list of clients at varying levels of the writing process.

My Primary Takeaways 

My primary takeaways from the conference were, in many ways, things I already knew. I am not a published author, nor am I particularly experienced at writing salable fiction, but I am (if I can toot my own horn here) excellent at researching topics and distilling the knowledge down to the salient points. Along these lines, I have done a lot of reading about writing and publication and have read points on all sides of the issue.

I tend not to write about publication and my opinions on the “right” or “wrong” way for two fairly simple reasons:
  1. I am not yet published
  2. I’d rather write than write about writing

There are hundreds of thousands of words out there about the various ways to get published, and they all boil down into the following categories:
  • Individuals who firmly believe that traditional publishing is the only way forward, and any who disagree are heartless blasphemers who will never shake the negative stigma of the self publisher
  • Individuals who firmly believe that indie publishing is the only way forward, and any who disagree are heartless blasphemers who will never earn even a tenth of their self-published peers
  • Individuals (and, most likely, the truth) who lie somewhere in between these two extremes

I use religious terminology in the above because in many cases that is the style that is taken by these blog posts and various discussions – absolutes thrown out with aplomb by individuals wholly dedicated to their particular cause, and god help the poor sap who dares to express a contrary opinion.

These people are not to be taken seriously. At least, not by me. They are informed by their own success, and thus may be biased towards what has worked for them. That is not to say that they don’t have any useful information, but arguments and opinions should always be taken with a grain of salt.

And ultimately, that was my key takeaway from the workshop. There is no right path. There are different paths, suited to different individuals, with different goals. Some people may want to make a living from their writing. An exceedingly small percentage of those people may achieve that goal. Some may only want the cachet of the title “Published Author,” and a small percentage may achieve that goal. Note the repetition of the phrase “small percentage” – the only true reality is that thousands and thousands and thousands of books are produced each year, and only a small number of those obtain publishing deals, let alone any kind of cultural relevance.

So in the end, this is what I gathered (right or wrong) from my time at the workshop:
  • Know your goal – am I looking to hit it big, or do I want the respect of a published writer, or do I simply want to create something that will live after I have died?
  • Plan your path forwards – what are measurable steps I can take towards that goal? How much will the options available to me cost me in time and/or money? How do I know when my goal has been achieved?
  • Do not dismiss any options until you are absolutely sure that they are not viable – the numbers game is already heavily weighted against me, would dismissing an entire market vertical help?
  • Finally, make your own conclusions – the only person with all the data on my situation is me, not an opinionated blogger or a pretentious literary critic, so why should their passion inform my decision if their reasons aren’t applicable?

The Fringe-Benefits, and Why I Will Never Be a Politician 

As any experienced conference attendee will tell you, the knowledge presented is only half of the reason for attending the event. If the knowledge was the only important thing, we could just download the PDF and go on our merry way as newly-enlightened writers. The other half of every conference, expo, convention, party, box social, et cetera, is the social aspect.

When I was a young college student getting ready to make my way in the “professional” world, I had a strong aversion to networking. I was earning a degree in Computer Science, which is based heavily in mathematics. In math, you are right or you are wrong, and there is no real room for in-betweens – that’s what statistics and probability are for. As I of course knew everything possible to know about the world at that age, I firmly asserted that I had no need of networking with potential colleagues. That kind of glad-handing may be necessary for business people and politicians, but I was a programmer. I just had to be the best programmer, and bam – job time for me. I envisioned myself living in a world of true merit, where the most talented were rewarded and the bull-shitters would be exposed and shamed.

We were all so naïve, once.

Some people say that money makes the world go ‘round. However, behind that money is a directing hand. This essentially means that the hand driving the money is just as important to the angular momentum of our planet as the money is itself. Thus, there are two paths to having an effect on the world:
  • Have lots and lots of money at your disposal
  • Connect with enough people with similar goals and work together to achieve what you need

Now this is a simplistic view of the world dedicated to show one fact: the only people who can afford to ignore the social side of the world are people with the fiscal resources to do so. Want to advance in your career? See and be seen. It is not enough to be damn good at what you do – that will get you local notoriety and aplomb, sure. If you want to make it big, though, you have to advertise. Be your own salesperson. Know your upsides and down, and emphasize the up while diminishing the down. Talk to people. Connect. Network. Make friends and find colleagues.

And this is where I fail. I like to describe myself as a quiet person. I have few social skills of which I am aware, and my sarcastic and self-deprecating nature can be off-putting to some people. On top of this, I have… while not exactly a fear of social interaction, I certainly have some sort of mental block against it. I rarely feel confident when introducing myself, and I’m by no means a people-person. To put it simply, I’m not an aloof ass – I’m just shy.

This is an issue that has plagued me for a while, and this past Friday it more or less reached a tipping point. I’m not great at networking (I even forgot to have new business cards made, as I am no longer a graduate student in computer graphics), and I tend to hang back by myself in a crowd. Here I am with a room full of people who can prove great people to know and potentially build a long-term correspondence with, and outside of a few smiles I only really talk to the people who approach me directly. A fantastic opportunity somewhat wasted.

In computer programming we see three phases of every solution: the hardware, with all the lights and sounds, that makes the program run; the software, with the thousands of lines of code, that makes the computer do what you want; and the wetware, with the hair and the appetites and the sporting team affiliations, that directs the entire process. Like far too many computer programmers over time I have focused a large portion of my attention on the two former, and not nearly enough on the latter.

And that’s probably my ultimate take-away from the workshop on Friday. Somehow I need to learn to be a people person, because even though I might be able to tell n interesting tale, nobody will read it if they don’t know who I am.

Long ramble, complete. Shutting down for now

Friday, April 19, 2013

Concrete Coding Corner - Productivity and Project Metrics

Project Management and You

As a programmer, one of the major things I spend my time talking about is how to measure productivity at work. Indeed, an entire field - project management - exists explicitly for this purpose. The ostensible purpose of this field is to provide metrics and milestones for business owners of projects, so that they have an idea of where a given project stands at any point in time. Of course, the cynic in me cannot help but point out the obvious: the entire field of project management is oriented around proving that a given individual, at any particular moment, is actually performing work. Project managers request task breakdowns, status updates, demos - all of the hallmarks needed to show that progress is being made, but it all boils down to the same thing: programming is essentially a black box for everyone but the programmer, and those without an understanding of programming sometimes need additional information to understand exactly what's going on.

You can couch it in all the business language you like, but the ultimate goal is to manage employees who develop software. Some organizations do so benevolently - using missed goals and milestones as learning opportunities as points of improvement. Others do so maliciously - using missed goals as a hammer to beat a programmer into extra hours in the pursuit of some arbitrary deliverable. Like most programmers, I've experienced both ends of the spectrum. Ultimately this is neither good nor bad - the use of project management techniques, like a weapon, is as benevolent as the intent of the wielder.

Hidden Benefits

One thing I've noticed, though is that while I may rail against the arbitrary metrics used to measure performance from time to time, there are indeed concrete benefits to these techniques when applied outside of the software engineering realm - particularly related to creative endeavors. Ultimately, I'd argue the major reason that many personal projects fail for many individuals (and they do fail - if New Year's Resolutions were written on paper, the entire world would be covered in the crumpled dreams of millions of resolvers) is that they simply lack means to measure progress. Self improvement, for example, is only useful in the chance that it actually produces improvement. 

Take an aspiring runner - given the lack of any information or motivation, the individual needs to decide on their own whether or not the activity of running is producing an effect. They need a metric - a means of measuring progress. Most of the time, the only metric available by default is the uncertain metric of how our bodies feel at any given point at time. This can be a good metric, particularly when working towards fitness goals, but it is also inherently flawed in that "body feel" can be influenced by any number of factors. A bad sleeping position produces a pulled muscle, and all of a sudden your progress metric is thrown off by an unrelated issue. Most people, with enough of these false indicators, will eventually give up on their goal. If they can't measure progress, then they can't see that their efforts are actually paying off.

Metrics

The source of the problem is in producing objective metrics - metrics that rely not upon an arbitrary element of the situation, but that focus on concrete results. One example is in practicing a musical instrument. In my spare time I play brass instruments, and in order to achieve quality tone and technique a brass player needs to spend hours practicing. However, with brass playing it is also very easy to slide once you reach a certain ability level - you find that you can put out a moderate level of adequate performance and that this adequacy, while not particularly impressive, is sufficient. The primary way to advance past mere adequacy is to work on fundamentals - sets of exercise that are equivalent to strength and agility training for brass players. These fundamentals are vital to building proper technique and muscle mass for endurance, but they are also extremely boring (and in some cases, borderline painful). After several practice sessions that seemingly fail to improve this adequacy, it is far too easy to write off the activity of fundamental practice altogether and focus exclusively on the music. We've identified a similar problem to that of the programmer. Our goal is concrete - become an amazing player - but the means by which we have to measure our progress are inexact. We're relying on inadequate body feel and the ephemeral concepts of a "good sound" - something that can be hard to identify without outside observation.

This is the issue faced by project managers when overseeing programming projects. Programming, to them, is a black box. On the surface, all they have is the equivalent of body feel - they have assurances from the programmer that everything is on track, or problem reports as they arise during development. These end up giving false indicators. The project managers, as a result, focus on goals that can be measured objectively in order to give them a more uncluttered view into the progress of a project. While this work seems arbitrary to the programmer (and in some ways it is, as from a certain perspective the need for this information is birthed from an inherent distrust between individuals - else there would be no need for assurances that work is actually occurring), it gives the project manager an objective view of the project and mollifies their concerns.

Application of Metrics

The end point of all of this is that project management principles are not exclusive to programming projects in the workplace. One solution to the body feel problem, which I have found successful, is in breaking the goal down into objective measures. For my brass playing, I developed a spreadsheet system. Along the top of the spreadsheet I put down metronome markings, starting at 60 BPM and increasing to 208 BPM (an arbitrary choice on my part that represented "very fast"). Down the side of the spreadsheet, I listed chromatic tones - C, C#, D, D#, E, and so on. I then printed out about twenty of these sheets, and assigned a sheet to every fundamental exercise: one sheet for lip slurs, one sheet for tonguing exercises, one for Clarke technical study #3, one for chromatic studies, and so on. 

This gave me a grid of concrete milestones - objective goals that I could check off as a list. As I would complete the requirements for a goal, I would write the date in the corresponding cell. For example, if I completed the F# Clarke Study at 140 BPM on February 2nd, I would write "2/2" in the corresponding spreadsheet cell. Over the course of several days of practice I would slowly fill in the spreadsheet with dates, and after a while it was possible to see progress very clearly. Where before I would easily get frustrated practicing technical exercises, reaching that wall where the fingers only want to fumble and the lip feels stiff and unworkable, with the new system I could look down at my spreadsheet and see that I had already completed three cells for the day, and feel confident in moving on. 

It took away the human tendency to focus on the negative - the problems faced as I worked on a particular exercise could dampen my mood very easily - and instead highlighted the positive. I could look back on my spreadsheet at any time and see the period of time where I couldn't perform the current exercise faster than 60 BPM, and realize that the troubles I'm facing at 120 BPM are a mark of progress rather than purely  a source of frustration. I was able to measure my progress based on where I had come from, rather than where I was headed. I was celebrating the mile I ran continuously, rather than lamenting my inability to complete a marathon. The marathon would come, just as surely as completion of the current exercise would come.

Metrics and Writing

Most writers debate this technique without knowing they are doing so by focusing on word count. Some writers proudly claim they only complete 500 words a day, but those 500 words are rock-solid. Other writers pound out 2,000 or more words in a day and are pleased with their progress, leaving rewriting for later (in the interest of full disclosure: I typed at a rate of 2,083 words per day when completing my first novel, with a high water mark of 10,000 words in a single day. I obviously fell into the latter category). The issue faced is that while word count is indeed an objective metric for writing, any individual can quickly tell that it is in no way indicative of quality. This tells us one thing: our metric is inadequate. We have found an objective measure, but not the right objective measure.

Of course the blogosphere constantly debates the issue of quality versus quantity, but ultimately we end up coming back to the same issue: what are the fundamentals for a writer? What is a way we can work on these fundamentals objectively in order to produce measurable progress that results in increased quality? We have critiquing, which despite the attempt at objectivity is almost entirely subjective. We have editing, which suffers from the writer's blind eye when working on their own pieces and suffers from the subjective perceptions of an external editor when performed by an outside party.

This is something that has been on my mind lately, and I'd argue that it's a concern of every writer. How do we know that what we write is actually good? Are we practicing the right things? Is there an objective measure of "good" or "bad" when it comes to art? I have my own ideas, but I am open to suggestions. Until then I am left with an imperfect metric of word count goals, which I pursue with vigor.