Chip Unicorn

https://im-in.space/@Chip_Unicorn

A perpetual student, here to read from more knowledgeable people more than to write. Software engineer, furry. Icon created by @rowyn

Suspected Mexican and Canadian sympathizer!

pronouns: they/them and he/him

Public Key

npub1jn2eupsx3ksc2kqeqqlkkrmtk5zwlm02mdrm5sqcmln7fry5rctsnpcegt

NIP-05 Address

chip_unicorn_at_im-in.space@momostr.pink

Profile Code

nprofile1qqsff4v7qcrgmgv9tqvsq0mtpa4m2p80ah4dk3a6gqvdlely3j2pu9cprpmhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmntqyqqdyl788

Publishing to

relay.momostr.pink

Author Public Key

npub1jn2eupsx3ksc2kqeqqlkkrmtk5zwlm02mdrm5sqcmln7fry5rctsnpcegt

Show more details

Last Notes

2026-01-06 19:52:39 UTC

One coworker -- who I'll call Xavier -- does everything through LLMs. He's the kind of developer that managers who have never been programmers *adore*: 3000 lines of code per day.
I just realized that Xavier cannot read code, even code that he submits for review. He "understands" code by running it against test files and seeing whether results are reasonable. He can only say what the code does, not what causes it to behave in a way.
But that has several problems. An obvious first issue is that if a problem doesn't show up in the test file, then it will never be fixed. A less obvious issue is that his code is brittle and it generalizes very poorly.
Because Xavier doesn't read code, he has a very tough time imagining "What might go wrong?" And because he relies on the LLM, he misses very broad solutions, like using well-established libraries that solve dozens of problems at once.
Programmers who dive deep are still very, very useful.