home.social

Search

69 results for “fazzaro”

  1. "What I didn't expect was how difficult it would be. I relate it somewhat to the feeling I have with working out. Often times I want to avoid it because it's hard, but I'm always happy when I push through and complete it."

    #focus #emptiness #meditation

    alexselimov.com/posts/men_who_

  2. "I didn't get _why_, but I understood what it meant about that galaxy: the underclass deeply resented droids."

    #ai #classconsciousness #starwars

    daringfireball.net/2026/04/we_

  3. "When you make "passivity" the thing you're optimizing for, you stop caring about anything a customer might actually want. Caring is active. Caring takes time. Caring is work. Giving a shit is, by definition, not passive."

    #passiveincome #entrepreneur #care #purpose

    joanwestenberg.com/the-passive

  4. "When you make "passivity" the thing you're optimizing for, you stop caring about anything a customer might actually want. Caring is active. Caring takes time. Caring is work. Giving a shit is, by definition, not passive."

    #passiveincome #entrepreneur #care #purpose

    joanwestenberg.com/the-passive

  5. "When you make "passivity" the thing you're optimizing for, you stop caring about anything a customer might actually want. Caring is active. Caring takes time. Caring is work. Giving a shit is, by definition, not passive."

    joanwestenberg.com/the-passive

  6. "When you make "passivity" the thing you're optimizing for, you stop caring about anything a customer might actually want. Caring is active. Caring takes time. Caring is work. Giving a shit is, by definition, not passive."

    #passiveincome #entrepreneur #care #purpose

    joanwestenberg.com/the-passive

  7. "When you make "passivity" the thing you're optimizing for, you stop caring about anything a customer might actually want. Caring is active. Caring takes time. Caring is work. Giving a shit is, by definition, not passive."

    #passiveincome #entrepreneur #care #purpose

    joanwestenberg.com/the-passive

  8. "People tend to reject what they imagine programming together would be like, but what they imagine is not the way group programming works."

    #pairprogramming #mobprogramming #classic

    industriallogic.com/blog/progr

  9. "If you're all working on your own branches, you are not collaborating. You are competing. To see who can get their code in fastest. To avoid being stomped on by someone else's code changes."

    #continuousintegration #continuousdelivery #cicd #tbd #scattergather #classic

    trishagee.com/2023/05/29/why-i

  10. "Give yourself time to think about what you're actually building and why. Give yourself an opportunity to say, fuck no, we don't need this. Set yourself limits on how much code you let the clanker generate per day, in line with your ability to actually review the code."

    #ai #softwareengineering #bottleneck #codereview

    mariozechner.at/posts/2026-03-

  11. "If you like something your friend is doing, promote it online. It doesn't matter if you have a big following. It's a gesture, it takes 0.5 seconds, and it matters more than you probably realize."

    #new #etiquette #share #classic

    thecut.com/article/tipping-rul

  12. "This is the real driver of the layoffs, the big players consolidating the rent seeking to them. They just say it's AI cause that makes the stock price go up."

    #ai #replacement #capitalism

    geohot.github.io//blog/jekyll/

  13. "Speed is dangerous without brakes. Make risk a blocking function. If the risk is unknown or unmitigated, the line stops. Do not hide danger in a report; encode it as a gate."

    #softwareengineering #developerexperience #safety #speed #andon

    o16g.com/

  14. "Each answer leads to more questions. The accumulated decisions, edge cases, and interactions create genuine complexity that no tool or language can eliminate. Someone must think through these scenarios. That thinking is software development, regardless of whether it's expressed in COBOL, a CASE tool diagram, Visual Basic, or an AI prompt."

    #ai #knowledgework #softwareengineering #replacement

    caimito.net/en/blog/2025/12/07

  15. "Each answer leads to more questions. The accumulated decisions, edge cases, and interactions create genuine complexity that no tool or language can eliminate. Someone must think through these scenarios. That thinking is software development, regardless of whether it's expressed in COBOL, a CASE tool diagram, Visual Basic, or an AI prompt."

    #ai #knowledgework #softwareengineering #replacement

    caimito.net/en/blog/2025/12/07

  16. "Each answer leads to more questions. The accumulated decisions, edge cases, and interactions create genuine complexity that no tool or language can eliminate. Someone must think through these scenarios. That thinking is software development, regardless of whether it's expressed in COBOL, a CASE tool diagram, Visual Basic, or an AI prompt."

    caimito.net/en/blog/2025/12/07

  17. "Each answer leads to more questions. The accumulated decisions, edge cases, and interactions create genuine complexity that no tool or language can eliminate. Someone must think through these scenarios. That thinking is software development, regardless of whether it's expressed in COBOL, a CASE tool diagram, Visual Basic, or an AI prompt."

    #ai #knowledgework #softwareengineering #replacement

    caimito.net/en/blog/2025/12/07

  18. "Each answer leads to more questions. The accumulated decisions, edge cases, and interactions create genuine complexity that no tool or language can eliminate. Someone must think through these scenarios. That thinking is software development, regardless of whether it's expressed in COBOL, a CASE tool diagram, Visual Basic, or an AI prompt."

    #ai #knowledgework #softwareengineering #replacement

    caimito.net/en/blog/2025/12/07

  19. "Even if I wanted to reject AI and go back to the days where the Thinker's needs were met by coding, the Builder in me would struggle with the inefficiency."

    #ai #knowledgework #dukka

    jernesto.com/articles/thinking

  20. "Even if I wanted to reject AI and go back to the days where the Thinker's needs were met by coding, the Builder in me would struggle with the inefficiency."

    #ai #knowledgework #dukka

    jernesto.com/articles/thinking

  21. "Even if I wanted to reject AI and go back to the days where the Thinker's needs were met by coding, the Builder in me would struggle with the inefficiency."

    jernesto.com/articles/thinking

  22. "Even if I wanted to reject AI and go back to the days where the Thinker's needs were met by coding, the Builder in me would struggle with the inefficiency."

    #ai #knowledgework #dukka

    jernesto.com/articles/thinking

  23. "Even if I wanted to reject AI and go back to the days where the Thinker's needs were met by coding, the Builder in me would struggle with the inefficiency."

    #ai #knowledgework #dukka

    jernesto.com/articles/thinking

  24. "I don't 'break down the work to determine how long it will take'. My management chain already knows how long they want it to take. My job is to figure out the set of software approaches that match that estimate. Sometimes that set is empty."

    #softwareengineering #scope #planning

    seangoedecke.com/how-i-estimat

  25. "Over the past few years, I've become more frustrated with the terms 'Unit' and 'Integration' because I have to explain what 'Unit' and 'Integration' mean before I can use them."

    #automatedtesting #unit #vs #integration #naming #classic

    ted.dev/articles/2023/04/02/i-

  26. "There is abundant evidence that over the last 20 years, American firms have shifted from an innovation mindset to one that focuses more on rent seeking."

    #innovation #vs #rentseeking #classic

    greg-satell.medium.com/4-signs

  27. "We have a process to help us build in quality that is based on feedback and inviting human judgement, but if the system incentives constrain our ability to get the feedback, that also means we are less likely to build in quality."

    #softwareengineering #pullrequests #vs #mobprogramming #classic

    infoq.com/articles/co-creation