korrents
Emanuele Bartolesi

Emanuele Bartolesi

@emanuele-bartolesi · 11 positions · On ppll ↗

Italian software architect working on Microsoft 365, Azure and GitHub tooling. Microsoft MVP and GitHub Star; writes, speaks and streams about developer productivity at emanuelebartolesi.com.

Emanuele Bartolesi did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

  1. management

    For me, a useful meeting resolves a question, exposes a dependency, or produces a decision.

    ↗Seasoned Developer Advice after 25 years in ITemanuelebartolesi.com 1st of 3 in this piece

  2. software quality

    Two methods that look similar may represent business rules that will evolve independently. Putting them in one common library creates a relationship you will have to maintain.

    ↗Seasoned Developer Advice after 25 years in ITemanuelebartolesi.com 2nd of 3 in this piece

  3. developer tools

    The age of a framework alone is a weak explanation for rewriting a working application.

    ↗Seasoned Developer Advice after 25 years in ITemanuelebartolesi.com 3rd of 3 in this piece

  4. 6 months earlier
  5. remote workdeveloper tools

    Remote Desktop is tolerable for admin work. For actual coding, it is a bad experience.

    ↗Stop Coding Through Remote Desktop. Use VS Code Remote Tunnels Insteademanuelebartolesi.com 1st of 2 in this piece

  6. developer tools

    SSH is often blocked, restricted, or simply not part of the approved setup.

    ↗Stop Coding Through Remote Desktop. Use VS Code Remote Tunnels Insteademanuelebartolesi.com 2nd of 2 in this piece

  7. 6 days earlier
  8. LLMsthe cloudprivacy

    You avoid sending prompts and contexts to external services. This is the strongest reason to use local models.

    ↗Using GitHub Copilot CLI with Local Models (LM Studio)emanuelebartolesi.com 1st of 2 in this piece

  9. the cloud

    Avoid this setup if you need: High accuracy Large context handling Production-grade reliability In those cases, cloud models are still the better option.

    ↗Using GitHub Copilot CLI with Local Models (LM Studio)emanuelebartolesi.com 2nd of 2 in this piece

  10. 8 days earlier
  11. LLMscoding agentssoftware qualityMicrosoft

    By default, Copilot tries to agree, avoid criticism, and keep answers "safe". That sounds good, but in practice it leads to weak suggestions, missed problems, and bad decisions slipping through.

    ↗GitHub Copilot Is Too Nice. Fix It With a Tone of Voice File.emanuelebartolesi.com 1st of 2 in this piece

  12. LLMsdesign

    But if you are building real systems, that is the wrong goal anyway.

    ↗GitHub Copilot Is Too Nice. Fix It With a Tone of Voice File.emanuelebartolesi.com 2nd of 2 in this piece

  13. 6 weeks earlier
  14. developer tools

    Conventional Commits are not about style. They are about structure.

    ↗GitHub Copilot to Generate Conventional Commit Messages in VSCode and JetBrains Rideremanuelebartolesi.com 1st of 2 in this piece

  15. coding agentsAI and jobsdeveloper toolsMicrosoft

    Copilot is not replacing judgment. It removes repetitive formatting work.

    ↗GitHub Copilot to Generate Conventional Commit Messages in VSCode and JetBrains Rideremanuelebartolesi.com 2nd of 2 in this piece