Anonymous user
User:Lhignight: Difference between revisions
m
Fixed language names (part 2)
(Added the Why RC and Quotes sections) |
m (Fixed language names (part 2)) |
||
| (5 intermediate revisions by 2 users not shown) | |||
Line 1:
<!-- Considering writing a BASIC to ??? translator for the old astronomy programs -->
<!-- Linking a project euler problem w/ code from RC
<!-- Add JNI w/ the LabJack to the different documents -->
<!-- A category for OOP design patterns (w/ invisible), functional programming and data structures similar to the sorting category. -->
<!-- Secure the facebook account -->
<!-- Finish the top of code portfolio -->
<!-- I would like to see badges or some other nifty item for particularly well-written examples, elegant solutions, etc. -->
<!-- An automated unit test framework for the submitted software would also be cool -->
{{mylangbegin}}
{{mylang|BASIC|Moderate (Rusty)}}
{{mylang|C|Skilled}}
{{mylang|C++|Moderate (Rusty)}}
{{mylang|C sharp|Skilled|C#}}
{{mylang|Clojure|Curious (Learning)}}
{{mylang|Common Lisp|Skilled}}
{{mylang|Emacs Lisp|Moderate}}
{{mylang|F
{{mylang|Haskell|Novice (Learning)}}
{{mylang|Java|Skilled}}
{{mylang|Mathematica|Novice (Learning)}}
{{mylang|
{{mylang|Prolog|Novice (Learning)}}
{{mylang|Python|Moderate}}
Line 18 ⟶ 27:
{{mylang|UNIX Shell|Moderate}}
{{mylangend}}
Hello, you have reached the Rosetta Code user page for Larry Hignight. It was in sixth grade, while learning to program in BASIC and Logo, that I caught a pretty serious case of the computing bug and convinced my parents that I ''needed'' a personal computer. Sometime in 1998, I became interested in the Linux operating system and began frequenting the IRC channel of [http://en.wikipedia.org/wiki/Loki_Software Loki Games], whose primary business was porting Windows games to the Linux platform. This led to my working as a beta tester on the [http://www.mobygames.com/game/linux/descent_/credits Linux port of Descent 3] and writing a Linux StepByStep guide for installing [http://linux-sxs.org/multimedia/smpeg.html SMPEG - The SDL MPEG Player Library] on Caldera Open Linux.
I began working as a software developer in 2004 and have completed a number of projects in industry and academia: California State University Fullerton (~1 year), Boeing (~5 years), USC ([http://www-bcf.usc.edu/~dkempe/former-students.html research] - 1.5 years while working at Boeing) and Embry-Riddle Aeronautical University (5 months). While at Boeing, I worked on teams responsible for a number of satellite programs, including DirecTV, XM Radio, Wide-Band Gap Filler (WGS), Global Positioning System (GPS), New Skies (NSS), and SSP (Boeing's internal name for the Future Imagery Architecture satellite system).
[[File:Project_Euler_Larry_Hignight.png|left|alt="http://projecteuler.net/profile/Larry_Hignight.png"]] In addition to Rosetta Code tasks, I have also submitted solutions to fifty-six [http://projecteuler.net/problems Project Euler problems]. Unfortunately, Project Euler doesn't support a public profile page, just a [http://projecteuler.net/profile/Larry_Hignight.png profile image], which I've included here (Note: The image will sometimes not appear due to bandwidth or permission issues -- I need to work on it). I also have [http://www.linkedin.com/pub/larry-hignight/28/46b/893 LinkedIn] and [http://www.facebook.com/larry.hignight Facebook] accounts.<br /><br />
=== Why Rosetta Code ===
I have always found well defined programming tasks to be an extremely beneficial learning tool for developers: whether it be learning a new language, a programming technique, a language paradigm, or simply a new type of problem. Not only does RC provide interesting tasks, but the diversity of the tasks, developers and programming languages is quite outstanding. This is especially true for developers interested in expanding their knowledge beyond mainstream programming languages. After all, you're not likely to benefit from a paradigm or language which you haven't been exposed to at some point. In that regard, most of the tasks that I've implemented on RC involve programming languages and paradigms that I haven't used extensively at work.
=== My Contributions ===
Line 119 ⟶ 134:
*The parser is 5 SLOC (even w/ having to parse square brackets); The writer is ~20 SLOC
**By comparison, the Java parser consists of 6 classes and ~200 SLOC
*Few languages have contributions for the harder task of writing S-Expressions
|}
| |||