Shaare your links...
3022 links
Httqm's Links Home Login RSS Feed ATOM Feed Tag cloud Picture wall Daily
Links per page: 20 50 100
◄Older
page 1 / 7
129 results for tags Best_Practice x
  • Human Task Switches Considered Harmful – Joel on Software
    Conclusion : never let people work on more than one thing at once.
    Mon Jan 11 15:03:13 2021 - permalink -
    - https://www.joelonsoftware.com/2001/02/12/human-task-switches-considered-harmful/
    Best_Practice Development Job
  • The Andon Cord
    The key, as Rother suggests, is that it wasn’t the tools that made Toyota great, it was the culture and specific behavior associated behind those tools.

    ==> As said by other smart persons :
    - Don't fix bugs, fix your process.
    - Don't work harder, work smarter.
    Tue Oct 20 12:35:15 2020 - permalink -
    - https://itrevolution.com/kata/
    Best_Practice Japan Job Wisdom
  • Production Oriented Development
    'BUY' ALMOST ALWAYS BEATS 'BUILD' : If you can avoid building something, you should. Code is the most expensive way to solve a problem that isn’t addressing a core area of your business.

    MAKE DEPLOYS EASY : Deploying should be a frequent and unexciting activity. Engineers should be able to deploy with minimal manual steps and it should be easy to see if the deploy is successful. (...) It’s not a coincidence that two of the four key metrics that the book focuses on are directly related to this (Deploy Frequency, Change Lead Time). Shipping is your company’s heartbeat.

    TRUST THE PEOPLE CLOSEST TO THE KNIVES : The people who work with a system are the ones who understand it best. (...) They should, therefore, be the primary stakeholders responsible for prioritizing technical work.

    BORING TECHNOLOGY IS GREAT : (...) you want a wide area of expertise for routine operations and when shit goes sideways (...). Very few organizations have the bandwidth to debug unique problems. (...) Using boring technology means you can lean on a large community of users. Shit on it all you want, but there are very few PHP issues that someone else hasn’t already encountered.
    Tue Mar 3 10:39:21 2020 - permalink -
    - https://paulosman.me/2019/12/30/production-oriented-development.html
    Best_Practice Development DevOps Job
  • The Let It Crash Philosophy Outside Erlang
    The "Let it crash" principle reminds me of the Unix's "Rule of Repair" (https://homepage.cs.uri.edu/~thenry/resources/unix_art/ch01s06.html) : "When you must fail, fail noisily and as soon as possible."
    Thu Jan 30 15:55:26 2020 - permalink -
    - http://stratus3d.com/blog/2020/01/20/applying-the-let-it-crash-philosophy-outside-erlang/
    Best_Practice Development Unix
  • 3 tricks to start working despite not feeling like it
    When we don't "feel like it", we're often procrastinating because we're afraid of performing poorly.
    Remove this pressure and "just do it" : poor quality work will get you started and in good condition to make something good.
    Wed Jan 22 11:10:07 2020 - permalink -
    - https://www.deprocrastination.co/blog/3-tricks-to-start-working-despite-not-feeling-like-it
    Best_Practice Motivation Wisdom
  • Comment être sûr de rater ton projet informatique
    Plein de bons conseils, malheureusement souvent mis en pratique :-/

    L'ensemble de l'article est aussi vrai que drôle.
    Mention spéciale à cette phrase qui a un petit goût de "j'ai-déjà-vu-ça-quelque-part" :

    Dans le désordre tu peux obliger tout le monde à travailler minimum 60 H par semaine. Quand les gens n’auront plus de vie personnelle, c’est avec plaisir non dissimulé qu’ils vont chier à l’intérieur de ton projet.
    Fri Jan 17 16:37:34 2020 - permalink -
    - https://www.jesuisundev.com/comment-etre-sur-de-rater-ton-projet-informatique/
    Best_Practice Job Manager
  • Reconnaître et mettre fin à ton burnout – 24 jours de web
    Par Mehdi Zed, l'auteur de https://www.jesuisundev.com/ego-des-developpeurs/
    Fri Jan 17 16:27:23 2020 - permalink -
    - https://www.24joursdeweb.fr/2019/reconnaitre-et-mettre-fin-a-ton-burnout/
    Best_Practice Job Psychology Santé Wisdom
  • The Efficiency-Destroying Magic of Tidying Up
    "Cleaner" does not mean "more efficient" : have a look at the urban planner's dream pizza to get the idea (well, read the article too ;-)

    Scott’s Law: never put order in a system before you understand the structure underneath its (apparent) chaos.
    Mon Nov 18 13:49:16 2019 - permalink -
    - https://florentcrivello.com/index.php/2019/09/04/the-efficiency-destroying-magic-of-tidying-up/
    Best_Practice Chaos Job Organization Process
  • Asynchronous Communication: The Real Reason Remote Workers Are More Productive
    Wed Oct 16 12:39:20 2019 - permalink -
    - https://doist.com/blog/asynchronous-communication/
    Best_Practice Job
  • Desirable developer skills
    1. Ability to ignore new tools and technologies
    2. Taste for simplicity
    3. Good code deletion skills
    4. Humility
    Thu Sep 19 08:41:15 2019 - permalink -
    - https://twitter.com/codeinthehole/status/540117725604216832
    Best_Practice Development Job Wisdom
  • How To Become A Hacker
    A FAQ with lots of interesting + useful information (and links !)
    Worth reading ;-)
    Mon Sep 2 08:22:10 2019 - permalink -
    - http://www.catb.org/~esr/faqs/hacker-howto.html#believe1
    Best_Practice Blog Geek_Culture Hack Internet Nerd Wisdom
  • Pourquoi la sécurité numérique ne peut pas être la même pour tous les journalistes
    Ne pas changer les méthodes de travail pour favoriser l’adoption

    Transformer son smartphone en coffre-fort peut être contre productif
    ==> les coups et la torture viennent toujours à bout des mots de passe
    Wed Aug 28 09:49:23 2019 - permalink -
    - https://gijn.org/2019/07/16/pourquoi-la-securite-numerique-ne-peut-etre-la-meme-pour-tous-les-journalistes/
    Best_Practice Journalists Security
  • Composing better emails
    Good advice (and common sense) about writing efficient + useful emails.

    IMHO, the best email (like the best comment in programming) is the one you need not writing. Instead use other dedicated tools : question code in GitLab (or equivalent), ask for clarification in issue trackers, and don't use emails for instant messaging. Also avoid "Ok, thx" in "Reply to all" ;-)

    NB : I'm not a big fan of emails anyway. Most of the time, information is missing, people are forgotten in the recipients list, and any communication that could be done easily gets complicated by the misuse of email.
    Thu Aug 1 07:30:58 2019 - permalink -
    - https://iridakos.com/how-to/2019/06/26/composing-better-emails.html
    Best_Practice Email Job
  • In the Defense of Spaghetti Code
    Pretty interesting article about "spaghetti code" and (specific!) situations where you've left with no choice but spaghetti code.

    Seen in the comments :

    "(...) essential and accidental complexity. Once you have got rid of the accidental complexity, you are left with the essential complexity, which cannot be further reduced without compromising on functionality.
    You can shovel the essential complexity around your system design all you like, but the overall quantity of complexity still remains constant."
    Mon Jul 22 12:30:57 2019 - permalink -
    - http://250bpm.com/blog:36
    Best_Practice Blog Coder_Proprement Development
  • A personal story about 10× development
    In fact, the overall health of the code base probably has a bigger effect on developer productivity than all developers' skills combined.

    But even more important than technical issues are things that promote healthy team dynamics. These include things like blameless postmortems, openness to ideas from everyone, permission to try new things even if they may fail, stern weeding out of jerk behaviour and, ultimately, trust.
    Fri Jul 19 14:50:13 2019 - permalink -
    - http://nibblestew.blogspot.com/2019/07/a-personal-story-about-10-development.html
    Best_Practice Blog Development Job
  • Assholes: A Probing Examination
    Assholes are a disease that spreads through your organization, slowly killing it from the inside. Yet, employing assholes is one of the most common mistakes I see tech companies make, because they are so laser-focused on hiring people with technical skills that those skills become the sole determiner of an engineer’s value.

    So how do you know if someone is an asshole? Here’s a simple test: if someone walks away from another person feeling bad about themselves, they were probably interacting with an asshole. Assholes undermine your confidence, they talk down to you, they try to make themselves look good at your expense, and they generally make you regret having to talk to them.

    When you learn something from a non-asshole you walk away thankful for the mentorship.

    assholery can have cascading effects where eventually everyone is being an asshole to each other.

    Asshole behavior at work can cost companies millions of dollars a year in lost productivity, drained morale, employee loyalty, and worker commitment.

    asshole behavior packs 5 times the impact as non-asshole behavior, so reaching only a 20% asshole population results in an oppressive, miserable work environment that cannot be fixed, only escaped.

    Job requirements rarely specify social skills as an essential task, so HR often won’t get on board with letting someone go for being an asshole unless they commit some outrageous act of harassment. Formalizing social skills as part of the job description can help with this.

    They (assholes) become the “experts” in particular areas of code (...). This results in a situation where assholes are deemed too important to lose, and the thought of just losing all of the assholes in the organization feels like losing your “best” people and a surefire way to destroy your company. Be assured that if you feel like you can’t “afford” to lose all of your assholes, your organization has been overrun by assholes.

    Creating an asshole-free work environment is actually very straightforward, all it takes is a commitment to following a few steps. (...) you need to decide, as an organization, you’re not going to tolerate assholes. (...) Simply being explicit is often enough.

    There is no question you can think of to determine if someone is an asshole that would not be trivially easy for a self-aware asshole to lie through. Don’t even bother trying.


    So also some interesting comments :
    - https://news.ycombinator.com/item?id=20359378#20360747 : "People with Asperger's or otherwise on the autism spectrum can be huge "assholes" by the definitions here. Does autism make you unemployable?"
    - https://news.ycombinator.com/item?id=20359378#20360341 : At least 10 thousand years of civilization, and we are still trying to figure out each other and ourselves. Why is "Don't be a dick" so hard to codify?
    Fri Jul 5 09:20:57 2019 - permalink -
    - https://www.nomachetejuggling.com/2019/06/03/dont-hire-assholes/
    Best_Practice Job Manager People Société
  • Inversion: The Power of Avoiding Stupidity
    TL;DR :

    Avoiding stupidity is easier than seeking brilliance.
    Mon Jun 3 09:27:52 2019 - permalink -
    - https://fs.blog/2013/10/inversion/
    Best_Practice Job Wisdom
  • Le « modèle de Reason »
    « Si un accident se produit, l’important n’est pas de savoir qui a fait une faute, mais d’identifier pourquoi et comment le système de sécurité a failli ».

    ==> aka l'effet "alignement des trous du gruyère"
    Thu May 23 09:27:05 2019 - permalink -
    - https://enperspective.pagesperso-orange.fr/james_reason.html
    Best_Practice Job Reliability
  • How I Almost Destroyed a £50 million War Plane and The Normalisation of Deviance
    "(...) the normalisation of deviance often results in an erosion of competency in which a culture of safety is slowly and gradually worn away."

    "It is well known that jet pilots start with a bag of luck and start to fill a bag of experience (...) The trick is to fill the bag of experience before you empty the bag of luck."


    ==> "Normalisation of deviance" is what, in IT, we call "normal errors". They lead to BIG crashes too ;-)
    Mon Apr 29 14:48:10 2019 - permalink -
    - https://fastjetperformance.com/podcasts/how-i-almost-destroyed-a-50-million-war-plane-when-display-flying-goes-wrong-and-the-normalisation-of-deviance/
    Armée Best_Practice Blog Job Plane Wisdom
  • The Ten Commandments of Egoless Programming
    1. Understand and accept that you will make mistakes.
    2. You are not your code.
    3. No matter how much "karate" you know, someone else will always know more.
    4. Don't rewrite code without consultation.
    5. Treat people who know less than you with respect, deference, and patience.
    6. The only constant in the world is change.
    7. The only true authority stems from knowledge, not from position.
    8. Fight for what you believe, but gracefully accept defeat.
    9. Don't be "the guy in the room."
    10. Critique code instead of people – be kind to the coder, not to the code.
    Tue Apr 2 07:00:00 2019 - permalink -
    - https://blog.codinghorror.com/the-ten-commandments-of-egoless-programming/
    Best_Practice Development Job Wisdom
Links per page: 20 50 100
◄Older
page 1 / 7
Shaarli 0.0.41 beta - The personal, minimalist, super-fast, no-database delicious clone. By sebsauvage.net. Theme by idleman.fr.