1. X
  2. Anže Pečar
Log inSign up
Anže Pečar
10K posts
Image
user avatar
Anže Pečar
@anze3db
I write code and surf waves.
Lisbon, Portugal
pecar.me
Joined April 2009
1,771
Following
1,141
Followers
RepliesRepliesMediaMedia
  • user avatar
    Anže Pečar
    @anze3db
    Jul 31
    My dog kept me in Zone 2 for 3kms. Then I had to drop him off and immediately made bad decisions. 💛
    Image
    Image
  • user avatar
    Anže Pečar
    @anze3db
    Jul 31
    We benchmarked 15 models for triaging vulnerabilities. * Kimi K3 came out on top but marked a true positive as a false positive ☠️ * Opus 5 refused to give a verdict on 11 vulnerabilities * Sonnet 5 and Luna outperformed Terra and Sol Full post 👇
    Image
    Benchmarking 15 LLMs on SAST false-positive triage
    From fencer.dev
  • user avatar
    Anže Pečar
    @anze3db
    Jul 27
    Quite a way to start a Monday 😅
    GitHub PR stats:

+86,316 of added alines
-29 removed lines
  • user avatar
    Anže Pečar
    @anze3db
    Jul 21
    I do think it nailed my voice though!
    Voice

First person, always. Posts are “I did X and here’s what happened”, not “one can do X”. Use “we” only for genuine team work or when walking the reader through code (“Let’s look at the view”).
Address the reader directly as “you” in tutorials: “You’ll have to add the pidfile parameter.”
Warm, enthusiastic, and self-deprecating. Admit mistakes and ugly code openly: “The one-liner has a face only a mother could love”, “which may or may not have happened in the past 🙈”.
Hedge honestly, not weaselly. Say “I haven’t tested it myself, so I’m not sure it’s foolproof” or “take the results with a grain of salt” rather than vague qualifiers.
Credit people by name with links: “Shoutout to Rémy on BlueSky”, “Thank you Hynek”. Community attribution is a core habit.
Exclamation marks are welcome when the enthusiasm is real. Emoji as sentence-final emotional beats: 🎉 for wins, 😅 for sheepishness, 🤞 for hope, 💥/☠️ for breakage, 🙈 for embarrassment.
    user avatar
    Anže Pečar
    @anze3db
    Jul 21
    I asked Claude to come up with writing guidelines based on my blog posts: > A few things I deliberately did not encode as guidelines: the frequent typos (characteristic of your fast publishing cadence) 88 blog post in 14 years is not fast publishing cadence 😅
  • user avatar
    Anže Pečar
    @anze3db
    Jul 21
    I asked Claude to come up with writing guidelines based on my blog posts: > A few things I deliberately did not encode as guidelines: the frequent typos (characteristic of your fast publishing cadence) 88 blog post in 14 years is not fast publishing cadence 😅

Log in or sign up for X

See what’s happening and join the conversation

Continue with phone
or
Log in with username or email
Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
Advertisement
Advertisement