Kirył 🌞

ruby programmer/backend web developer, snow/wake/kiteboarder, cyclist, bit guitar player #StandWithBelarus

[Andrej Karpathy @karpathy]

We'll be spending a lot more time trying to understand the outputs of language models. A few thoughts, tips & tricks:

Writing. Something I've had success with: Ask your LLM to explain something in ASD-STE100, it's a controlled language specification originally developed for aerospace maintenance documentation. LLMs well-versed in this language and it comes with heavy constraints on clean writing style that I often find a lot more readable. Sometimes I've tried to soften it a bit e.g. ask for "80% of the way to ASD-STE100" because the spec is quite stringent. But even better:

Diagrams / images. Instead of writing, ask your LLM to create a diagram. These can be a lot easier to process, parse, and understand. But even better:

Web pages. Ask for output "in HTML" to get a beautiful, interactive webpage. LLMs are getting really good at frontend and can create beautiful experiences, animations, etc. But even better:

Explainer videos. The output format I am most bullish on is fully custom / bespoke explainer videos generated on any arbitrary topic. Experiment with things like "Create a 3b1b style video explainer on X. Use my ElevenLabs API key for audio narration". (you'd need an API key for the latter or you can ask your LLM to find you decent free alternatives that use your local compute). This is actually starting to work!

In summary:
- As LLMs get better, they will do more and more of the legwork autonomously, and a lot more of our work will rise up the abstractions into oversight and understanding.
- Luckily, LLMs can help here too because as intelligence and code are increasingly abundant, you can ask for large, custom, discardable software artifacts (e.g. web apps, video explainers) that would have never made sense to create before. Push the boundaries here and you'll be surprised.

[Kirył 🌞 @siakiera]

Seems https://t.co/nV2VzFVf2l is down. Can we do smth about it? Author retired 6y ago. #ruby #rubyonrails #mri

[Kirył 🌞 @siakiera]

@davidsenra @dhh @37signals I wish I'll work with you in the same company some day @dhh @jasonfried

[Uncle Bob Martin @unclebobmartin]

I’m significantly older than you. I started coding in the late 60s. My current strategy is to not read any of the code written by my agents. That’s the only way I can take advantage of their productivity. What I do instead is to surround the agents with extreme constraints. Unit tests, gherkin tests, QA procedures, quality metrics, mutation testing, test coverage, and a plethora of others. In the end, I have very high confidence in the code they produce because they’ve had to run the gauntlet of all of my constraints and tests.

[Kirył 🌞 @siakiera]

@vera_katleta Ха, менавіта такой цябе і памятаю

[Kirył 🌞 @siakiera]

@TheAliceSmith Maybe it's all about authoritarianism with different branding ?

[Kirył 🌞 @siakiera]

@sergeynazarovx True

[Kirył 🌞 @siakiera]

@CP_Ogamba Just pay your bills first

[Kirył 🌞 @siakiera]

@patrickstea сякеры топ

[Kirył 🌞 @siakiera]

@fabpot Ruby on Rails still the better option.

[Kirył 🌞 @siakiera]

@stats_feed Australia is known for Vienna [joking]

[Kirył 🌞 @siakiera]

@elonmusk And if ANY resistor ANYWHERE can prevent voltage spikes EvErYwHeRe you have broken design.

[Kirył 🌞 @siakiera]

@NiohBerg True.

[Kirył 🌞 @siakiera]

@klmivn Лепей з сабой калі не жадаеце прыгод з атраўленгем альбо ізжогай

[Kirył 🌞 @siakiera]

@maccaw https://t.co/rhL5Aa0HAK

[Kirył 🌞 @siakiera]

@strzibnyj Turkey goes pretty expensive nowadays, no?

[Kirył 🌞 @siakiera]

@varjat @zlyaleh666 Таму і гатовы прымаць, хіба што не ў стане вайны.

[Kirył 🌞 @siakiera]

@varjat @zlyaleh666 Фінляндыя ўступіла без хвалі нядаўна. Беларускі выступ занадта важны каб яму адмовіць.

[Kirył 🌞 @siakiera]

@varjat @zlyaleh666 А чаму Латвію і Эстонію ўзялі ?

[Kirył 🌞 @siakiera]

@andbugfixes Koyaanisqatsi