featured in #342
Knuth And McIlroy Approach A Problem
- Matt Rickard tl;dr: "A computer scientist was writing a column about Literate Programming – one of Knuth's ideas on how documentation and code should live side-by-side. So he asked both Knuth and McIlroy to write a program: "Given a text file and integer k, print the k most common words in the file - and the number of their occurrences - in decreasing frequency."featured in #342
How Do I Progress To The Next Level In My Career?
- James Stanier tl;dr: "Progressing, in general, is a two-stage problem: you need to discover where it is that you’d like to go, and then you need to take positive action to work towards it. In my experience, many people over index on the prescriptive “how” before spending enough time on the “what”. The search space of possibilities for your career trajectory is effectively unbounded, and can rarely be predicted over long enough periods of time. This is a feature, not a bug, and should be embraced."featured in #341
The Secret To Getting To The Staff+ Level? Leverage
- Camille Fournier tl;dr: "You need to develop skills that give you the leverage to show bigger value to the company. These could be interpersonal skills that make you more trusted and valued, execution skills that let you drive complex projects to success, strategic skills that give you bigger ideas and the ability to sell them, or, occasionally, expert skills that make you very hard to replace."featured in #341
featured in #341
featured in #341
“Black Hole Words” And The Power Of Asking Stupid Questions
- Molly Graham tl;dr: Molly warns us of black hole words, which "are commonplace in a given industry but everyone has a slightly different definition of them. You can have a whole meeting and if you don’t define the word, you just wasted an hour of everyone’s time." Molly gives us examples, such as "values", "work-life balance", "impact" and "fast."featured in #340
featured in #340
Thinking About The Costs Of A Software Feature
- Roland Weigelt tl;dr: (1) The work necessary for turning a rough sketch of an idea into a viable concept. (2) Time spent on planning the work. (3) Effort that goes into preparing the coding part of the development. (4) Time spent on writing the code. (5) Testing the software. (6) Documentation. And more.featured in #339
featured in #338