jvns

20 ms·

151.
Using strace to avoid reading Ruby code(jvns.ca)
2 points by jvns 13y ago|0 comments
152.
by jvns 13y ago
You can ask anything you want. Prefixing your questions with "I want to know what I'm getting into before I bet my family's well-being on it" is a great way to start. When I was interviewing, I asked literally anything I
153.
Spying on ssh with strace(jvns.ca)
2 points by jvns 13y ago|0 comments
154.
Dear sir or madam: the bookmarklet you didn't know you needed(notwaldorf.github.io)
2 points by jvns 13y ago|0 comments
155.
Three steps to learning GDB(jvns.ca)
2 points by jvns 13y ago|0 comments
156.
by jvns 13y ago
Ask questions. Ask lots of questions. The thing that makes the saddest is to watch a new person flounder and waste days trying to figure out something on their own which I could have easily helped them out with.
157.
Women who program aren't unicorns(medium.com)
4 points by jvns 13y ago|0 comments
158.
by jvns 13y ago
Good question! This year I started by giving talks at local user group meetups (Montreal Python), and then my friend encouraged me to submit a talk to PyCon Canada, and the same talk got accepted to PyCon 2014.
159.
by jvns 13y ago
If you're looking for a stable language you shouldn't use Rust right now. The language is still changing every few days. If you have a bit more time to spend it's fun, though -- I spent a lot of time in the IRC channel. The p
160.
Paths to being a kernel hacker(jvns.ca)
84 points by jvns 13y ago|17 comments
161.
by jvns 13y ago
One way to deal with this is to ask at the beginning of an interview how much time there is for questions. Once you have an offer, you can also schedule extra interviews just for you to ask questions.
162.
by jvns 13y ago
Yup -- definitely use your discretion here. I'm nervous about asking a lot of these in a first interview, but once I have an offer I'll ask pretty much anything.
163.
Questions I'm asking in technical interviews(jvns.ca)
144 points by jvns 13y ago|40 comments
164.
Short survey on using "guys" to describe programmers. Answer it for science? (docs.google.com)
2 points by jvns 13y ago|0 comments
165.
Understanding how killall works using strace(jvns.ca)
65 points by jvns 13y ago|29 comments
166.
by jvns 13y ago
Yup, all the standard library. If you look at the top of main.rs [1], you'll see #[no_std] which means "don't use the standard library" Instead of the standard library, I use rust-core [2], which provides some of the sta
167.
by jvns 13y ago
I do! The main issue there is that my build process is a bit broken -- my version of clang is not quite right somehow, and so I can't build properly without making some janky changes to rust-core.
168.
by jvns 13y ago
Maybe! Why are Linux syscalls odd? How would you do it instead?
169.
I now have Rust code for executing executables(jvns.ca)
145 points by jvns 13y ago|22 comments
170.
by jvns 13y ago
This article is pretty great. I used it as a reference to write gunzip in Julia: https://github.com/jvns/gzip.jl
171.
Something is erasing my program while it's running (oh wait oops)(jvns.ca)
78 points by jvns 13y ago|26 comments
172.
How to run a simple ELF executable, from scratch(jvns.ca)
2 points by jvns 13y ago|0 comments
173.
12 things I learned today about linkers(jvns.ca)
2 points by jvns 13y ago|0 comments
174.
Linkers are amazing.(jvns.ca)
1 points by jvns 13y ago|0 comments
175.
Writing malloc wrong, for fun(jvns.ca)
45 points by jvns 13y ago|24 comments
176.
After 6 days, I need to look at generated assembly to debug(jvns.ca)
4 points by jvns 13y ago|0 comments
177.
After 5 days, my OS doesn't crash when I press a key(jvns.ca)
259 points by jvns 13y ago|88 comments
178.
by jvns 13y ago
Another cool thing about writing Rust is that the language is really alpha, so you'll run into language bugs or rough spots if you use it seriously for any amount of time (like a week).
179.
by jvns 13y ago
> you have to know the language quite well to be able to avoid the parts that require runtime support. This isn't really true, it turns out :) I've only spent about a week using Rust. I spend a ton of time in #rust asking quest
180.
by jvns 13y ago
Right now it's a fork of rustboot [1], a proof-of-concept repo for implementing a kernel in Rust. I'm working on extending rustboot [2] to support handling keyboard interrupts and to have a real print function. It's not remot

More ›