Alan Christensen

@christensena

Kiwi software developer (mainly .NET), climber, tramper

Christchurch, New Zealand
Vrijeme pridruživanja: kolovoz 2008.

Tweetovi

Blokirali ste korisnika/cu @christensena

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @christensena

  1. proslijedio/la je Tweet
    27. sij

    If your org doesn't have deliberate software architecture, then all your software engineers are building arbitrary undesigned structures, and your CTO is the mayor of a software shanty town.

    Poništi
  2. proslijedio/la je Tweet
    14. pro 2019.

    The story of Nigel Richards, the man from New Zealand who memorized every French word in the French scrabble dictionary and won the French Scrabble Championship without speaking any French

    Poništi
  3. proslijedio/la je Tweet
    Poništi
  4. proslijedio/la je Tweet
    18. ruj 2019.

    Gorgeous. (You'll need to click on photo to read in full).

    Poništi
  5. proslijedio/la je Tweet
    3. kol 2019.

    The fact that DuckDuckGo and its 67 employees produce a search experience that is almost imperceptibly different than Google's is one of the most impressive achievements in tech right now.

    Poništi
  6. proslijedio/la je Tweet
    22. srp 2019.

    “Feature branches” vs trunk-based development is a straw man. Branch lifetime is a primary indicator of integration difficulty. Keep stories small, branches are short. Attack the disease, not the symptom

    Prikaži ovu nit
    Poništi
  7. proslijedio/la je Tweet

    One of the things to emerge over last few years is npm and Node.js ecosystem - billion dollar companies and startups alike are building complex systems on top of often unmaintained code written by random people for no pay.

    Prikaži ovu nit
    Poništi
  8. proslijedio/la je Tweet
    30. svi 2019.

    never saw this before from via

    Poništi
  9. proslijedio/la je Tweet
    27. svi 2019.

    TDD for visual components is often detrimental. Unless you have a fixed static design (and even those almost never stay fixed), you usually have to implement and style a UI component before you can tell if it’s the right approach.

    Prikaži ovu nit
    Poništi
  10. proslijedio/la je Tweet

    I came across these three graphs in , XP Explained. They show the level of software design needed in a system. And they so remind me of . In a Simple and Obvious system, just do it. In a Complicated one, think about it. And in Complexity, rely on experience.

    Prikaži ovu nit
    Poništi
  11. proslijedio/la je Tweet
    30. tra 2019.

    When we rush development, skip tests and refactoring, we get “Escalating Risk.” Please give up the “technical debt” description; it gives businesspeople a very wrong impression of the tradeoffs. From

    Poništi
  12. proslijedio/la je Tweet
    11. tra 2019.

    We have lots of ways to catch issues: 1. Compiler error 2. Unit test 3. Integration test 4. PR comment 5. Manual QA 6. User feedback When you find a problem, ask how you can move it up 1 or more levels. e.g. “How can I turn this PR comment into a compiler error or unit test?”

    Poništi
  13. proslijedio/la je Tweet

    Of all the technical debt you can incur, the worst in my experience is bad names -- for database columns, variables, functions, etc. Fix those IMMEDIATELY before they metastasize all over your codebase and become extremely painful to fix later.. and they always do.

    Poništi
  14. proslijedio/la je Tweet
    26. ožu 2019.

    25yrs ago: COM (focus on your biz logic) 20yrs ago: Java (focus on your biz logic) 15yrs ago: .NET (focus on your biz logic) 10yrs ago: Dynamic langs (focus on your biz logic) 5yrs ago: Microservices (focus on your biz logic) 0yrs ago: Serverless (focus on your biz logic)

    Prikaži ovu nit
    Poništi
  15. proslijedio/la je Tweet
    18. ožu 2019.

    “If you go to the library and get out a book on WWII, afterwards the librarian doesn’t say ‘you might also enjoy this copy of Mein Kampf’. But YouTube does.” The Daily pod nailing it, on ChCh attacks and the online environment

    Poništi
  16. proslijedio/la je Tweet
    18. ožu 2019.

    Ardern: “We cannot sit back and accept these platforms just exist, that what is said on them is not the responsibility of the place they are published. They are the publisher not just the postman. They cannot have the profits without the responsibility.”

    Prikaži ovu nit
    Poništi
  17. proslijedio/la je Tweet
    27. velj 2019.
    Poništi
  18. proslijedio/la je Tweet
    17. sij 2019.
    Poništi
  19. proslijedio/la je Tweet
    8. sij 2019.

    What code is it OK to have bugs in? Pairing is proven to cut defects by 80% and is only 15% slower (2001 Williams study). Bugs equate to 85% of the cost of software 6 months or older. So how much money are you saving by not pairing again?

    Poništi
  20. proslijedio/la je Tweet
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·