Skip to main content Dennis Traub - Software Engineer & Developer Advocate

Welcome!

This is my personal logbook of discoveries, links, code fragments, and random learnings, where I document things I don’t want to forget and solutions I might need again.

  1. Upgrading .NET dependencies: Essential dotnet CLI commands

    Need to update your .NET packages? Here are the key commands you’ll need:

    Check for Updates:

    shell code snippet start

    dotnet list package --outdated

    shell code snippet end

    Update Packages:

    Single package (latest version):

    shell code snippet start

    dotnet add package PackageName

    shell code snippet end

    Specific version:

    shell code snippet start

    dotnet add package PackageName --version 1.2.3

    shell code snippet end

    Bulk updates:

    While there’s no built-in command to update everything, you can use dotnet-outdated:

    shell code snippet start

    dotnet tool install --global dotnet-outdated-tool
    dotnet outdated -u  # Updates all packages

    shell code snippet end

    Pro tip: Always backup, and test after upgrading. Add --prerelease if you need preview versions.

    /* End of post */
  2. Hedonic adaptation

    Also known as hedonic treadmill: The tendency of humans to return to a relatively stable level of (un-)happiness despite positive or negative changes. The reason why we always need more: more money, more stuff, more likes…

    /* End of post */
  3. Writing CSS selectors with Amazon Q Developer

    I’m notoriously bad at CSS! 😅

    I rarely work with it, so advanced selectors always leave me scratching my head. But thanks to AI, I don’t need to memorize them anymore!

    Today’s example: I needed to style specific elements, but only if they weren’t the first one. Instead of googling CSS selectors for the hundredth time, I let Amazon Q’s new Inline Chat handle it for me. Here’s my workflow:

    1️⃣ Select the CSS snippet
    2️⃣ Press Ctrl+i (Cmd+I on Mac) for Q’s Inline Chat
    3️⃣ Explain what I need in plain English
    4️⃣ Review Q’s generated diff
    5️⃣ Quick sanity check and accept!

    Using AI without interrupting my coding flow really is a game changer!

    /* End of post */
  4. How to set up the vertical ruler in VS Code

    There’s this handy vertical ruler feature in most IDEs, showing a simple guide line to help maintain consistent line lengths across your codebase. It’s one of those small tools that makes a big difference in keeping your code maintainable and easier to review.

    Here’s how to set it up in VS Code: Open your settings file and add the editor.rulers configuration. You can set a single ruler at the traditional 80-character mark, or add multiple guides for different contexts. Here’s an example that sets the ruler at 80 characters:

    json code snippet start

        "editor.rulers": [80]

    json code snippet end

    Remember, this ruler is just a visual guide - you’ll still need to format your code manually or with your preferred auto-formatter.

    /* End of post */
  5. Temperature and Top-k demystified

    Most AI models provide temperature and top-k to control response randomness, here’s what they do:

    🌡️ Temperature (creativity level) - Like a chef in the kitchen: Low means sticking to recipes, high means getting creative with flavors.

    ▼ Top-k (word choice limits) - Like restricting your chef’s pantry. Rarely useful in practice.

    Pro tip from AI engineers: Use temperature alone. Let your chef focus on creativity without restrictive ingredient lists!

    /* End of post */
  6. Jekyll or Hugo?

    After years of procrastination, I finally dove into static site generators. Jekyll didn’t click, but Hugo won me over - taking just a few hours to set up with help from Claude. Here’s how that conversation went.
    » Read more
  7. Testing JetBrains Fleet

    I’ve started testing JetBrains Fleet today. It feels a bit odd after having spent decades working with fully featured IDEs, like IntelliJ IDEA, etc. I’m not sure if I like it yet. But I guess I’ll give it a try for a few days and we’ll see if it can be a lightweight alternative, at least for simple editing, like writing this blog.

    /* End of post */