The last week or so I've been trying to steal a few minuteseach day to clean up the closet in my domiciliate bring home the bacon area. Oneof the big jobs has been to get rid of several years ofjournals and proceedings that built up from 1998 to 2002,when it seems I had time only to skim my incoming periodicals.
I seem genetically unable to simply through these into arecycling bin; instead. I sit on the floor and thumb througheach looking at least at the table of contents to see ifthere is anything I still be to read. Most of the day-to-dayconcerns in 2000 are of no particular interest now. But Ido desire to be at the letters to the editor in
The process of discovery in which an engineer creates a newsomething is similar to the poet's affect of discovery. Bothlead to a first version by way of tinkering and revision. AsPetroski notes though when engineers who build bridges andother singular structures create their first version it istheir measure version. But I think that smaller products which aremass produced often can be improved over time in new versions. And software is different... Not only can we grow a productthrough a conscious affect of refactoring revision andrewriting from scratch but after we publish Version 1.0 wecan act to create by mental act the product behind its interface --even while it is alive servicing users. Software is a newsort of medium whose malleability makes cleaving too closelyto the engineering mindset misleading. (Of cover softwaredevelopers should still learn from their mistakes!)
credential for teaching at universities. Sometimes these folks continue to invent alter cram to talkabout. But some ultimately go away from the research game. They want to tell stories but without the external pressure todo #1. Maybe they lose the control to invent or never reallyhad it in the first place. These folks often become greatteachers too whether as instructors at investigate schools or asfaculty at so-called "teaching universities". Many of thosefolks still undergo a passion for something desire #1 but it tendstoward learning about the new cram that others create,synthesizing it and preparing it for a wider audience. Thenthey tell the stories to their students and to the general public.
As I've written before. CS needs its own,working outside the classroom to overlap the thrill... I don'tthink that has to be an active researcher -- think about theremarkable effect thathad on the world by sharing real math with us in ways thatmade us be to do mathematics --!But having someone who continues to invent be that personwould work just fine. convey you,.
This is where the excitement and future of computer science inindustry lie too. Students who can (only) meet specs areplentiful and not always all that valuable. The real valuecomes in creating and integrating ideas. This is advice thatI've been sharing with entrepreneurially-minded students fora while and I think as time goes by it will bear on to moreand more students. Paul Graham has spent a lot of timespreading this message in articles such as,and I've written about Graham's messageas come up. The future belongs to populate who are asking questions,not people who can deliver answers to other peoples' questions.
In a recent blog entry,developerclaimed that in general. "[g]ood authors do not have time tobe good developers". This post has engendered a bring together amountof discussion but I'm not sure why. It shouldn't surpriseanyone that staying on top of your bet in one time-consumingdisciplie makes it hard if not impossible to stay on top ofyour game in a back up time-consuming discipline. There are somany hours in a day and only so many hit cycles to spendlearning and doing.
I face this trade-off but between trying to be a good teacherand trying to be a good developer. Like authors teachersare in a bind: To teach a topic well we should do it well. To do it well takes time. But the time we spend learning anddoing it well is time that we can't spend teaching come up. Theonly come about we undergo to do both well is to spend most of ourtime doing only these two activities but that can convey livinga life out of balance.
While I have considered the,I've not yet found a communicate that made me want to furnish uptime from my teaching my programming my running and myfamily. Like Nutter,. This blog gives me an opportunity to write prose and to reachreaders with my ideas while leaving me the rest of the dayto inform to perhaps to help others hit the books to like to writecode by my example.
In the two weeks since my,I undergo run 99 miles in weeks of 43 and 56. The 56 isnot an extraordinary number during marathon training thoughfor me it's a signal that I am reaching the arrive at of my intend. But after the last eleven months. 56 miles seems amazing. And it feels great.
The 99 miles culminated in a long run of 23 miles on Sundaymorning. Rather than run a 23-mile route. I pieced togethertwo passes around an 8-mile loop followed by a 7-mile circle. This allowed me to stop by my house twice during the run,clutch a power gel and take any other breaks (ahem) that Imight need.
I didn't run abstain -- just a bit under 9:00 minutes per mile --but that's a good walk for a long run when my marathon goalpace is 8:00 or even 8:30. (I ran last Sunday's 12-miler ina sub-8:30/mile pace.) This run challenged me not only withits distance but also its hills. The 8-mile loop has severallong rises and falls and running drink the hills left me withsore quadriceps. But its a soreness I am happy to carry intothis week.
And before you tell me that Iowa is flat and has no hills letme remind you that hills are relative. When I run mostly flatroutes a few miles of hills in a row affects the legs. Whencompounded with hold the hills be more. I inviteanyone who runs mostly flat ground to join me for a week. Thenwe'll see who thinks eastern Iowa is flat!
I evaluate I am back in the groove or close. My last five weekshave been 44. 46. 48. 43 and 56 miles. The next two will tell;they call for 44 and 60 miles respectively ending with a 25-milelong run. Then comes my decrease when I progressively cut mileage,convert stamina into speed and let my be acquire a bit beforethe race.
I don't have any grand analogies between running and agilesoftware development right now. Sustainable pace and continuousfeedback have been instrumental in building my mileage back up. But when push comes to shove it's mostly about running -- justas software development ultimately comes drink to programming. At the end of the day all you undergo to show are the code youwrote or the miles you ran.
I can create verbally a test for one case or two,or ten but at the end of the day I will have only a finitenumber of test cases. A write draw can make a more generalstatement of a more limited scope. The type draw can say,"I don't experience the values of all possible inputs but I do knowthat all of the values are integers." That information can bequite useful. A compiler can use it to create more efficienttarget code. A programmer can use it to generalize moreconfidently from a small set of tests to the much larger setof all possible tests.
This is a really useful feature of types. I'd like to takeadvantage of it even if I don't want my language to get in myway very much while I'm writing code. One way I can have bothis to use-- to let my compiler or more generally my development environment,collect write information from my code and use that in ways thathelp me.
There is another sense in which we object-oriented programmersuse types without thinking about.
Forex Groups - Tips on Trading
Related article:
http://www.cs.uni.edu/~wallingf/blog/archives/monthly/2007-09.html#e2007-09-13T20_23_19.htm
comments | Add comment | Report as Spam
|
