dogear

enter for all results · esc to close

Productivity

Productivity and work: focus, habits, note-taking, time management, writing things down, and tools for getting things done.

  1. Psychology Today: How Programmers Can Avoid Burnout psychologytoday.com

    “Veteran software developers often recommend to: 1. Work at a place where you can grow; 2. Build transferable skills; 3. Have creative outlets and create a space to focus on yourself, switch off, and relax; 4. Of course, there's always the nuclear option: make your money and…

  2. Organizational Skills Beat Algorithmic Wizardry prog21.dadgum.com

    “When it comes to writing code, the number one most important skill is how to keep a tangle of features from collapsing under the weight of its own complexity.”

  3. The Baldwin Formula for scientific writing: writing papers and reviews people.clas.ufl.edu

    “The most efficient way to write scientific papers is to write while you are still conducting experiments”.

  4. 7 Rules of Power openlibrary.org

    By Jeffery Pfeffer. Tells you how to play office politics if success in the workplace is the only thing you care about.

  5. First, Break All the Rules: What the World's Greatest Managers Do Differently openlibrary.org

    We learn in this book that employee happiness was not correlated to company success. A comment on HN details the questions that were highly correlated to company success.

  6. Some tips on public speaking news.ycombinator.com

    “If you ever find yourself buffering on output, rather than making hesitation noises, just pause. People will read that as considered deliberation and intelligence.”

  7. source news.ycombinator.com

    ) - A recipe on how to work with your direct reports, from a section of 7 habits of highly effective people.

  8. “Company I've worked for had manager who tried to ship features over the weekend with a ragtag team of developers who… news.ycombinator.com

    Tactics of hustling managers, and how the company reacting to that kind of manager makes or break a good place to work.

  9. source news.ycombinator.com

    ), or why the key practices for achieving large professional goals is missing the parts about office politics.

  10. Colleague is leaving. How to investigate what went wrong? news.ycombinator.com

    “Most of the time people leave bosses, not the job or the company.” And why you're unlikely to get any substantial insights from exit interviews. (source)

  11. I try to optimize my code around reducing state, coupling, complexity and code, in that order news.ycombinator.com

    An engineer's perspective on which priorities should be addressed first to increase robustness of systems.

  12. Notes on Technical Writing mkaz.blog

    An effective list of do and don't when it comes to writing documentation.

  13. Book Summary of "Who: The A Method for Hiring" medium.com

    The essential of Who, a popular book on recruiting executives.

  14. You're Not Managing a Team of Software Engineers, You're Managing a Team of Writers medium.com

    Because writing software is “a creative process which is by its nature unpredictable and personal, in an environment which craves certainty, predictability and consistency.”

  15. I coached CEOs, founders, VCs and other executive: These are the biggest takeaways leowid.com

    Excerpt: “We're all just big, complicated bags of emotion walking around; Power comes with the ability to receive a No; Learning to manage your focus, not your time.”

  16. Work at different management levels larahogan.me

    A great progressive breakup of what it feels like to work at different levels of management.

  17. Manager Energy Drain larahogan.me

    “How do I handle how tired I am as a manager? 1. Defrag your calendar; 2. Delegate messy and unscoped projects; 3. Say no.”

  18. Questions for our first 1:1 larahogan.me

    A personal list of high-level questions from a manager.

  19. The Good, the Bad and the Ugly Standup kristoff.it

    Author experienced 3 formats of stand-ups before ending with one working for his team, and concludes that “the details that make up a good meeting are subtle and the pursuit of an artificial standard of aesthetics will prevent you from doing the necessary experimentation to…

  20. Managing Remote Teams - A Crash Course klinger.io

    Compilation of easy rules and processes to bootstrap a remote team.

  21. Get your work recognized: write a brag document jvns.ca

    There's this idea that, if you do great work at your job, people will (or should!) automatically recognize that work and reward you for it with promotions / increased pay. In practice, it's often more complicated than that.

  22. Noise, Cognitive Function, and Worker Productivity joshuatdean.com

    “An increase of 10 dB reduces productivity by approximately 5%.”

  23. Why it's difficult to build teams in high growth organisations jchyip.medium.com

    Describes 3 different approach a manager can take to accommodate new people in the team: 1. Sink or Swim; 2. Split and Absorb; 3. Absorb and Split.

  24. Programmer Moneyball: Challenging the Myth of Individual Programmer Productivity insights.sei.cmu.edu

    “Since software project managers have limited ability to evaluate individual developer capability, they should rely on a productive environment and developing talent.”

  25. A guide to distributed teams increment.com

    A nice wrap up on the numerous dispositions required to have a highly effective distributed team.

  26. Power Bends Light honkathon.com

    “Most things at most startups are perpetually on fire, but if you can accept that, there is a lot to like. One well-known one: at a fast-growing startup, a hard-working, talented person who has some support from company leadership can often acquire an impressive title (or at…

  27. The Psychology of Design growth.design

    An extensive list of cognitive biases and design principles with examples and tips to fine-tune your product and UX.

  28. How to exit vim, the Product Manager way github.com

    A satire with a grain of truth, especially the comparison between the basic vs experienced level.

  29. How to be a Manager – A step-by-step guide to leading a team getweeklyupdate.com

    A full, detailed guide on modern management practices.

  30. Yes, and… en.wikipedia.org

    “A rule-of-thumb in improvisational comedy (…). It is also used in business and other organizations as a principle that improves the effectiveness of the brainstorming process, fosters effective communication, and encourages the free sharing of ideas.”

  31. Building and Motivating Engineering Teams elidedbranches.com

    What DO engineers want? Money, purpose and respect.

  32. What nobody tells you about documentation divio.com

    There is four kinds of documentation: tutorials, how-to guides, explanation and reference. Each with their own structure and mode of writing.

  33. Technical Writing Courses developers.google.com

    This collection of courses and learning resources aims to improve your technical documentation. Learn how to plan and author technical documents. You can also learn about the role of technical writers in a company.

  34. 3 tricks to start working despite not feeling like it deprocrastination.co

    “'Screw it, let's do it'; Start sloppy; Start small”.

  35. Mistakes I've Made as an Engineering Manager css-tricks.com

    Mistakes: “1) Thinking people give feedback the way they want to receive it; 2) Trying to do everything yourself; 3) Communicating something one time is enough; 4) You have to have everything together all the time.”

  36. Learning Technical Writing Using the Engineering Method cs.tufts.edu

    An alternative approach, involving a weekly meeting of a writing group. An interesting dynamic to gather feedback and experience.

  37. Tips for Writing Technical Papers cs.stanford.edu

    Another set of tips, specifically using the example of a technical paper describing an improvement of an algorithm.

  38. Surprising Things About Working at Well-Known Tech Unicorns blog.pragmaticengineer.com

    Echoes my own experience on differences between expectations and reality in high growth and visible companies from the point of view of an engineering manager.

  39. Teams are like bread blog.jessitron.com

    Resonates with the Absorb and Split strategy discussed above: “if you have one team where the magic is flourishing, don't kill it. Feed it, grow it, and let it be a source of further strong teams. No rushing.”

  40. Ten simple rules for structuring papers biorxiv.org

    “Focusing on how readers consume information, we present a set of 10 simple rules to help you get across the main idea of your paper.”

  41. The Art of Powerful Questions - Catalyzing Insight, Innovation, and Action betterevaluation.org

    “Leaders believe that they are being paid for fixing problems rather than for fostering breakthrough thinking.”

  42. Strategies for long Projects benbrostoff.github.io

    Relentless, irrational optimism; Daily progress documentation; Compounding investments; Time budgeting.

  43. Why procrastination is about managing emotions, not time bbc.com

    “Research shows that once the first step is made towards a task, following through becomes easier”.

  44. What Happens When Your Career Becomes Your Whole Identity archive.ph

    “A particular confluence of high achievement, intense competitiveness, and culture of overwork has caught many in a perfect storm of career enmeshment and burnout.”

  45. Things Many People Find Too Obvious To Have Told You Already archive.ph

    A set of heuristics on tech companies and the ecosystem they live in.

  46. How CEOs Manage Time archive.ph

    A study on what CEO of large companies spent their time on, and how. Opens a new window into what leadership is all about and into its many components and dimensions.

  47. If Your Boss Could Do Your Job, You're More Likely to Be Happy at Work archive.ph

    “Although we found that many factors can matter for happiness at work – type of occupation, level of education, tenure, and industry are also significant, for instance – they don't even come close to mattering as much as the boss' technical competence.”

  48. Who are you trying to impress with your deadlines? archive.ph

    “There are companies where those deadlines are set in stone, and a missed deadline is next to fire. That's when the problem starts.”

  49. If You're So Successful, Why Are You Still Working 70 Hours a Week? archive.ph

    “Our tendency to overwork and burn out is framed by a complex combination of factors involving our profession, our organization, and ourselves. At the heart of it is insecurity.”

  50. next page of items loading…