Home
Joel Liu's Library tagged → View Popular
Shanghai High-Schooler Wins International Coding Crown - China Journal - WSJ
-
This year, Facebook and the National Security Agency were sponsors — and both are using the event for recruiting purposes.
The best of the best was 18-year-old Bin Jin, a high school student from Shanghai, who swept the algorithm competition and beat contestants with doctoral degrees, as well as Petr Mitrichev, a Moscow State University student and three-time world algorithm champion.
Crazy On Tap - Lessons learned in 30 years of programming
-
3. Don't play any blame games. It doesn't matter who put the bug in. Again, your co-workers will be more loyal to you if you soft-pedal problems they introduce. I often apologize for bugs found, and gently argue with people that it was indeed my fault, when we both know it wasn't.
For women: Inspiring Women Interview: Corrinne Yu - Kombo.com
-
If you don't know who Corrinne Yu is or what she has done, you are in for a special treat. Corrinne Yu is Principal Programmer at Microsoft's Halo team, and first party Halo Lead. She is the first and only female Technical Lead of the whole Microsoft Game Studios. She has worked as Director of Technology of several 3D game companies. She is the first female founding member of Microsoft's Direct 3D Advisory Board and Graphics Advisory Board. Besides gaming, she had programmed on the Space Shuttle Project at Rockwell International California. She had designed and conducted accelerator experiments at LINAC in California and the accelerator at Brookhaven National Laboratory. Her nuclear physics research had won her a national award from the U.S. Department of Energy. She volunteered time in the past to advise on CUDA, visual computer and GPU simulation at NVidia. She remains active on the GAB and continues to volunteer time to review the designs of new Direct 3Ds. Check out this interview with Corrinne Yu, Halo Team Principal Programmer.
The Mythical 5%
-
Let's say that this follows the 80-20 rule. Roughly 80% of programmers don't read books, don't go to conferences, don't continue learning, don't do anything but what they covered in college. Maybe they've gotten a job in a big company where they can do the same thing over and over. The other 20% struggle with their profession: they read, try to learn things, listen to podcasts, go to user group meetings and sometimes a conference. 80% of this 20% are not very successful yet; they're still beginning, still trying. The other 20% of this 20% -- that's about 5% of the whole who are 20x more productive.
-
These people are not those who can remember all the moves and have fingers that fly over the keyboard erupting system commands. In my experience those in the 5% must struggle to get there, and struggle to stay there, and it's the process of continuous learning that makes the difference.
- 5 more annotations...
Reading Comprehension Will Make You A Better Programmer : So Jake Says:
-
Writing is also hard, and you’ll find plenty of instances where the authors
come up short. The burden is on you to prove beyond a shadow of a doubt that
you’re right and the author is wrong. If you’re not bending over backwards to
try to say “well, maybe the author was using it in the context of..”, you’re not
giving them much credit, and might not be putting enough thought into the
process. When you find yourself saying “this code is awful!”, try thinking of
how you would do it yourself. Sometimes you find that you come up with a better
way than the author. Sometimes you’re led right back to the same solution as the
author. -
This is where a programmer’s critical thinking skills will shine.
Granted, it’s difficult to determine the ramifications of question such as,
“What would the impact of using this non-standard syntax be if I made 300,000
library users adopt it?”. However, thinking on such a big scale can only help
you as a programmer, and the bigger you think, the more you help yourself. - 1 more annotations...
How to Write an Effective Design Document » “Hello World” - The SlickEdit Developer Blog
-
The process of designing before coding is becoming outdated. Documenting designs is becoming even rarer. Many developers have never written a design document and cringe at the idea of doing so. Many who are required to, typically generate a lot of interaction diagrams and class diagrams, which don’t often express the developer’s thought process during the design phase. This article will discuss how to do write an effective design document concisely with no special tools, and without needing to know UML. It will also discuss why a well written design document is one of the most valuable tools a developer can have when entering a new project.
Hacknot - Developers are from Mars, Programmers are from Venus
-
The term "programmer" has historically referred to a menial, manual input task conducted by an unskilled worker. Predecessors of the computer, such as the Hollerith machine, would be fed encoded instructions by operators called "programmers". Early electro-mechanical, valve and relay-based computers were huge and expensive machines, operated within an institutional environment whose hierarchical division of labor involved, at the lowest level, a "button pusher" whose task was to laboriously program the device according to instructions developed by those higher up the technical ladder. So the programmer role is traditionally concerned only with the input of data in machine-compatible form, and not with the relevance or adequacy of those instructions when executed.
-
Developers like to code as well, but they see it as being only a part of their job function. They focus more on delivering value than delivering program text, and know that they can't create value without having an awareness of the business context into which they will deploy their application, and the organizational factors that impact upon its success once delivered.
- 2 more annotations...
Selected Tags
Related Tags
Top Contributors
Groups interested in programmer
-
Unserstanding developers
The myths and truths about ...
Items: 23 | Visits: 1702
Created by: Joel Liu
Diigo is about better ways to research, share and collaborate on information. Learn more »
Join Diigo