Deschide articolul original într-un tab nou Schimbarea acestei opțiuni se aplică imediat și reîncarcă pagina.
LECTURA
Înapoi la articole →

Márcio Florindo

marcioflorindo.com/feed.xml
Vizitează site-ul

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 31

  1. Remote, but not from here

    (Márcio Florindo)

    The job market is brutal, but have you noticed how few remote jobs you can actually apply for?

  2. You already have docs, you just don't know it yet

    (Márcio Florindo)

    If your company's knowledge is scattered across multiple places and nobody owns it, sooner or later that knowledge debt will cost you money.

  3. Measuring my search, not defining myself by it

    (Márcio Florindo)

    After months of applying to jobs and waiting for answers that might not come, you can start measuring your self-worth by the number of replies you (don't) get.

  4. An untested API example is just a guess

    (Márcio Florindo)

    A curl command can be perfect and still be a lie.

  5. The context nobody wrote down

    (Márcio Florindo)

    Companies keep building AI agents that work great in demos.

  6. How to use AI in your workflow as a tech writer

    (Márcio Florindo)

    As tech writers we have a lot of tools at our disposal.

  7. Nobody checks the AI that rejects you

    (Márcio Florindo)

    I use AI to search hundreds of job ads and show me the ones that might suit me best.

  8. I tried to hijack my own job search

    (Márcio Florindo)

    A few weeks ago, I fed my job-search tool a fake job advert built to hijack it.

  9. Too efficient to keep

    (Márcio Florindo)

    The explanation I was given for my redundancy was that AI had made me too efficient.

  10. Nobody fetched my llms.txt

    (Márcio Florindo)

    A while back I added some machinery to my site in order to make it more legible to AI.

  11. I rebuilt a 1996 Macintosh and found nothing missing

    (Márcio Florindo)

    Click the new button on my site and you'll see a 1996 Macintosh running System 7.5.3 in your browser.

  12. Check the research before you read it

    (Márcio Florindo)

    When a coding agent gets something wrong, you find out fast.

  13. The fake job I nearly applied to had a documentation problem

    (Márcio Florindo)

    It was late, I'd been looking at applications for a while, and the posting looked enticing.

  14. My CV is no longer a document

    (Márcio Florindo)

    My CV existed as four copies that never quite agreed: a Markdown file, a website page, a PDF, and the copy my job-search tool reads.

  15. The skeptical agent: why one AI is never enough

    (Márcio Florindo)

    I've spent quite a bit of time building AI workflows and learned one thing that immensely improved the quality of my work: AI is blind to its own errors and needs a pass from a skeptical agent to catch mistakes.

  16. I built a game to defend my job

    (Márcio Florindo)

    The healthy response to losing a job is probably long walks and a journal.

  17. I wanted to run my own AI. My laptop says not yet

    (Márcio Florindo)

    The pitch sells itself.

  18. When thinking is just a slower way to make the same decision

    (Márcio Florindo)

    Does more reasoning actually lead to better decisions, or just more latency?

  19. I haven't written code in years—but I still built this app

    (Márcio Florindo)

    After years of fighting clunky spreadsheets on my phone, I realized the problem wasn't the data, but the interface.

  20. Job hunting: How I scaled my personal tool for anyone to use

    (Márcio Florindo)

    A few days ago I wrote about how I built a tool to automate my job hunting process.

  21. AI got me laid off. So I built an AI to get me hired

    (Márcio Florindo)

    Stop scrolling, start applying.

  22. I built an app that notifies me when there's a fire nearby

    (Márcio Florindo)

    This morning I heard sirens.

  23. I keep rewriting my own job title

    (Márcio Florindo)

    I've changed the title on my own website four times this month: Technical Writer, then Knowledge Engineer, then back.

  24. Writing is the output. This is the work

    (Márcio Florindo)

    The label I've been using for five years — technical writer — is accurate and fundamentally misleading at the same time.

  25. AI doesn't replace tech writers — it gives them leverage

    (Márcio Florindo)

    There is a version of the AI narrative that tells you that AI writes content, therefore writers are obsolete.

  26. Your AI assistant forgets everything between sessions — here's how I fixed that

    (Márcio Florindo)

    A colleague of mine built a system he calls Project Brains.

  27. Separating what the AI knows from what the AI does

    (Márcio Florindo)

    As a technical writer, there are a lot of repetitive tasks I have to do manually that eat into my time.

  28. You don't need to remember 22 command names — the AI already knows them

    (Márcio Florindo)

    Over the past month or so I've built 22 slash commands that automate different parts of my documentation workflow with OpenCode.

  29. The part before writing is the slowest part — so I automated it

    (Márcio Florindo)

    The other day I closed a P1 ticket that asked me to review a 5-lesson internal training course and figure out what was missing from our developer docs.

  30. From one tool to a full toolkit: how I used AI to rename 4 products across 695 files in 3 days

    (Márcio Florindo)

    A few months ago, I was asked to lead the documentation side of a large product renaming project.

  31. Building an AI research command for documentation tickets

    (Márcio Florindo)

    Tech writers spend a lot of time researching before they can start writing.