not a google fanboy by any stretch... though i've been thrilled with the flash line of models... i exclusively use it on high, and have found it to be a great fit for increasing productivity 10-fold while maintaining quality... sure it can't just go off and one-shot a bunch of work, but at the complexity level i tend to work at, neither can the frontier in a robust way that i can be confident in... sure i have to be in the loop more, but that helps keep me grounded and course-correct earlier before wasting tokens... and when you sufficiently spec out a coding/software problem, and i mean really document all of the critical nuance, it will successfully satisfy the constraints... the quality is rarely acceptable on first-pass, but it forces me to stay connected to the architecture more than i would be if using a frontier model... i've found this to be a happy middle-ground of productivity and awareness...
HN user
fur-tea-laser
I'm a quasi-mathematician who adapts and translates rigorous, nuanced mathematical concepts for more expressive mediums like natural language and code. This results in shared processes for synthesizing and analyzing technical assets that are actionable, pragmatic, and accessible to both deep domain experts and practical execution teams alike.
Think of me as an LLM wrangler who uses latent space acupuncture to pin down precise model behaviors, replacing haphazard reactions with a systematized, consistent iterative process.
Let's chat at fur.tea.laser@gmail.com.
https://github.com/fur-tea-laser
suprasole - a pty proxy for enabling deterministic and ergonomic extensions/middleware for harnesses in an agnostic way... also working towards building an automation/scripting layer on top of harnesses via suprasole...
apologies for polluting the space... though i have to grab the attention of whoever i can, however i can, and filter out bad fits simultaneously.. i'll stop my mini-marketing campaign now... i just don't want to be sleeping on the sidewalk again, hence the aggressiveness...
good day!!
full-disclosure: i am ex-homeless transitioning from living on the streets to being a participant in society again...
Location: United States of America _MST_
Remote: No
Willing to relocate: Yes
Technologies: Irrelevant, but Typescript, Javacript, React, GraphQL, .etc
Resume: https://fur-tea-laser.github.io/resume/
Email: fur.tea.laser@gmail.com
Think of me as an LLM wrangler who uses latent space acupuncture to pin down precise model behaviors, replacing haphazard reactions with a systematized, consistent iterative process.
Let's chat!
full-disclosure: i am ex-homeless transitioning from living on the streets to being a participant in society again...
Location: United States of America _MST_
Remote: NO
Willing to relocate: Yes
Technologies: Irrelevant
Resume: https://fur-tea-laser.github.io/resume/
Email: fur.tea.laser@gmail.com
Think of me as an LLM wrangler who uses latent space acupuncture to pin down precise model behaviors, replacing haphazard reactions with a systematized, consistent iterative process.
Let's chat!
aspect-oriented programming is an apt name for what i imagine will be llm-science 101 in the not-too-distant future... though i found the "joint point model" details superfluous, and the piece as a whole to be cursory... modern aspect-oriented programming will become a much richer & more robust ontological and application tapestry than its legacy predecessor... one of the core fundamentals of aspect-oriented programming in the context of llms is the need to accurately model the entanglement of related aspects... let's look at an over-reduced and isolated example using english expressions as our subject... let's define two aspects of an english expression: brevity and precision... if we amplify one aspect, the other begins to degrade... thus we need to align our models with the nature of english, and entangle the two aspects... entangling aspects changes the nature of optimization itself... we go from maximizing in one direction to pushing to the entanglement's frontier (pareto), and then steering along that frontier for taste... this doesn't mean we don't define aspects in isolation... it just means we need to align our aspects with reality and reflect its nature via entanglement...
i have a bunch of md templates at my disposal, which serve as the basis for my prompt toolbelt... these templates are populated and crystalized with concrete json instances... the json instances are tailored & scoped for various tasks... currently i have to synthesize a bunch of markdown artifacts that pollute my project directory and are at risk of becoming stale and out-of-sync... prompt-time middleware hooks that allow me to transform a json file into my final markdown prompt would alleviate these issues and improve developer ergonomics...
can you expand? i'm looking, but havent come across anything along the lines of what i want