News for hackers. Stuff that matters.
Re:Tips to succeed as a programmer (Facebook engineering Notes) by tdr on Wednesday April 25, 2012 @10:41AM (#3889292)
Timeless advice for any software engineer!

The one thing to add (related to 1 and 3) is:

     *do not focus completely on the technology. learn what's around it also*. 
I once worked for a company where 1 week/month the managers would work in 1 department (as regular team members). With the hands-on feedback, they would improve the process/team/business. Needless to say, that company was making profits in the 2008-2009 "dark-age period".

The main lesson for me is that software is the business where you learn about & improve other businesses. The value is that you get to understand better the world (business) around you. That way you can avoid building "innovative products" that no one needs.

Re:Tips to succeed as a programmer (Facebook engineering Notes) by invalidOrTaken on Wednesday April 25, 2012 @10:58AM (#3889361)
This sounds similar to the edw519 approach of "talk to people, see how you can improve things."

I think there's a lot to be said for it. I suspect we (as a species) waste a lot of time because we're ignorant of the big picture.

Re:Tips to succeed as a programmer (Facebook engineering Notes) by tdr on Wednesday April 25, 2012 @11:17AM (#3889450)
Not only that, but you also strengthen the relationship and stay up-to-date (micro & macro).

In some cultures (eg. ex-communist countries) there is a natural "distance" (approachability) between employees and management. I did not see this in Western Europe (at least at such level)

EDIT: thanks for the tip about edw519 ( https://twitter.com/#!/edw519 ). New feed to read!

Re:Tips to succeed as a programmer (Facebook engineering Notes) by JoachimSchipper on Wednesday April 25, 2012 @10:36AM (#3889272)
Re:Tips to succeed as a programmer (Facebook engineering Notes) by Drbble on Wednesday April 25, 2012 @01:03PM (#3889934)
Patio is a successful "small tech consultant", and enjoys blogging and sales and marketing. Some people prefer to lean more heavily/exclusively to technology and math, and they are needed and well rewarded to work on large technical systems. (My team is hiring. )
Re:Tips to succeed as a programmer (Facebook engineering Notes) by Estragon on Wednesday April 25, 2012 @02:30PM (#3890367)
As far as I can tell, you have provided no contact information at this stage, so the information that you're hiring may not do anyone any good. :-)
Re:Tips to succeed as a programmer (Facebook engineering Notes) by Drbble on Wednesday April 25, 2012 @06:25PM (#3891436)
I am confident that you've heard of us and others like us, and know how to apply.
Re:Tips to succeed as a programmer (Facebook engineering Notes) by AznHisoka on Wednesday April 25, 2012 @12:01PM (#3889625)
I had the same thoughts as I was reading this... why limit yourself to success as a programmer? Why not success as a problem solver?
Re:Tips to succeed as a programmer (Facebook engineering Notes) by gaius on Wednesday April 25, 2012 @05:08PM (#3891095)
1. Look for jobs that will let you program. ...  You want your job title to be ‘software developer,’ ‘software engineer,’ ‘programmer,’ ‘coder

Followed by

Goranka Bjedov is a capacity engineer

Hmm.

Re:Tips to succeed as a programmer (Facebook engineering Notes) by jon6 on Wednesday April 25, 2012 @02:47PM (#3890437)
I love how I can just read the bullet points and glean 90%-95% of what the post is about. So many blogs waste words.
Re:Tips to succeed as a programmer (Facebook engineering Notes) by bsphil on Wednesday April 25, 2012 @10:36AM (#3889271)
Reading code always worried me. That was always my biggest deficit in school - I couldn't just pick up someone else's code and dive in, it took a lot of effort to understand anything more than the most basic code.

Of course, now I'm not in a programming job, so I can only imagine I've gotten worse.

Re:Tips to succeed as a programmer (Facebook engineering Notes) by calibraxis on Wednesday April 25, 2012 @11:03AM (#3889381)
Well, OPC (Other People's Code) is generally unpleasant to read. ;) Rarely do people try to write programs "for people to read, and only incidentally for machines to execute", as SICP puts it.

So, I think it helps to do more than just passively "read" it. I might create a private branch, run the sucker with lots of print statements, comment the hell out of it, take copious notes in org-mode, draw diagrams to leverage my visual systems, etc. (It might feel silly, but no one's watching.)

Running it repeatedly (with print statements) allows me to form little hypotheses and test them. The idea is to approximate having a REPL. Something like emacs helps to automate this as much as feasible.

Re:Tips to succeed as a programmer (Facebook engineering Notes) by Drbble on Wednesday April 25, 2012 @12:58PM (#3889911)
Don't add printf, add unit tests!
Re:Tips to succeed as a programmer (Facebook engineering Notes) by gaius on Thursday April 26, 2012 @03:23AM (#3892862)
Printf tells you "this function entered, then that function" while the program is running. Unit tests are trendy, but how do you know what to unit test before you even know the code paths? Do you even care about individual functions at that level? Printf may be dirty, but in the initial stages it's better even than a debugger with breakpoints.
Re:Tips to succeed as a programmer (Facebook engineering Notes) by calibraxis on Thursday April 26, 2012 @05:16AM (#3893050)
Interesting, I too kind of believe that print statements are better than debuggers, but I always thought that was an irrational belief on my part. (Like, I often don't have a decent debugger available, so never got much experience using them.) What are your reasons?
Re:Tips to succeed as a programmer (Facebook engineering Notes) by gaius on Thursday April 26, 2012 @05:50AM (#3893122)
It's just easy, intuitive, doesn't require any scaffolding, and gives you just the information you want, exactly as your program sees it, yet with the full power of the language to format it exactly as you want to see it, in the most useful way. A breakpoint will do the same thing sure, but only by stopping your program in its tracks! Dtrace is the only thing I've seen that is as useful as liberally sprinkled printf's.

A unit test will tell you if you know what output a function should give for a given input, that it does. Ermm, brilliant, but what if that function isn't on your code path anyway? And assuming that you already understand the program well enough to create any state the function expects if it's impure. Above poster has drunk too much Kool-aid and is suffering from Golden Hammer Syndrome ;-)

Re:Tips to succeed as a programmer (Facebook engineering Notes) by roguecoder on Wednesday April 25, 2012 @10:51AM (#3889341)
It's really about practice and context.

Context makes it so much easier. In the real world there is usually a purpose to code, and good code has a cohesive metaphor you can understand before you start reading. Practice eventually makes the syntax second-nature, but I found being able to understand the context and subtext of the code is a much bigger boost.

I took a poetry class in college and found that learning to read poetry helped me become more fluent at reading code. Instead of reading it like prose, from start to finish, reading poetry is about building a mental castle of what the poet is talking about, and then the actual words fill in the important details. Plus you learn to pick up on repetition, rhythm, deviations from established patterns and is-a relationships ;-)

Re:Tips to succeed as a programmer (Facebook engineering Notes) by meej on Wednesday April 25, 2012 @06:13PM (#3891393)
At least you understand how important it is. I graduated from engineering school in 1999 and I still marvel at the classmate in my data structures class who complained that there were too many code reading exercises on the exams during the semester-end course evaluation. It was like he thought he would spend his life writing code and never reading it, I was amazed.

I recently started programming at work after at least a decade of mostly not programming at work. My experience so far has been that reading code is easier than writing it, at least when an unfamiliar SDK is involved.

Re:Tips to succeed as a programmer (Facebook engineering Notes) by swapsmagic on Wednesday April 25, 2012 @04:28PM (#3890895)
For me it's the other way around. Reading and understanding others code is easier for me rather developing it from scratch in the beginning. Though now i have improved in the later part.
Re:Tips to succeed as a programmer (Facebook engineering Notes) by brunohq on Wednesday April 25, 2012 @04:58PM (#3891050)
in fact, these are valuable lessons for any position. Specially, the last one.

1. Look for jobs that will let you <do whatever you want to do>. 2. Don’t give up on becoming <whatever you want to become>. 3. Learn how to take charge of your career.

Re:Tips to succeed as a programmer (Facebook engineering Notes) by denzil_correa on Wednesday April 25, 2012 @06:34PM (#3891460)
Crisp and to the point. Likes it.
Re:Tips to succeed as a programmer (Facebook engineering Notes) by perlpimp on Wednesday April 25, 2012 @10:18AM (#3889193)
404
Re:Tips to succeed as a programmer (Facebook engineering Notes) by Maven911 on Wednesday April 25, 2012 @12:36PM (#3889809)
I had to hit refresh a few times to get a page that loaded
Re:Tips to succeed as a programmer (Facebook engineering Notes) by jerryji on Wednesday April 25, 2012 @10:33AM (#3889257)
works for me