Skip to content

Instantly share code, notes, and snippets.

View sjmatta's full-sized avatar

Stephen Matta sjmatta

View GitHub Profile

Analyze this codebase and create comprehensive technical documentation. For each major component:

  1. API Surface: Document all public functions, classes, methods, and their signatures

    • Parameters (types, defaults, descriptions)
    • Return types and values
    • Exceptions/errors thrown
  2. Code Examples: Provide practical, copy-paste ready examples showing:

    • Common use cases (80% of typical usage)
  • Advanced patterns

Making Data "LLM-Ready" for Agent Function Calls: A Comprehensive Guide

Demystifying agent-ready data structures

Making data "LLM-ready" for agent consumption via tools and function calls represents a distinct challenge from traditional API design or RAG system preparation. This research synthesizes findings from production systems at NVIDIA, Bloomberg, Microsoft, and other leading organizations to provide actionable guidance on transforming raw data into formats that LLM agents can effectively consume and reason about through function interfaces.

Part 1: Data Formatting and Structure Requirements

The universal standard emerges

Choosing the Right Java Thread Pool

1. Fixed Thread Pool (Executors.newFixedThreadPool(n)): The Steady Performer

What is it?
A thread pool with a fixed number of threads. It keeps things predictable and straightforward.

Best For:

  • CPU-bound Tasks: Ideal for tasks that are heavy on computation. Keeping the number of threads aligned with the number of CPU cores helps avoid context-switching overhead.
  • Controlled Concurrency: Useful when you want to cap the number of concurrent threads to prevent overloading the CPU.
@sjmatta
sjmatta / sagemaker.error5.txt
Created September 14, 2018 18:03
SageMaker: ClientError: Artifact upload failed:Error 5: Received a failed archive status
When running a SageMaker training job, training succeeds but you get an error.
ERROR: SageMaker: ClientError: Artifact upload failed:Error 5: Received a failed archive status.
SOLUTION: Increase additional volume size

Keybase proof

I hereby claim:

  • I am sjmatta on github.
  • I am sjmatta (https://keybase.io/sjmatta) on keybase.
  • I have a public key ASC9-LMqa_AYUnzhQlNQ_D7J_zolDR_6nSok0wUfRIK7rgo

To claim this, I am signing this object:

@sjmatta
sjmatta / gradle-notes.txt
Created February 10, 2017 13:53
Notes for Gradle
* in cmder: gradle(w) clean build --console plain
@sjmatta
sjmatta / classification.html
Created March 3, 2016 16:25
FOUO Classification Banner
<div style="height: 2em; line-height: 2em; color: white; background-color: green; text: white; text-align: center;">
<strong style="display: inline-block; vertical-align: middle; line-height: normal;">UNCLASSIFIED/FOUO</strong>
</div>
package react.config
import groovy.transform.builder.Builder
import org.springframework.context.annotation.Configuration
import org.springframework.context.annotation.Profile
import org.springframework.core.io.ClassPathResource
import org.springframework.core.io.Resource
import org.springframework.util.StringUtils
import org.springframework.web.servlet.config.annotation.ResourceHandlerRegistry
import org.springframework.web.servlet.config.annotation.WebMvcConfigurerAdapter
docker-machine create --driver digitalocean --digitalocean-size "2gb" --digitalocean-access-token=$DIGITAL_OCEAN_TOKEN default
@sjmatta
sjmatta / gist:bc5c810d0babd60e1023
Created October 9, 2015 13:09 — forked from leftclickben/gist:322b7a3042cbe97ed2af
Steps to migrate from SVN to GitLab

Steps to migrate from SVN to GitLab

This process worked for me. I take no responsibility for any damage or loss incurred as a result of following or not following these steps or, for that matter, anything else you might do or not do.

Setup

  • SVN is hosted at svn.domain.com.au.
  • SVN is accessible via http (other protocols should work).
  • GitLab is hosted at git.domain.com.au and: