dogear

enter for all results · esc to close

Programming

Software development: programming languages, coding, libraries and frameworks, software engineering and architecture, source control, developer tools, databases, and infrastructure.

  1. source news.ycombinator.com

    ).

  2. source news.ycombinator.com

    ).

  3. source news.ycombinator.com

    ).

  4. The different engineering levels at Google news.ycombinator.com

    From L3 to L8: a quick description of what makes an engineer at each level.

  5. source news.ycombinator.com

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

  6. source news.ycombinator.com

    ) - Another way of putting it: managers needs domain knowledge and to know the work their reports do.

  7. source news.ycombinator.com

    ).

  8. source news.ycombinator.com

    ).

  9. source news.ycombinator.com

    ).

  10. “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.

  11. source news.ycombinator.com

    ).

  12. source news.ycombinator.com

    )

  13. source news.ycombinator.com

    )

  14. source news.ycombinator.com

    ).

  15. source news.ycombinator.com

    ).

  16. source news.ycombinator.com

    ).

  17. Some reasons why enterprise software is good and maybe even fun news.ycombinator.com

    The majority of us will not build the next unicorn: we statically have a better chance to build enterprise software. The twist? It might even be more interesting than you expect.

  18. source news.ycombinator.com

    )

  19. source news.ycombinator.com

    ).

  20. source news.ycombinator.com

    )

  21. source news.ycombinator.com

    )

  22. source news.ycombinator.com

    ) - Some tips on how to balance which kind of information needs to be shared or muted.

  23. source news.ycombinator.com

    )

  24. source news.ycombinator.com

    ).

  25. source news.ycombinator.com

    ).

  26. Things to look for when hiring remote workers news.ycombinator.com

    “1. You have to adhere to employment laws within the country you're hiring from; 2. To employ someone full time, many countries require you to have a legally entity within that country; 3. Prioritize countries where we have the most interest; 4. Keep a healthy timezone overlap…

  27. Best project management practices in 2018? news.ycombinator.com

    There is no silver bullet.

  28. source news.ycombinator.com

    ) - Examples in which developers that might pass tough job interview just fine are bringing negative value later.

  29. What makes a Senior Dev news.ycombinator.com

    “Time, man. You gotta do your fucking time.”

  30. 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.

  31. Things I Learnt from a Senior Software Engineer neilkakkar.com

    “I sat next to a senior software engineer for a year. Here's what I learnt.”

  32. 7 absolute truths I unlearned as junior developer monicalent.com

    “1. I'm a senior developer; 2. Everyone writes tests; 3. We're so far behind everyone else (a.k.a. tech FOMO); 4. Code quality matters most; 5. Everything must be documented; 6. Technical debt is bad; 7. Seniority means being the best at programming”.

  33. Things I have learnt as the software engineering lead of a multinational minnenratta.wordpress.com

    Some interesting points here, some others needs to be challenged.

  34. 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.”

  35. All the best engineering advice I stole from non-technical people medium.com

    “It's intriguing that the stuff that really seems to make a difference in the quality of software never seems to be about software.”

  36. Developers spend most of their time figuring the system out lepiter.io

    “A hand drawn picture about the current system is a belief. Decisions should never be based on beliefs. Not in engineering. (…) As software is highly contextual we cannot predict specific problems. We can only predict classes of problems.” And that's why it is hard to estimate…

  37. Work at different management levels larahogan.me

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

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

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

  39. Rethinking the Hiring Process karllhughes.com

    “Testing programmers at something they aren't actually expected to be good at and expecting to learn something about how they would work at your company is delusional, and I think these kind of interviews only serve to make the hiring team feel smarter and ensure better…

  40. LEGO blocks and organ transplants johndcook.com

    “People have been comparing software components to LEGO blocks for a couple decades. (…) Integrating two software systems is usually more like performing a heart transplant than snapping together LEGO blocks.”

  41. Incentive Pay Considered Harmful joelonsoftware.com

    “Incentives (or bribes) simply can't work in the workplace. (…) Most software managers have no choice but to go along with performance review systems that are already in place. If you're in this position, the only way to prevent teamicide is to simply give everyone on your team…

  42. A high-resilience org chart jessitron.com

    “If you know what problem you're solving and you know how to solve it, a bureaucratic organization will do. Stick with what you know. If you're writing software, that's a generative activity. You need a high-resilience org chart. Fewer boxes, more flexibility.”

  43. 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.”

  44. Developers can't fix bad management iism.org

    “Why do so many software projects fail? Software development is much closer to creating a new factory than running an existing factory. (…) Software development is made up of many unknown duration tasks, this fundamentally unpredictable nature makes traditional management's…

  45. Google Engineering Practices google.github.io

    Explains how to perform code reviews and how to submit them.

  46. Paper we love: Software Engineering Organizations github.com

    “The practice of software engineering, and its history is, itself, a complex study in humanity, coordination, and communication.”

  47. Code reviews at Google github.com

    “Why Should Code Reviews Be Fast? (…) To optimize for the speed at which a team of developers can produce a product together, as opposed to optimizing for the speed at which an individual developer can write code.”

  48. The 4 Worst Software Metrics Agitating Developers in 2019 gitclear.com

    The worst KPIs to track a software team output: Lines of Code, Commit Count, Issues Resolved (aka “Shipping Velocity”) and Code Churn (aka "Efficiency").

  49. What Makes A Great Software Engineer? faculty.washington.edu

    Doesn't conclude on a definitive answer to the question, but details a model based on 53 attributes (!). Still a good source referencing other papers on the topic.

  50. next page of items loading…