720 karma · joined February 15, 2009
--John McCarthy, http://www.infoq.com/interviews/Steele-Interviews-John-McCar...
I think commit messages are the appropriate place for this stuff; I use `git annotate` etc. to find the information when I need it. I often have a 50-line commit message accompanying a one-line code change -- a ratio that would obviously make the code unreadable if all the comments were in-line with the code itself.
http://www.inference.phy.cam.ac.uk/withouthotair/c15/page_95...
http://www.inference.phy.cam.ac.uk/withouthotair/c20/page_13...
And not just Haskell and OCaml: See for example https://github.com/drothlis/pretty-symbols
(though of course Haskell and OCaml might be much more suited to this kind of visualisation -- in python, say, you just get λ ≠ ≥ ≤).
I played with this idea in the syntax highlighting of the code samples in this article: http://david.rothlis.net/c/compilation_model/#chapter005
but would you want all variables at the same scope in the same colour? Different colours for each variable, with the darkness/lightness indicating the scope?
> grep-only highlighting—define a set of things to grep for quickly and highlight them.
Emacs has this with the "highlight-regexp" command. To be honest I don't use it that much. What I do like is highlighting all matches whenever you're doing a "find in file" (though unlike highlight-regexp, the highlighting disappears as soon as you exit the search). I probably use this more because I use search all the time (who doesn't), whereas I tend to forget that "highlight-regexp" even exists.
> block-focused—highlight code blocks so you get an idea of the overall structure of your program.
A few examples of how this might look: http://web.archive.org/web/20080723220126/http://lemonodor.c...
> No-highlighting
In Emacs the "font-lock-mode" command will toggle all highlighting; and you can specify the "level" of highlighting you want by setting the "font-lock-maximum-decoration" variable (you could set up a specific key to toggle this variable). I think these levels were originally intended for performance reasons, so they're cumulative (enabling level 3 also brings in all the highlighting from levels 1 & 2) rather than individually-toggleable features.
I only bring up Emacs because that's what I'm familiar with, and because I'd like more people to experiment with these types of things in Emacs. But perhaps Sublime Text would be a better platform for such experiments, for some people; I don't know.
At YouView we are automating the testing of our product (a set-top box) using stb-tester[1], a tool that we developed and open-sourced which captures video from the set-top box and analyses it in real time.
These are early days for the project, so you can have a large impact on its direction and success. One week you might be writing a python module to control a network-controllable power supply; another week it might be a script to generate comprehensive test coverage of a menu tree. There will be tedious work too, but we want the kind of person who hates tedious work so much that they automate it away.
Unix shell scripting and administration experience is highly desirable. The test scripts themselves are written in python.
Currently stb-tester's image processing is very simple: It looks for specific, previously-captured images, accounting for some noise. But there is plenty of scope for much smarter processing: Identifying areas with text within the image, then doing OCR; or measuring some aspect of image or video quality.
If you're interested send me an email for help getting started, and see the 2 latest commits on https://github.com/drothlis/stb-tester/commits/motiondetect_...
I usually use perl/sed/awk + markdown for generating html from my own made-up mini-formats. I'd love to keep the sources in org-mode instead, but I wonder whether elisp is the right language for the type of text munging I want to do.
If you like this approach, I've written a guide (http://david.rothlis.net/emacs/customize_c.html) which, at 3,000 words, is half the length of the Emacs manual table of contents.
Games is not a problem. It's expected for a new graduate that most experience will be projects such as those. You have more projects to show than most graduate CVs I see; this is a strong plus.
I'd like to see links to your code; the screenshots don't tell me much. (I look for tidy, well-documented code; it shows conscientiousness.)
On the first page I would like to see clickable links to the website for each project/product you worked on (and to source code if possible). Perhaps the whole CV would work better as a single page (or two) with links to your website for each project.
I don't know the official meanings of the words, but to me "Resume" and "CV" are the same thing.
Nitpicks: Some slightly awkward grammar & hyphenation on the first page. The formatting in the "Skills" section is a bit weird. Include a country code in your phone number.
If you're interested in a permanent position in London, send me an email (see my profile).
My team writes middleware (i.e. software that interfaces with OEMs' software and with the GUI team's software) for set-top boxes. We use a bit of C, a bit of C++, a bit of shell, a bit of Python. We have a great team and you will learn a lot.
As your first task we'll probably get you to do some bug-fixes and feature work on Polipo (an open source HTTP proxy) and you would be pushing your patches upstream.
> 'interactive' is when called with -i flag (which sshd does when reached by
> ssh with no command passed, i.e if you do 'ssh ls' it should not call
> bashrc, but should call bash_profile)
Re. ssh, the bash man page says (at least on my system, with bash 4.2.37): "Bash attempts to determine when it is being run with its standard input connected to a network connection, as when executed by the remote shell daemon, usually rshd, or the secure shell daemon sshd. If bash determines it is being run in this fashion, it reads and executes commands from ~/.bashrc".
That last quote from the bash man page contradict my own experiments. Logging into my OS X system with ssh loads .profile, not .bashrc. The same is true logging into my Fedora 17 system with ssh. Perhaps sshd uses --login instead of -i (or, on my systems, happens to be configured in that way).
Running a command via ssh ("ssh hostname somecommand") loads nothing when the remote system is OS X, and loads .bashrc when the remote system is Fedora 17.
All in all, I will respectfully disagree that "there is no madness". Normally I completely relate to the RTFM sentiment, and I have spent plenty of time in the bash manual myself.
I remain unconvinced that there is a better solution than putting everything into .bashrc (with the $- guard around stuff specific to interactive shells) and doing nothing in .profile other than unconditionally sourcing .bashrc.
> [[ $- == *i* ]]
login shell .profile
interactive non-login shell .bashrc
run by the remote shell daemon .bashrc
log into OS X user account (nothing)
new terminal .profile
run "bash" from that terminal .bashrc
run a shell script (nothing)
ssh hostname .profile
ssh hostname somecommand .bashrc
* .profile does nothing other than source .bashrc
* In .bashrc anything that should be specific to interactive shells goes inside:
if [ -n "${-//[^i]}" ]; then
...
fiI wish people would add a one-line comment to the top of every source file saying what it's for. ONE LINE is all I ask.
I use:
(set-face-attribute 'default nil :family "Menlo" :height 120)
(set-fontset-font "fontset-default" 'unicode "Menlo")For those reasonably comfortable with Emacs, I think you should build it from source, and get into the habit of fixing tiny documentation problems as soon as you come across them. Mind you, I have submitted a couple such patches to the ido built-in help and they have languished un-noticed for 2 months.
P.S. Another thank-you here for the starter kit -- I no longer use it, but I did for a year or so and it did teach me several features I wouldn't have known about otherwise.
:-(
This PDF file is optimized for screen viewing, but may
easily be recompiled for printing. Please see the
preamble of the LATEX source file for instructions.
For those already using CMake--ninja will slot right in.
Are there any large projects using premake? Ninja+gyp is used by Chromium.
I recommend my own guide http://david.rothlis.net/emacs/howtolearn.html which teaches you how to use the Emacs built-in help, the elisp source code, and the built-in access to these very manuals.
[1] lynx --dump http://www.gnu.org/software/emacs/manual/html_node/emacs/ind... | sed '/^References/,$ d' | wc -w